This is pretty much exactly what OAuth does - enables the user to authorize a web service to access another one on their behalf, with per-app, per-user constraints.
It was used long time before that. Many TUI DOS aplications (especially Turbo Vision based or copying Turbo Vision UI style) use this character for leftmost item of menubar with "system" things and utilities like calculator (obviously inspired by Mac OS's Apple menu).
What the author misses is that with colour LCD displays you can do sub-pixel anti-aliasing with the 3 RGB sub-pixels, if you start from a vector, which is why HTML type looks better than Photoshop rendered type.
I purposefully chose to ignore subpixel antialiasing because it's complicated and you have little control over how it works. It's done at a layer further abstracted from the source file, so you can't accurately pixel-fit anything to a subpixel. It's also just another hack, using a smaller unit than a half-pixel, and, like most hacks, it has some serious negative side-effects.
He's not suggesting that you subpixel antialias manually. He's pointing out a benefit of leaving your images as vectors: the browser knows the subpixel order of the display, and can make the image prettier than you can without that information.
It can make it effectively higher-resolution than you can, but that doesn't mean it can make it prettier. It could still look end up looking worse (from the color bleeding effect, for instance).
You can't even reliably fit raster images to screen pixels on the web. Images can easily end up at non-integer screen pixel locations which requires resampling (and ruining your careful alignment) to render.
Logo design should be done in-context, not in a dark room at 400% zoom.
I contacted the curator at the Lincoln Museum by email. His response:
This is entirely a hoax. Clever, too. We have an official stastement to that effect due within the hour. -James
James M. Cornelius, Ph.D.
Curator, Lincoln Collection
Abraham Lincoln Presidential Library & Museum
112 N. Sixth St.
Springfield, IL 62701-1310 217.785.7954
http://www.alplm.org
I contacted the curator at the Lincoln Museum by email. His reponse:
This is entirely a hoax. Clever, too. We have an official stastement to that effect due within the hour. -James
James M. Cornelius, Ph.D.
Curator, Lincoln Collection
Abraham Lincoln Presidential Library & Museum
112 N. Sixth St.
Springfield, IL 62701-1310 217.785.7954
http://www.alplm.org
It's a great hoax. On the edge of plausibility, with several related verifiable facts that make it seem allllmost possible. Toss that in with the I Want To Believe syndrome, and it's bound to spread.
Sorry about "the original". It wasn't actually supposed to have that query string on the end. That was for Google Analytics tracking elsewhere and I forgot to remove it when I posted it here.
I'm not sure why it produced an redirect loop because it worked many times for a lot of people. It may have had something to do with my server getting overloaded. I'm on a Hostgator reseller account, so I have limited resources and when HG saw the massive CPU usage from all of you people checking this out, they shut down my site for a bit.
Relying on RSS feeds is tricky, as many of them are partial extracts, summaries, or just plain wrong (eg archival standalone pages linking to the current front page, stale feeds, links to now-defunct feed services).
If you want to help people writing these things, using hAtom in your HTML is a really good idea.
The thing here is that when properly used, a page can contain several pieces of text tagged as articles, especially blogs with comments (think of article as "an article of clothing", not as "a magazine article"). You'd have to rely on other heuristics to find the "correct" article, which probably is not that much easier than finding the correct div element.
Take a look for example at Fred Wilson's blog http://www.avc.com he is using the article element. You can use multiple times in different blog posts in the same web page and I don't feel this is bad.
According to MG Siegler, Chrome is in the bizdev-required proprietary 'with Google' part of Android, not the Open Source part.
http://parislemon.com/post/17215781807/chrome-for-android-th...
That means we're stuck with legacy browsers in existing Androids and in the non-Google-blessed world (Amazon Fire and the billion Chinese phones and tablets).
Interesting. The chromium blog post linked above mentions upstreaming a bunch of new components, so maybe it will be like the Chrome/Chromium situation? Here's hoping...
