What does the Microsoft "partnership" with Facebook mean for users?
Here's the key fact: Facebook's users are not its customers. They're the targets to which Facebook's customers aim advertising. In old media this was no big deal. But Facebook isn't just a "medium". It's a vast walled garden where the social activity of members and visitors constantly improves the ability of advertisers to "target" both.
This is a Good Thing only if it works for everybody including both those targeted as well as those doing the targeting. And if users are actually involved, they have some important questions:
- What happens to my identity-related information?
- How is it used, and by whom?
- How much control do I have over my data (or data about myself) including what Facebook "partners" do with that data?
Jeremiah Owyang visits these questions in his latest post, How Microsoft got their Passport after all. He begins,
A few hundred million is a steal for your identity, they've got plenty of money.
Microsoft and Facebook are in partnership, but what's at stake? Three things:
- Facebook knows who you are: your name, your gender, where you live, your martial and political status, sexual preference, age, where you work, the list goes on. The funny thing is, you've voluntarily given that information up.
- They also know who you connect to, who you talk to, and what you say to them (you don't own those private message ya know).
- Sure, up to one third of all profile information is bogus, but what about those unsaid gestures: What people do is more important than what they say. What apps you use, how frequent, what and who you click on.
Great, but why does it matter? Because the new partner likely will have access to this very precious data.
[We once rejected Microsoft's Passport identity campaign, but weve potentially and unknowingly just handed it over]
First, Microsoft had a very instructive failure with Passport, and the "Hailstorm" effort of which it was a part. One guy leading that instruction is Kim Cameron, primary author of the Seven Laws of Identity and creator of the Identity Metasystem concept (among other things), all which we made a cover story in the September 2005 issue of Linux Journal. To the best of my knowledge, that was the first time a Microsoft effort made the cover of the magazine and it deserved to.
In brief, the Seven Laws are:
- User Control and Consent
- Minimal Disclosure for a Constrained Use
- Justifiable Parties
- Directed Identity
- Pluralism of operators and technologies
- Human integration
- Consistent experience across contexts
Second, many independent developers at companies and organizations large and small (including many individuals their own) have joined together (guided to a significant degree by Kim and his Laws) as in informal Identity Gang (now a working group of Identity Commons) with the shared purpose of empowering individuals to control their own identity-related information in the networked world. "User-centric identity" is still new, and we're all still in the early stages of Whatever This Will Be; but already much technical progress has been made, most of it in the form of open source development.
The Gang gathers at informal but highly productive Internet Identity Workshops (IIWs) twice per year at the current rate. In fact, I'm one of the organizers. The next one is December 3-5 in Mountain View. Here's my open invitation for Facebook folks to come help the rest of us work on applying the Laws of Identity in the social contexts they're pioneering.
There is much work to be done. We'd love to have Facebook help us do it.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide