Making more sense of Flickr’s Ides of March

Yesterday I wrote a post that was admittedly vague and rambling. I definitely did not “go home” before I wrote it, so I’d like to correct that, and try to make my meaning clearer (and by “go home”, I’m using speaker trainer Lura Dolas‘ concept of being grounded and authentic before opening your mouth to say something).

So, if I were to rewrite my post, I might say something like this:

The account merger for Yahoo! and Flickr accounts on March 15 (the Ides of March) should not come as a surprise; indeed, we’ve known that it was coming for a long time.

What the deadline represents to different Flickr members is personal and unique; there is very little generalization that can be made of the event, except that the reactions vary greatly along a spectrum from utter indifference to downright anger and resentment.

What Flickr members are experiencing is consistent with what any passionate community experiences when something that represents the core of their experience is disturbed. Whether logical or not, it’s kind of like repotting a plant — the more sensitive to the environment, the more the transplant can be debilitating, destabilizing and disorienting. There’s no rhyme or reason per se, but the individual shock can be a challenge to overcome.

Anecdotally, my personal experience was rather blasé. Previously, I had maintained a “self-perceived independence” by not succumbing to the demands of the Yahoo! conglomerate and merging my account. Indeed, every time I signed in via the “old skool login”, I got a rush of silent pride that I was still free, having avoided “following the sheep”.

My resistance somehow guaranteed that I still had ultimate control over my destiny — and that no corporate monolith could tell me what to do — especially as long as I had trusted friends on the inside advocating for my right to free choice and free association.

But that was a temporary illusion that I knew in the back of my mind would someday end.

And yesterday, the jig was up, the mirage evaporating in the form of a FlickrMail: the embodiment of Flickr’s final transformation from a renegade underdog that busted convention and ran roughshod over a corporate hegemon to become yet another cog in the machine.

Or so the self-serving mythology goes.

In reality, I’m not so sure that all that much has changed, really. I am inclined not to make any final pronouncements about Flickr, Yahoo! or whatever else. Hell, I switched over my account, and it wasn’t that bad. Innocence lost, yadda yadda, the world carries on.

Now, the part that I want to take a moment to reflect on, which I also alluded to in the last two paragraphs of yesterday’s post (and is somewhat carried on here), is the part about managing, owning and making choices that effect the destiny of the identity (or identities) that one has spent time creating and cultivating online.

I would posit that the fear or fear-driven reactions that a lot of people have expressed or experienced in the past two days can be traced to this particular nugget of thinking.

What we lack online today is the equivalent of what we call human rights in the offline world. As it stands, Terms of Service are written foremost in the interest and protection of the Corporation. Thus individuals have little transformative recourse when things go wrong for the vocal are but few among millions.

As such, minority hold outs are left feeling particularly vulnerable and exposed. Especially in the case of Flickr, where people have developed visceral and almost human connections through the service, anything that threatens their “dominion” is an invasion that provokes an immune response by what I’d call the “proverbial community anti-bodies”, for better or worse.

In this case, Yahoo! — as the larger organism eclipsing the smaller — is perceived as effectively infusing its memetic DNA into the cultural neurology of the lesser system and without effective recourse to prevent this kind of “digital “, the anti-bodies lash out in response to the invading foreign agents, as you would expect in any system.

This dance is natural, is normal, and a simple part of biological and social evolution. In the scheme of things, I think the reaction of the minority does make sense here, even if it ultimately doesn’t matter that much. Given the current architecture of social networks, where your existence and environment is at the whim, pleasure and financial health of the network owner (let’s call her “God”), these kinds of decisions will continue to elicit strong social responses when God acts like… well… God.

Asides (lightly scrambled)

I do wonder, then, if this kind of personal exasperation would more quickly lead to the creation of “articles of digital personhood” or a collective “bill of digital human rights”. Or if, instead, it might drive the furtherance of independent identity services that promise to restore dominion over one’s online personas.

On a larger scale, will these experiences lead to the recognition of our digital selves as rights-weilding extensions of ourselves? Were there a “Digital Civil Liberties Union”, would those with grievances turn to such a centralized body for redress? or, rather than unionizing power, would they prefer to simply come and go as they pleased, as one does when she moves from one house to another, taking all her possessions and friendships with her but leaving the structure behind, and letting the market woo and serve her by playing to her desires and free will to choose?

