Mozilla Archive Format, with MHT and Faithful Save :: Add-ons für Firefox. Asked about something like this today, my knowledge was a bit outdated, so I googled again and this seems to be the most interesting extension to save complete pages (including images, styles, and JS). Practical, for example, if you want to put together a dummy for presentations.
web
Social Networks and my use of them
At some point, you realize that you simply have too many places on the web where things happen and where you are somehow represented. For this reason, here is a list of the current networks in which I appear and how I actually use them (or plan to use them - not everything I want to do always works out).
- my digital home is here in the Blog. Everything possible lands here, links, images, articles, etc. If something is important enough for me to want to say something about it, I put it here - because only here do I actually have full control over my content. Some of my content is also posted to Metaowl - our small privacy aggregator.
- I also have a small Tumblelog on Tumblr. I actually only use this to post photos or occasionally comments, etc., when I'm on the go. So it is primarily fed by my iPhone.
- On Twitter is what Dave Winer calls the "Firehose". So if you want to know what I'm doing in general, wherever, you can follow my stream there. Be careful, it's really a lot - because every new service that gives me access to my activities there in any way is hooked up.
- On Flickr I have a number of photos, and I will certainly also post pictures there from time to time. Simply because sometimes I also want networking for the pictures - usually the same pictures then also end up here in the blog.
- As a social network, I primarily use Google+ at the moment. Of course, it still has some problems, but the architecture appeals to me much better than in the other networks. And the integration with Picasa of course also leads to the fact that I post pictures there.
- As social code networks, I currently use Bitbucket and Github. My open source projects land there (although I of course also have copies locally in case these hosts disappear one day). However, I currently mainly use Github to follow projects there, my own projects use Mercurial and therefore end up at Bitbucket.
- Facebook I actually don't use at all. I send some content (blog posts and, for example, Google+ updates) there, but otherwise I'm just there as a hook and for people who don't want to use my RSS feed but want to follow my content there because they are already there.
So, everyone should know where I hang out and where I appear. And now please no complaining "your Twitter stream is too full" - that's intentional. And also no "check your Facebook" - that only happens sporadically.
Tumult Hype. Interesting - I had actually expected this much earlier, a tool for creating animated presentations using only HTML5 and JavaScript. Essentially what Macromedia Director or Asymmetrix Toolbox used to be.
Its About The Hashbangs. Blogged because it is a pretty good description of what is wrong with these #! in addresses. The part after the # is only client-side, the server never sees it - any form of server-side redirection and server-side routing is completely out of the question. Also, server-side access controls are largely out of the question, the server only sees the main page. For single-page applications like TiddlyWiki, this is all fine - everything is already in one file and it is the declared purpose of these applications to be structured this way. For websites like Twitter or even news sites like those of Gawker Media, it is simply absurd. Twitter can perhaps guarantee due to its banal structure that the URLs to tweets also work with #! in the long run, in that a corresponding JavaScript part remains in the homepage forever (which is already pretty silly), but news sites will sooner or later simply drop the old #! URLs - and thus produce massive link rot.
ongoing by Tim Bray · Broken Links. Why these overused #! fragments in URLs are a big mess and why you shouldn't use them. And yes, it's annoying to rape the web - especially since there's absolutely no reason to do so, dynamic servers can easily map various URL structures. And yes, I know about the problem that you can only switch the URL in the browser in the fragment part via JavaScript, without forcing a reload - but that's no reason to convert all URLs to such a stupid fragment format.
Chromium Blog: HTML Video Codec Support in Chrome. Wow. Google is removing H.264 from Chrome's video support and fully switching to Theora and WebM.
Pure CSS GUI icons (experimental) are an excellent example of what you shouldn't do with CSS. Painting with box models is rather unproductive. But somehow it's still fascinating what some people do with their time ...
Long Live the Web: Scientific American by Tim Berners-Lee. Why the web is so important to us and why and what we must protect it. Because more and more interest groups are trying to reduce the openness of the web for their purposes, ostensibly often to protect users or rights or other great and positively sounding reasons - but behind it all is simply the grab for power that one wants or fears to lose.