PUBLIC MARKS with search aware

Context-Aware DoNotTrack is a particular implementation of Do Not Track initiative, a movement aimed at stemming the widespread use of user tracking by third party ad-networks as users surf through the web.

Octopress is a framework designed by Brandon Mathis for Jekyll, the blog aware static site generator powering Github Pages. To start blogging with Jekyll, you have to write your own HTML templates, CSS, Javascripts and set up your configuration. But with Octopress All of that is already taken care of. Simply clone or fork Octopress, install dependencies and the theme, and you’re set.

Accessibility can often seem daunting and complex but in fact there are only four types of disability you need to be aware of. Through groupings, simulations and quick fixes, UX and accessibility consultant Ian Hamilton shows that the basics are actually surprisingly simple

Jekyll is a blog-aware, static site generator in Ruby

We are now aware that the police have used traffic information that you have helped to create to place speed cameras at dangerous locations where the average speed is higher than the legally allowed speed limit.

You can chain up to six Thunderbolt devices. That’s not a problem today as we’re not even aware of six products that support Thunderbolt yet. But if the connection becomes widespread, the six device limit might be a problem for some people. In comparison, FireWire supports 63 devices and USB supports up to 127 devices.

Bah, ça n'est pas une limitation, Apple vendra à ce moment là une extension bien pratique et hors de prix pour contourner cette limitation complètement artificielle.

Dragdealer is a drag-based JavaScript component that embraces endless front-end solutions. Elegantly crafted for JavaScript-aware coders.

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).

SparkleShare is a syncing and collaboration tool that shines by its absence. it's designed to get out of

your way, to make sharing documents and collaboration easier, and to make peers aware of what you are doing.

Yahoo! PlaceFinder is a geocoding Web service that helps developers make their applications location-aware by converting street addresses or place names into geographic coordinates (and vice versa).

A Week in the Life is a visualisation of telecommunications data. The data sculpture represents my movement and communication made with my cell phone in one week. With this project I want to make people aware of the german telecommunications data retention act (Vorratsdatenspeicherung) which requires the telecommunications providers to collect the connection data of all customers, which is an unneccessary breach of privacy. What can be read from the sculpture is my position in the city through the cell sites I used.

# karl Says:

May 4th, 2010 at 12:09 am

David,

How do you handle these challenges, I can imagine, in the case of an organization like Mozilla (or any big companies).

1. Do you get reviews from the people who are supposed to work on the specific parts mentioned by the charter?

2. Do you plan in advance who will be potentially available for committing work to the Working Group (in terms of comments and spec reviews)?

3. How Mozilla validates its development choices. For example, here you’re saying “No Web SQL database, no widgets”, is it defined by the lack of resources? or by a more general technical choice in a roadmap?

That is part of the questions I always had when I was in W3C Team. Life of a working group can be really constraining for work schedules and the right balance is difficult to achieve. Sometimes 20% of time seems to be nothing. I’m painfully aware of it, now that I’m not 100% at W3C and having a swallowing-time-job.

# aruner Says:

May 4th, 2010 at 9:06 am

@karl (this is Arun responding):

1. Yes, David typically solicits reviews from folks in the WG in question.

2. Yes, we generally plan in advance who might be on call to review specifications.

3. In the case of Web SQL Database, we were pretty much mostly in consensus that hitching our wagons to SQLite wasn’t the right choice for a web API (nor was stringifying SQL statements in JS desirable to developers), and that the web needed a better database model. We think IndexedDB sounds promising. And as for widgets, we’re pretty much in consensus that there are more important things to work on.