EOF - Waving Goodbye to Facebook
In a blog post last April titled “Building the Social Web Together”, Mark Zuckerberg of Facebook wrote, “The power of the open graph is that it helps to create a smarter, personalized Web that gets better with every action taken.” The “open graph” of which he speaks is your social graph—your collection of contacts—on Facebook, augmented by “personalized experiences” with the likes of “Microsoft Docs, Yelp and Pandora”—which are Facebook's “three pre-selected partners”.
Responding in his own Newsweek blog, Barrett Sheridan called Zuckerberg's plans a “Play to Take Over the Entire Internet”. In TechCrunch, MG Siegler's headline read, “I Think Facebook Just Seized Control Of The Internet”. Whether or not Facebook is that ambitious, it won't succeed at anything other than enlarging itself. The limits to that are those of any private architecture. It can get big, but not bigger than the planet. What Facebook has built is the Great Indoors. A lot of people like going there, just like a lot of people like going to shopping malls. But Facebook is a building, not geology.
The Web is geology. It is a wide-open public space on which private and public structures can be built in boundless varieties. Linux is probably the most widely used building material below and within those structures. Calculating its value is pointless, because—as Eric S. Raymond made clear long ago—Linux has use value more than sale value. As useful stuff, its leverage is boundless and, therefore, incalculable. It also will last as long as it remains useful.
The same cannot be said of Facebook, whose value is quite calculable and which will thrive only as long as its revenue model and its investors' patience holds out. Both of those will be shortened by the dissatisfaction of users, which Facebook has been risking increasingly over the years.
We've seen this movie before, many times. The most important and dramatic example is Microsoft's “HailStorm”, which arrived and flopped in 2001. As with all heavy weather, it threatened to change (at least superficially) the Web's geology...
The HailStorm architecture is designed for seamless extensibility and consistency across services. It provides common identity, messaging, naming, navigation, security, role-mapping, data modeling, metering and error handling across all “HailStorm” services. And rather than risk compromising the user-centric model by having advertisers pay for them, the people receiving the value—end users—will be the primary source of revenue. “HailStorm” will help move the Internet to end-user subscriptions, in which users pay for value received.
...by putting the Net itself inside Microsoft's own building. That didn't work. Nor will anything Facebook does for roughly the same purposes.
Of course, Microsoft wasn't talking about the real Internet. It was talking about the commercial activity happening on top of the Net. Likewise, Facebook isn't talking about the Web, but rather the “social networking” that's been all the craze during the past few years, and which seems to be happening mostly within and between commercial entities.
As Facebook seems determined not to learn from the failings of its elders, how about moving past all the commercial interests here? How about making our own social networks—ones that are owned by nobody (or close enough), used by everybody and improved by anybody? How would we do that?
One possibility is Google's Wave. It's a way to meet, collaborate, share files and do other literally social stuff. It's also an open-source project that still needs a lot of shaking down. And, although Google hosts the first incarnation, it's still there for anybody else to run with it, fork it or whatever. Here's how Joel David Palmer summed up the possibilities, in a blog post by Steven Hodson:
At the extreme in personal control, we could each configure our own computer as a little wave server and have primary control of our social networking server logs. Less extreme than this, any community or association that's used to serving e-mail could as easily and securely serve waves to their group.
Widespread adoption of waves would automatically reclaim a lot of user privacy and personal responsibility for on-line communications of every kind. The contents cannot be mined by outside interests without committing criminal acts—waves are as private as e-mail.
Waves give you and your connections complete control over your social networking experience, and real opportunities for creative collaboration. A wave can be e-mail, telephone, IM, videophone, collaboration platform, art form, performance venue. Transitioning to waves appears to be a good strategy toward a collaborative social Web that is peer-to-peer rather than server-client.
Sounds good to me. If you've got any better ideas, let's hear them. Maybe we can coax some Facebook occupants—including ourselves, in many cases—to come enjoy the Great Outdoors.
Doc Searls is Senior Editor of Linux Journal. He is also a fellow with the Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at UC Santa Barbara.
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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
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