PUBLIC MARKS with search created

Images created using law enforcement composite sketch software and descriptions of literary characters. All interesting suggestions considered. Include descriptive passages if you can.

The dynamic map is completely created in your browser. This has the advantage that the map is interactive, you can zoom into it, change colors, and see for every point what article it is and link to it. But it has the major disadvantage that it requires some heavy resources. This link may crash your browser. Use a reasonably fast machine, a current version of Chrome, and be patient while loading the data — your browser is loading more than 50 MB of data and processing it via JavaScript into an HTML5 Canvas.

The growing interest in both the SPDY protocol and Node.js created the need for a stable Node.js SPDY module when the first version was released last year.

Oh, the Catholic church won't be happy about this. Banksy just unveiled a brand new sculpture called Cardinal Sin which is a 18-century stone bust of a priest with its face sawn off and replaced by blank "pixelated" bathroom tiles. It was created as a response to the child abuse scandal in the Catholic church and its subsequent cover-up.

Hi, Paul. Actually, I tweeted about "Move the Web Forward" on Blue Beanie Day the moment I saw it, and I linked to it from Facebook and Google+, but carry on with the character assassination. I tweeted about it without knowing who was behind it (doesn't matter), and without being *entirely* clear what it was about (you have some copy problems I would have been glad to help with). I was pleased to discover this blog post as I thought, "Ah, now I can reach out to the people behind that site and help them publicize it more" but then, a few paragraphs in, I saw your shitty little whiney character assassination of me (quoted above) and thought, oh, well. Why do you do this to yourself? Why do you create something nice and then shit on someone else? What kind of behavior is that? You did the same thing when you complained about A List Apart even though we've reached out to you for *three years* asking you for content and input. Calling something on the web crap is always a childish move, particularly when that thing is open and your feedback and content have been solicited for it many times. I gather you have some unexplained grudge against me. Or against the young dude in Ireland who created some web standards buttons for fun. If you think my help of his project is how I earn my living, you need to get out of the cubicle more. I'm usually polite to everyone, even very rude people, but you're being both whiney *and* a dick, which is a hard combo most people to pull off (fortunately most people don't try). Your project looks cool and could benefit from outside help, but I won't be helping because you are an asshole. You are, I think, the only asshole I've met in 20 years of doing web work. Fuck off.

LLOVE is an exhibition consisting of a hotel with guest rooms created by Dutch and Japanese designers to celebrate 400 years of trade and cultural relations between Japan and the Netherlands.

I've created this page to attempt to convince you. It shows examples and lists six reasons why it's a good idea and three common arguments against them (some of which I refute).

Wiring is an open source electronics prototyping platform composed of a programming environment (IDE), an electronics prototyping board, documentation thoughtfully created with designers and artists in mind and a community where experts, intermediate and beginners from around the world share ideas, knowledge and their collective experience.

The common conception among Web designers is that a good style sheet is created by hand, each curly bracket meticulously placed, each vendor prefix typed in manually. But how does this tradition fit in a world where the websites and applications that we want to create are becoming increasingly complex?

here is the proposed sequence of steps in this scenario: clients GET the template and a token from the factory resource. since this operation does not change server state, it is safe and idempotent and it is possible to use GET. clients PUT to the token URI, at which point the server creates and populates the resource at the repository level, and keeps track of the token from which the resource has been created. the server responds with a 303 (See Other) response, indicating the persistent URI of the resource. subsequent requests to the token URIs are handled with a 301 (Moved Permanently) response, telling clients that the token URI should no longer be used, and that a persistent URI is now available.