Further reading

Bating the mousetrap with chunky peanut butter

Flickr peanut butter
Original by starpause kid and shared under a Creative Commons License.
When it comes to mousetraps, it’s fairly common knowledge that an effective cheese alternative for trapping mice is peanut butter.

However, we already know that Yahoo isn’t too fond of peanut butter. At least the smooth kind spread thin.

So it’s interesting to note that, perhaps as part of the strategy to outlaw renegade peanut butter within the organization, the formerly independent outpost known as Flickr will be forcing users to either merge or create a new Yahoo account to login after March 15:

On March 15th, 2007 we’ll be discontinuing the old email-based Flickr sign in system. From that point on, everyone will have to use a Yahoo! ID to sign in to Flickr.

We’re making this change now to simplify the sign in process in advance of several large projects launching this year, but some Flickr features and tools already require Yahoo! IDs for sign in — like the mobile site at m.flickr.com or the new Yahoo! Go program for mobiles, available at http://go.yahoo.com.

If you still sign in using the email-based Flickr system (here), you can make the switch at any time in the next few months, from today till the 15th. (After that day, you’ll be required to merge before you continue using your account.) To switch, start at this page: http://flickr.com/account/associate/

Complete details and answers to most common questions are available here: http://flickr.com/help/signin/

If you have questions or comments about signing in with a Yahoo! ID, speak up!

You can imagine that not everyone is happy about this, especially after the reaction the first time around:
Jimbo doesn't like it

Now, I’m not interested in opening old wounds. The Flickr folks have given plenty of notice about the coming changes (figure at least a month and a half if not the full 18 months since they were acquired) and of course are available for consolation, hand-holding and so forth.

Oh, and contrary to my tendency towards conspiracy theories, I’ll let Stewart debunk them outright:

And that’s it: there’s no secret agenda here, no desire to come to your homes and steal your TV. Over time, it just gets more expensive to maintain independent means of authentication and we could “spend” those efforts on other things which make Flickr more useful, more fun, more versatile, etc. And the smaller the ratio of old skool to Y!ID-based gets, the harder it is to justify not spending that effort on improvements.

I will, however, take this opportunity to rise up on my soapbox again and point out something worth reflecting on…

Look, Google’s already done the same thing with Dodgeball; it’s a sure bet that they’re going to do the same thing with their YouTube acquisition. We know that Yahoo logins are going to show up on MyBlogLog and eventually, probably Upcoming too — and, for that matter, any other user-centered acquisition that comes down the pipe. Microsoft is no different. Let’s face it: the future of the web is in identity-based services. And this is a good thing, if you’re ready for it.

My buddies Brian Oberkirch and Aldo Castañeda talked about the potential for this new economy recently. It’s coming and it’s scary (for some) and it’s unclear what it looks like. But the more that this happens under authoritarian login regimes, the more concern I feel for the effect these consolidation efforts will have on true democratic choice in where and how you spend your attention.

Realistically, it’s not terribly surprising that Yahoo! and the rest are going this direction. Hell, from a systems perspective, you’re just two entries in a grand database in the sky whereas you could be one. From a service perspective, unifying “you” across systems allows convenience and synergies to emerge. The problem is that these actions belie the sophisticated relationships that some people have with their online accounts and how their personas are represented. Though not everyone cares a whole lot about their screennames, others absolutely do. And beyond that, for whatever reasons they have, some people simply do not want to go near Yahoo! — something they never thought would be a concern of theirs when they originally joined Flickr.

But there’s a curious reality to look at here.

While I call Flickr home (NIPSA’d and all), just as there is a vehicle to vent my individual frustrations to Flickr, those same vehicles and mechanisms are available to me to splinter off and build my own peanut-butter-rich outpost anew. The missing piece of the puzzle, however, is my identity. I can’t just pack up my digital self and move on… whichever login system Flickr uses — Yahoo’s, Google’s, their own — I can’t “take it with me”. Even with their API, which is one of the most generous in the biz, it still doesn’t give me the ability to fully reincarnate myself somewhere else.

