PUBLIC MARKS with search guess

If it sounds like I'm saying Apache was a mistake, I'm not. Apache was a big part in the success of CouchDB, without it CouchDB would not have enjoyed the early success it did. But in my opinion it's reached a point where the consensus based approach has limited the competitiveness of the project. It's not personal, it's business.

Since the Mongol Rally is an adventure not a guided tour we un-invented the un-route. There is a place to start and a place to finish, but where you go, and what happens in between is anyone's guess. That's the whole point.

Today, fewer than 1% of iPhone, iPad, and iPod Touch owners are Instapaper customers, despite Instapaper spending a lot of time (including today) at the #1-paid-app spot in the App Store’s News category for both iPhone and iPad.

“JSON is a JavaScript subset”. Guess what? They’re wrong. Wrong, wrong, wrong.

Originally posted by obarthelemy:

My guess is Opera is missing something to account for different mouse settings.

Try reducing the Mouse Gesture Threshold to 1 or 3.

Effectivement, on en revient à un fonctionnement (presque) normal.

How to guess sameness of blank nodes?

it’s a pragmatic look at what it takes to move projects from idea to reality.

MarcoPolo brings context-aware computing to your portable Mac computer.

It allows your computer to determine its context through gathering evidence

from your environment (evidence sources), using flexible rule-based

fuzzy matching to make an educated guess (rules), and then

performing arbitrary actions upon changing context (actions).

karl dubost 0 minutos atrás I guess there are other things which might influence than only the raw number of participations. The social dynamic of Wikipedia system has evolved. The rules (like any communities) have strengthened and are more rigid than what they were in the past. It is basically more and more painful to create content for Wikipedia. As an occasional editor, I'm less and less inclined to make the effort to contribute because the article might go quickly under "Articles for Deletion" hammer.

Interesting thing to look at:

1. Timeline of Articles for Deletion (raw number and % of how many new articles)

2. Deletion compared to new contributors (stable, going down, going up)

3. Timeline should also plot the milestones of new editing rules.

4. The rate of new articles creation compared to the number of contributors.

These could drive to new processes, maybe there is a need for a better drafting tool that will help an article to reach a stage of maturity to be part of Wikipedia, and this will create another set of behaviours ;) Not a closed system.

Network Realism is writing that is of and about the network. It’s realism because it’s so close to our present reality. A realism that posits an increasingly 1:1 relationship between Fiction and the World. A realtime link. And it’s networked because it lives in a place that’s that’s enabled by, and only recently made possible by, our technological connectedness.

For each country, guess the gov domain, search on Google for "site:domain filetype:xls", then divide the results by the population. A sample of the results ordered by this ratio:

A very wise systems programmer once told me: “Don’t guess. Measure.”

answer Right. And it results in a type of error that doesn't teach you anything. You have chaotic errors where all you can say is, "Boy, this was really screwed up, and I guess I need to go in and go through the whole thing and fix it." You don't have errors that are proportionate to the source of the error. And that means you can never have any sense of gradual evolution or approximate systems. So, the real difference between the current idea of software, which is protocol adherence, and the idea I'm discussing, pattern recognition, has to do with the kinds of errors we're creating. We need a system in which errors are more often proportional to the source of the error.