Awesome to see the #indieweb featured in Wired! Now, if they would also adopt some basics like mf2, or accepting webmentions, it would be even better :-)
The auth dance is too complex and does not add much value to me since the trust in #indieweb is at the domain level anyway. If you are worried, you could make the 'obscure' url something like url + token for one time use (but that requires a backend to keep track of token and generate them).
Happy to implement it if you move forward!
It's an impressive tool, works like a charm, provides me with similar data than Google, and at least it runs on my server, and the data is stored in my database.
Great discussion between Tantek Çelik and Brett Slatkin about the #indieweb and the upcoming indiewebcamp. They discuss the latest progress, like inideauth and indiecomments. I'm making a surprise appearance towards the end of the interview :-)
Unfortuntaley I won't be in Portland, but I'll try to join online and I hope to receive many new indiecomments on this post. This is gonna be fun!
I just need to decide myself to switch my email provider and logout from Google/Facebook/etc for good. That's another work in progress.
If you are curious about the indieweb, checkout http://indiewebcamp.com and join #indiewebcamp on #freenode.
Ho boy, was I proud of this title ^^^ and blog post by @scobleizer. It was on May 22nd 2010, exactly three years ago. Facebook was engulfed in a major privacy scandal, the Diaspora team was wrapping up an amazing kickstarter campaing and Google was having multiple "social web" sessions at I/O and I had just been interviewed by Robert on the topic of Federated Social Networks and presenting him our work on Onesocialweb.
It felt like a perfect storm for making Federated Social Networks happen. Yet.. three years later, this dream feels further away than ever. What went wrong? Where do we go from here?
What went wrong?
Although many things eventually played against the various projects, I think we can single out three key factors:
- Loosing the leaders: A big chunk of the thought leaders got hired by major companies in a very short period of time. In fact, most of them went to Google.
- Analysis paralysis: Although we shared the same goals, the Federated Social Web community got quickly paralysed by endless debates on how to get there. XML vs JSON vs RDF, email vs uri identifier,etc...
- Building Cathedrals: We were too busy architecturing the perfect protocols and not paying enough attention to the developers (and the challenges of interoperability) and the end users.
I think this last point is crucial, and was nicely phrased by @tomcoates as the following (in CAPS indeed :-) : "THINGS THAT USERS DON'T UNDERSTAND THAT DON'T MAKE MONEY **DO NOT SUCCEED**. THEY GO BUST OR FALL AWAY AND GET REPLACED BY THINGS THAT DO MAKE MONEY AND THAT USERS GET!"
What next then?
Well, over the last months I fell in love with the #indieweb community. Which, could be summarized as: "stop talking, start coding". The idea is simple: get your own domain, host your site there, and slowly work towards federating with others.
Instead of focusing on protocols, it focuses back on YOU and your needs. You get immediate value out of it (you got a blog) and you make exciting progress with a community of likeminded folks. As an example; a couple weeks ago, we managed to federate 5 different implementations around a single comment thread. Yes, this stuff is real.
I also like the 'low-tech' approach of the indieweb. Instead of complex API, we rely on the web and some simple markup in html pages to share content in an interoperable way.
A company that was the cheerleader of the open web is rapidly turning its back on every single open standard they once championned. Their latest move, announced yesterday at Google I/O, appears to be closing XMPP server-to-server federation.
It is only a natural next step in a process started a while ago. Here is a quick, and probably not exhaustive recap:
- Google+ has no open RSS output, hence no PuSH support, no write API, in fact it has absolutely nothing open
- Google Reader is scrapped, along with RSS support within Chrome
- WebDav CalDav for Google Calendar is dropped in favor of their proprietary API
- XMPP is dropped, while 3 years ago it was at the core of their Wave efforts
This is what email would have looked like if it were invented in the Web 2.0 era. By aaronparecki.com
- Indiewebcamp: reclaim your social identity and content
- Unhosted: serverless web services
- Freeyourspeech: distributed communications
Update (May 19th 2013):
1) Two additional movements worth having a look at:
- W3C Federated Social Web community group: developing Best Practices for the Open Social Web
- Autonomo.us: Working towards free network services
2) It seems RSS in Chrome is back and that was a mistake. In addition, some users argued that CalDav support is not dropped but replaced by an "OAuth enabled" version and that it should not be a cause of concerns for third party developers. Not sure about that last one.
No silos, no paywall, no control by a single entity or government. Pure freedom, at least as pure as emailing or calling someone.
I love it :) When are you joining the conversation ?