Tag Systems "are supremely responsive to user needs and vocabularies (...). (T)ransforming the creation of explicit metadata for resources from an isolated, professional activity into a shared, communicative activity by users is an important development"
Folksonomies könnten ähnlich wie natürliche Sprachen wachsen, sich verändern und sich verbreiten. Die Tagger sollten sich höchtens locker an einigen wenigen, einfachen Konventionen orientieren.
Chain.js – Data Binding Service for jQuery Chain.js is a jQuery plugin, providing unobtrusive data-binding capability that allows you to generate web contents automatically by binding your data to html. Unlike other data-binding frameworks and library, it uses pure DOM, instead of string-based innerHTML approach, so event binding won’t gone during rendering. This library can also be very helpful if you strictly separate your data from your HTML, e.g. developing using MVC-Pattern
Folks. "promote exploration and learning as users browse related topics, tags, and users. (...) users have the opportunity to locate new resources that they might not ever have come across through searching."
* MakeCloud simplifies adding a cloud to any web page. Give it an RSS feed, and it makes a link cloud that summarizes the contents of the feed, and provides code to embded the cloud * FeedMarklet instantly creates an RSS feed and a browser button. You click the browser button to add whatever page you are currently reading to the feed. It is faster and easier to save links, because you do not have to interupt your browsing flow to go to a different website, and it automatically extracts information to save you the effort of entering it manually. * Video Lecture Database is a collection of links to streaming video lectures on subjects ranging from quantum mechanics to literature. The lectures are tagged. * The WizzardWiki is a power user's wiki- no stripped down markup here, just raw HTML, with real-time previews. * Hebbalicious is an experimental link cloud. Links get bigger when clicked, and anyone can submit a link. The cloud sorts out the rest.
February 17th, 2008 A 'problem' with the Mongrel/Rails platform A request comes in to the web server, and if it's dynamic, falls down to a waiting mongrel process. Mongrel calls Rails which wraps a big lock around most of the request/response cycle so the mongrel thats serving the request has to wait for a response from Rails to unlock and start serving other requests. This is the Blocked Thread stability anti-pattern that Michael Nygard talks about in Release It!. The problem is that Nginx or Apache doesn't know that a mongrel is blocked and keeps blindly sending requests. Thats means that even a single blocked mongrel will result in some slow responses for requests that come in to that same mongrel. Cut the Request Fat And one way to do that is to use the "Skinny Request, Fat Backend" principle. What that means in practical terms is pretty simple: Do as little as possible inside of the Request/Response cycle.