The Internet Archive discovers and captures web pages through many different web crawls.
At any given time several distinct crawls are running, some for months, and some every day or longer.
View the web archive through the Wayback Machine.
Just noticed a new addition to Ubuntu: PowerNap. I have a server that I use to offload running some tests from my primary development machine. I start jobs via a web interface, and they retrieve the sources to test using git and svn. The net result is that there is no keyboard or mouse activity, not even ssh.
PowerNap’s value proposition is that it monitors processes, looking for arbitrary regular expressions, and considers the presence of matching processes as activity. Simple and effective.
PowerWake determines and caches MAC addresses, simplifying wakeup.
Monthly, the Apache Software Foundation has a board meeting, and the work flow that leads up to this is that a rotating selection of Officers prepare written reports and either commit them directly to subversion or email them to a mailing list where they will be picked up.
It is an unfortunate truth that a number of these officers are still using proprietary operating systems and tools. The end result is predictable: a file which contains a number of encoding errors.
Joe Armstrong: After a small amount of experimentation I was able to make Erlang talk to a web page using pure asynchronous message passing. I think this means the death of the following technologies:
comet
long-poll
AJAX
keep-alive sockets
I see the appeal for a single node Erlang or Eventmachine or node.js server. (Can sockets be passed between servers?)
I’m less clear about how this could work with request/response servers like PHP or Rails. Event loops on the server are not typically application patterns for applications using such frameworks — shared nothing is more of the norm.
CouchDB crossed my radar just over two years ago, a few months later, Damien was at IBM, it entered incubation at the ASF a little over a month later. It has been an exciting project to watch.
My role was simply as a catalyst at a few junctures.
Lately I’ve been moving around more between my netbook, laptop, and desktops, so having any single machine being designated as my mail portal at the moment often means that I often don’t have convenient access to my email.
I figured it was time to investigate running my own mail server.
Sometimes the answer to information overload is to seek more information.
I’ve been trying to track the changes to both Rails 3.0 and Ruby 1.9.2 which affect Edition 3 of Agile Web Development with Rails, as well as track both with my work on Edition 4. Depot Dashboard is a static snapshot of the result, updated frequently throughout the day.
Jacques Distler: To borrow a phrase from Samuel Johnson, “… like a dog’s walking on his hind legs. It is not done well; but you are surprised to find it done at all.”
Jacques has a way with words. It does seem to me that collaboratively editing complex formulas and simple diagrams would be one of the use cases for Google Wave, yet I can see the vast number of separate problems that need to be solved in order for this to be addressed ubiquitously (i.e. using only the browser that the user happens to have in front of them at the time).
Aurélio, Küng, Stärk, Uña, Łuksza, these are but a few of the names of contributors to the ASF. Names which contain non-ASCII characters. Characters that subversion doesn’t deal with consistently between Mac and other platforms.
The Wikipedia entry for Umlaut indicates that there is set of rules for mapping such characters to ASCII for Telex devices, but I have been unable to locate these rules. Anybody have a pointer?
There are times when the scalability I care about is the ability to scale down. For many applications, one request per second is more than enough, as the application has few users, often only one. These applications tend to contain all of the same types of bits that “real” applications do: markup, stylesheets, server side logic, and client side logic; just generally not enough to spread across multiple files.
Simon Phipps: Your browser doesn’t seem to support HTML 5 (or perhaps the Ogg Theora standards) so you’re missing the embedded video here.
Excellent presentation (and excellent means of delivery via the web) by Simon. His thesis is that a license is a necessary but not sufficient indicator of openness in a community. (Related: Mark Wielaard points out a contemporary example [via Dims]). In my opinion, whether Simon’s got all of the details right isn’t the point, the point is to start a conversation on this important topic.
Incidentally, I was cameraman for this particular video, a task which entailed my pushing a single button and then holding a flip video recorder for approximately a half hour.
Slides from a presentation that I should be giving in just over two hours.
Static rendering and HTML-syntax compatibility turned out to be useful as I could simply place my presentation on a flash drive and copy it onto the machine provided for presentation (also running Ubuntu), and then launched using firefox agenda.
I’m sure that there is a rhyme or reason to this, but for the life of me I can’t imagine what it would be. If anybody has any insight as to what it might be, suffice it to say that I am very curious at this point.
X3Dom works today in nightly builds of FireFox 3.7, and makes use of a namepsace and mixed case element and attribute names in XHTML. We will be discussing this tomorrow.
CollabNet: The CollabNet-sponsored Subversion project and The Apache Software Foundation (ASF) announced today that the award-winning Open Source project has formally submitted itself to the Apache Incubator in order to become part of the Foundation’s efforts.
Mark Pilgrim: Anyone who tells you that HTML should be kept “pure” (presumably by ignoring browser makers, or ignoring authors, or both) is simply misinformed. HTML has never been pure, and all attempts to purify it have been spectacular failures, matched only by the attempts to replace it.
I strongly agree with Mark’s statement. Furthermore, I believe that it is a useful predictor of which parts of HTML will ultimately succeed and which parts will ultimately fail.