dave winer: deadness.
many nice pictures taken from the book of personal computing history.
yeah, yeah... and next they will break the internet – wait, what?
on 8 june 2011 is world ipv6 day – and there is no plan b!
dave meslin: “the antidote to apathy” (only 7 min tedx talk, via molochronik.)
faceback made it into yesterday’s issue of web app development daily.
with or without much further ado.
i created my first sproutcore application: faceback.
it empowers every facebook user to reclaim their data for their own purpose!
well, actually that means all posts of a profile at facebook.com can be copied to an antville weblog – and currently even more specifically: to one very chosen antville weblog inside the antville.org testing environment.
to get things started you need to be logged in to both, facebook and the virtual antville site. then navigate to faceback.antville.org and you should see all (or at least: most) of your posts in your profile.
selecting a list item from the left pane should highlight it and display the actual post contents (date, title, probably an image with a link etc.) – which then can be imported to the antville site clicking the “import” button.
please check it out (but be aware you are about to free your content from the ghetto!) and feel free to post a comment and let me know how it works for you. praise is always welcome!
of course, the goal is to import to your very own antville weblog – but that still needs some polishing in the antville codebase.
regarding sproutcore i must say the developers did an amazing job (thank you very much!) but the sproutcore documentation totally spoils the fun i tried so hard to have during development.
as you might have already guessed it: documenting javascript certainly is b-r-o-k-e-n!
this is becoming a mini series here.
also broken: certificate revocation. (maybe even the general idea of certificate pki.)
more breakage.
while david teller quite reasonably analyzes that “web development is just broken”, other folks are trying to break the whole web by breaking the hypertext transfer protocol with so-called hash-bang uris:
“the problem with this is that the response is no longer representative of the content. i will receive response 302 found for something that is completely different than the actual content. this is where the problem lies to me.” — david coallier.
amongst that hash-bang gang is google.com with their hilarious attempt to index javascript-driven sites by adding a “highly intuitive” ajax url rewriting technique.
(well, maybe this technique is not so hilarious at all, at least it requires only one url entry point – well, maybe a few – for satisfying google’s crawler. on the other hand: why is not google using a headless browser themselves?)
anyway, where are we lost in web development and where are we going with it? did we somehow miss an important turn?
jeni tennison summarizes the situation very comprehensively, although i am left with suggestions for good practice that make browser hell sound like heaven again.
all i can see is paramount cluelessness and disapproval, neither a heads-up for current practices nor a de-facto standard, a reliable way of solving these issues.
of course, saying the web is broken actually means the web is undergoing fundamental changes. someday somebody might come and fix this. or, more likely, we will see an evolutionary outcome, the survival of the fittest. (practice, that is.)
Venkatesh Rao: Tempo.
