This year
Facebook: Upgrading to OAuth 2.0 | Straylight Run
jQuery HTML5 Uploader
2011
schema.org - Getting Started
Code Sign error: The identity 'iPhone Developer: x Xxxxx' doesn't match any identity in any profile - Stack Overflow
Broken Links
Music Made with NYC Subway Schedules; HTML5+Flash, Q+A with Artist-Developer
steady pulse of the (actual) New York City subway system into gentle, generative string plucks in his new interactive piece “Conductor.” The visual effect as well as the musical one is mesmerizing, as the subway is viewed in the abstract, sparse geometries of designed Massimo Vignelli’s 1972 diagram.
2010
The Definitive Guide to HTML, URL and Javascript Escaping | jehiah.cz
This means you should always, and I mean ALWAYS, find yourself escaping for XHTML context, escaping for including a string in a URL, and escaping for a javascript context. Any time you output the contents of a variable, escape it.
Datejs - An open-source JavaScript Date Library
Undelete! | Atomic Object, Software Design & Development
Ben Alman » jQuery Misc plugins
:.. Portal Aprendendo Linux ..: » Ubuntu 10.4 – Trocando a ordem dos botões das janelas!
Principles for Standardized REST Authentication - O'Reilly Broadcast
a set of standards that I think should be in place for any REST authentication scheme.
Here's the summary:
1. All REST API calls must take place over HTTPS with a certificate signed by a trusted CA. All clients must validate the certificate before interacting with the server.
2. All REST API calls should occur through dedicated API keys consisting of an identifying component and a shared, private secret. Systems must allow a given customer to have multiple active API keys and de-activate individual keys easily.
3. All REST queries must be authenticated by signing the query parameters sorted in lower-case, alphabetical order using the private credential as the signing token. Signing should occur before URL encoding the query string.
Table Wizard | drupal.org
Frankie Roberto – Pragmatism in URL design
karl says:
March 2, 2010 at 11:07 am
In your paragraph
“one of the axioms of the web that URIs are opaque, and that machines “should not look at the contents of the URI string to gain other information”, but there are lots of ways in which humans don’t follow this principle”
Not only humans in fact. The first item in your list is talking about Google and it has changed a lot the way the Web is made. In commercial environments (aka Web Agencies), SEO (capacity of having a better findability) touches the content organization but also the words in URIs. So often the SEO person will not only recommend the way to architect content in the page, but also the words that must be in the URI. It is basically an additional constraint to the list you created.
* Persistence
* Readability
* Findability
Bug #292504 in gnome-exe-thumbnailer (Ubuntu): “Use embedded icons for executable files”








