myOpenID.com is dead. OpenID is dead. Long live Web Sign-In. #indieweb #indieauth

I got an email saying the service will end on 2014-02-01, but the site appears to be down already. janrain.com, the company who apparently ran myOpenID, is also down, so I can’t find a “goodbye” post. Here’s the notification email:

I wanted to reach out personally to let you know that we have made the decision to end of life the myOpenID service. myOpenID will be turned off on February 1, 2014.

In 2006 Janrain created myOpenID to fulfill our vision to make registration and login easier on the web for people. Since that time, social networks and email providers such as Facebook, Google, Twitter, LinkedIn and Yahoo! have embraced open identity standards. And now, billions of people who have created accounts with these services can use their identities to easily register and login to sites across the web in the way myOpenID was intended.

By 2009 it had become obvious that the vast majority of consumers would prefer to utilize an existing identity from a recognized provider rather than create their own myOpenID account. As a result, our business focus changed to address this desire, and we introduced social login technology. While the technology is slightly different from where we were in 2006, I’m confident that we are still delivering on our initial promise – that people should take control of their online identity and are empowered to carry those identities with them as they navigate the web.

For those of you who still actively use myOpenID, I can understand your disappointment to hear this news and apologize if this causes you any inconvenience. To reduce this inconvenience, we are delaying the end of life of the service until February 1, 2014 to give you time to begin using other identities on those sites where you use myOpenID today.

Speaking on behalf of Janrain, I truly appreciate your past support of myOpenID.

New profile photo practise: colour on my #indieweb site, B&W on other identities. Next is some way to differentiate between other identities which I only #POSSE to and those which I still host content on (e.g. soundcloud)

One Indie Web Camp UK spot left, then we move to waiting list. Get in there quick, it’s going to be great: indiewebcamp.com/2013/UK

On Friday I made a bunch of @indiewebcamp badges in preparation for IWC UK — thanks @piratepartyis for letting me use your space :)

Join us in Brighton on September 6th-7th to get hold of one — or, print out your own (here’s the PDF).

Which website creation/hosting providers have beautiful set-up experiences?

I just faked having a task queue for #taproot #indieweb note posting tasks using Symfony HttpKernel::terminate() and it was the easiest thing ever.

Instances or subclasses of HttpKernel have a terminate($request, $response) method which, if called in the front controller after $response->send(); triggers a kernel.terminate event on the app’s event dispatcher. Listeners attached to this event carry out their work after the content has been sent to the client, making it the perfect place to put time-consuming things like POSSE and webmention sending.

Once you’ve created your new content and it’s ready to be sent to the client, create a new closure which carries out all the the time consuming stuff and attach it as a listener to your event dispatcher, like this:

$dispatcher->addListener('kernel.terminate', function() use ($note) {
    $note = sendPosse($note);
    sendWebmentions($note);
    $note->save();
}

Then, provided you’re calling $kernel->terminate($req, $res); in index.php, your callback will get executed after the response has been sent to the client.

If you’re not using HttpKernel and HttpFoundation, the exact same behaviour can of course be carried out in pure PHP — just let the client know you’ve finished sending content and execute code after that. Check out these resources to learn more about how to do this:

• FPM, specifically fastcgi_finish_request()
• flush()
• HttpFoundation\Request::send() as a sample implementation

Further ideas: if the time consuming tasks alter the content which will be shown in any way, set a header or something to let the client side know that async stuff is happening. It could then re-fetch the content after a few seconds and update it.

Sure, this isn’t as elegant as a message queue. But as I showed, it’s super easy and portable, requiring the addition of three or four lines of code.

Testing posting #indieweb videos via email and the iOS camera app:

Aw, the upload worked but embedding didn’t. Here it is:

This evening’s #indieweb activity was moving a load of the photos in the posts I exported from Diaspora onto my own server so they don’t get lost if/when diasp.org goes down.

The webaction toolbelt can also do select-to-quote:

Previously: Quoting UI #indieweb #webactions

Taking distributed #indieweb actions on your own site, in context? Yes, webaction toolbelt does that:

To clarify, this is a page on news.indiewebcamp.com which supports inline webactions. When I click “Reply”, a pre-populated new note form from my own site is loaded into an iframe. It detects this, and adjusts its styling accordingly.

“For a platform to be reliable, it must either have a single implementation, or be so utterly simple that it can be implemented uniformly. If we assume a practical need for open, freely implementable standards, the only option is simplicity.”

Magic Ink, @worrydream #indieweb #tech