Now, I could and would like to turn this into a pitch for OpenID, but I won’t, at least directly. The Yahoo! folks have already expressed their distaste for creating Just Another Identity Silo and I keep waiting for them to prove it. I don’t mind waiting a bit longer. The wheels of the OpenID community are already in motion and I don’t have to plead for acknowledgment from the powers that be. The truth is, there are only a few more sites that will fall. The truth is, we are only now beginning to realize the degree to which we are all exposed and what the reality of our transparent society looks like. And the truth is, we are only just beginning to wake up to the idea that we should and can have dominion over our online lives, just as we believe is our right offline.

hResume is live on LinkedIn

Detecting hResume on LinkedIn

And the hits just keep on comin’.

I’m thrilled to be able to pass along Steve Ganz of LinkedIn‘s Twitter announcement (tweet?) of their support for hResume on LinkedIn (these tweets are becoming trendy!).

Brian Oberkirch is curious about the process they went through in applying microformats post facto — that is, without changing much of the existing codebase and design — and will have a podcast with Steve tomorrow on the topic. Personally I’m curious if they developed any best practices or conventions that might be passed on to other implementors that might improve the appearance and/or import/export of hResumes.

If you’ve been playing along, you’ll note that this is one of the first examples of a successful community-driven effort to create a microformat that wasn’t directly based on some existing RFC (like vcard and ical). Rather, a bunch of folks got together and pushed through the definition, research and iteration cycles and released a spec for the community to digest and expound upon.

Soon after, a WordPress plugin and a handy creator were released, Tails added support and then Emurse got hip: Elegant template has hResume support — long term planning, ya know? It’s your data, and we want to make it as flexible as possible..

I wrote about the importance of hResume in August:

Why is this better than going to Monster.com and others? Well, for one thing, you’re always in charge of your data, so instead of having to fill out forms on 40,000 different sites, you maintain your resume on your site and you update it once and then ping others to let them know that you’ve updated your resume. And, when people discover your resume, they come to you in a context that represents you and lets you stand out rather than blending into a sea of homogeneous-looking documents.

Similar threads have come up recently about XFN, hcard and OpenID on the OpenID mailing list and the possible crossover with hResume should not be ignored. When LinkedIn is already support hcard and XFN — it’s just a matter of time before they jump on OpenID and firmly plant themselves in the future of decentralized professional networks.

Oh, and the possibilities to accelerate candidate discovery for all those job boards shouldn’t be understated either.

Fixing Error 412 and Precondition failures in WordPress

Apparently mod_security is really aggressive around certain words (like in my previous post). To get around this, add SecFilterEngine off to your .htaccess file. You might not want to leave that snippet in there long, since it disables the security check, but if you find WordPress denying you the ability to post, it’s worth a shot.

Technology for the future: MacFUSE

Introduction: I can’t say for certain, but with concerns about BitTorrent making the rounds (P2P as a concept and technology should be fine long-term) I’m curious about two new technologies with a lot of future-shaping potential — one that I was already aware of and a new one that I just found out about yesterday…

I previously covered Adobe’s Apollo and now I’d like to discuss Amit Singh of Google’s MacFUSE.

FUSE

SSHFS iconLet me first state that this topic is going to sound downright dorky, but it’s actually really cool (as any geek would agree). Second, it took me a bit of research, some code digesting and a couple app installs to actually grok this, but now that I do, I think it’s an amazingly powerful demonstration of future web technology. Anyway, don’t say I didn’t warn you.

First, FUSE is a Linux fanboy’s dream — it allows you to hook up your file manager to just about any “collection of stuff”. A germane example might be connecting your Linux computer with a Windows machine in order to read, write and delete files. A less obvious example might be hooking up the Mac Finder up to an RSS feed and treating it like a hard drive where each post represents individual files that you can copy, move and delete.

Not that you would, but you could.

And in fact, Amit Singh, who built MacFUSE, demonstrates that use case in this excellent video. If that doesn’t give you goose-pimples, well… what if you could create “true smart folders, where the folders’ contents are dynamically generated by querying Spotlight.” No? Hmm. Ok.

Well, I’ll leave with you with two examples that might start to shed some light on what’s so interesting about this technology and then follow up with another post that extrapolates on an idea I’ve mentioned before and where I see kind of technology heading (perhaps not in its current form but in a more polished state).

SSHFS

So, let’s say that you want convenient access to SSH storage on your Mac. Ok, no problem. Just install MacFUSE Core, restart, then install sshfs (both files are available here). Load up sshfs, connect to your remote host (for example, on TextDrive, you’d used something like nelson.textdrive.com), enter your password and sshfs’ll mount the remote drive on your desktop, which you can then browse as though it were a local drive — moving, copying, drag and dropping files. In fact, I used this trick to upload the photo in this post.

GmailFS

The second example is definitely not for the faint of heart (and honestly, I couldn’t really get it to work though it compiled and connected just fine). The goal is to enable you to mount your Gmail account on your desktop — which might start to reveal Google’s interest in developing FUSE (more on that later). (Oh, and for the record, gDisk already serves this purpose very well, FYI). So, take a look at the detailed instructions laid out by Jean-Matthieu and then crack open that command line. You’ll need some knowledge of compiling apps (and you’ll need Apple’s developer tools) but it’s still pretty cool to be able to type mount -ovolname=bla -t gmailfs /usr/local/bin/gmailfs.py ~/gmailfs and have your Gmail account pop up on your desktop. Sort of.

Finally, as a bonus, you can mount a number of other services, including RubyForge and soon Blogger.

Given this advance (and Amit’s demonstration of hooking into Picasa, an RSS feed, Gmail, Google Docs and Spotlight) it’s just a matter of time before we’re able to connect natively to remote web services, as we do today over FTP, AFS and Bonjour. I’ll elaborate on just what that might mean in my next post.

Technology for the future: Apollo

Introduction:I can’t say for certain, but with concerns about BitTorrent making the rounds (P2P as a concept and technology should be fine long-term) I’m curious about two new technologies with a lot of future-shaping potential — one that I was already aware of and a new one that I just found out about yesterday…

The first is Adobe’s Apollo, and I’ll cover that in this post. The second is a more obtuse technology called MacFUSE, which I’ll cover in a second post.

Apollo

Apollo LogoThe first is Adobe’s forthcoming platform. In a recent interview with Mike Downey, Apollo’s senior product manager, he made some interesting comments. First, about the relationship between Firefox and XUL and Apollo:

With Apollo you can take advantage of OS-level services like system notifications, drag and drop from the desktop and complex local data storage and manipulation. Browsers are great for browsing content and Apollo doesn’t aim to replace that.

And second, about monetizing Apollo:

Adobe is also looking to build applications on top of Apollo. I can’t give you any specific examples right now, but we have several teams within Adobe that are building software on top of Apollo as we’re developing it. They give us some great feedback and will also give us some great examples to showcase at Apollo’s launch later this year.

So to me what this sounds like is web-enabled versions of flagship Adobe apps — and others that we’ve not heard of yet. Their Bridge product is already something of a browser of sorts, and I think we’re going to see that functionality woven more directly into each app — so instead of opening your color palettes from your local drive, you might import them from an Apollo-backed web service like Kuler.

Additionally, the relationship between Apollo and as a distribution platform is fundamental. As Ted Patrick points out, Flex is being built as a long term development and deployment platform, meaning subsequent generations of tools will be able to code against generations of Flash players beyond the current Version 9. As Ted says, can rest easy investing in Flex today and tomorrow. In choosing Flash Player 9 for the deployment target of Flex 3.0, Adobe is making a larger commitment to supporting a longer application life-cycle.

All this suggests that, from the standpoint of developing Rich Internet Applications (RIA), Apollo and Flex will be a serious platform pairing to watch.

Twitter and the future of transmogrification

Technorati on Twitter

I proposed to Ma.gnolia a short while ago that they start using Twitter to broadcast their system status updates and they implemented it shortly thereafter.

The beauty of using Twitter is its flexibility — you can ping it using Jabber, the web, SMS or through its API. You can also receive updates through the same protocols, as well as via feed subscriptions. I call this “” — essentially the ability to morph data between forms and through various inputs.

It seems that others are picking up on the trend towards Twitterification — and I find it very interesting, especially as the differentiation between bot, aggregate and human is essentially nonexistent. Was it a service, a friend or one of many friends pinging you just then? One never knows!

So far I’ve found these non-individual, non-human Twitterers

Organizations & Companies

Weather

I’m sure there are more, but do you know of any more that I missed?