It's really all just about the ride

And the winner of the Firefox Flicks Video Contest is: <drumrolls> Daredevil, by Pete Macomber </drumrolls>


Watching that reminded me of Waking Life. The part where the girl in the Daredevil video says:

It's really all just about the ride.

reminded me of the man in the boat/car saying:

The ride does not require an explanation. Just occupants.

:)


The one part from Waking Life that keeps playing in my head these days given where I currently am in my life is something the now late UT Austin philosophy professor Louis Mackey says:

... So what are these barriers that keep people from reaching anywhere near their real potential? The answer to that can be found in another question, and that’s this: Which is the most universal human characteristic - fear or laziness?

hmm...

Here's a synopsis and the script but I highly recommend watching Waking Life, if for nothing else but the innovative animation and rotoscoping technique that gives the movie a surreal feel in keeping with the protagonist's persistent dreamlike state.


Oh, and dont forget to check out the second place winner of the Firefox Flicks Video Contest "Wheee!" by Jeff Gill. It cracks me up! ROTFL! =))

Browser URL Size Limits

Via Rules for Bookmarklets:

Browser	Max chars
Netscape	> 2000
Firefox	> 2000
Opera	> 2000
IE 4	2084
IE 5	2084
IE 6	508
IE 6 SP 2	488
IE 7 beta 2	2084

The evolution of Web Design

• web2.0 logos!


• The Logos of Web 2.0 - A breakdown of the fonts used in some of the above logos.


• The Elements of Typographic Style Applied to the Web - a practical guide to web typography

Totally tripping on the new new media

[Video] YouTube: Man dancing

That's an ex-programmer (Matt Harding) who quit his job and used his savings to travel around the world! Why?




[Audio] Odeo: Return From Madness - where have I been?

A bizarre adventure caused a long absence. I do my best to explain where I’ve been for three months, without mentioning any names. I lost myself and am only just now coming back from a deep emptiness. A little quote from Salvador Dali, an ad for “instant problem fixing cream”, and my “Theme to Forever”, a piece I wrote 25 years ago or more...

Thats by 1-800-Weirdos: A freeform exploration of original music and spoken word, including samples from the 1-800-Weirdos voice mail. Improvisational and interactive, the weirdest podcast ever!!




[Photo] Flickr: Browser clocks at Opera



:)

Yahoo unREST

Saying that they use REST is a misnomer. What they actually use is Browserland HTTP.

Case in point:

By default, Yahoo! Web Services return output in XML format. Some, but not all, of the Yahoo! Web Services can also return Serialized PHP. To get output in Serialized PHP format, use the output=php parameter in the request:

http://api.search.yahoo.com/ ImageSearchService/V1/ imageSearch?appid=YahooDemo &query=Madonna&results=1 &output=php

The RESTful way to do this is with an Accept Request header field.

I did point this out to Rasmus during a Web Services BOF at FOSS.in to which he said that it was easier to call it REST than call it HTTP. I don't buy this. A web developer will be much more familiar with the word HTTP (the thingy you see in the address bar of your browser and in the URI I've quoted above from Yahoo!'s own documentation) than with the word REST (an architectural style for distributed hypermedia systems described in a dissertation by Roy T. Fielding).

Now that that's out of my system, I really like what they are doing with PHP, especially this. I'm using Serialized PHP for representations as well in a web application I'm working on using Inertia with the following media type: application/x-serialized-php.

The V intro

Found this via the V for Vendetta guestbook

Voilà! In view, a humble vaudevillian veteran, cast vicariously as both victim and villain by the vicissitudes of Fate. This visage, no mere veneer of vanity, is a vestige of the vox populi, now vacant, vanished. However, this valorous visitation of a bygone vexation stands vivified, and has vowed to vanquish these venal and virulent vermin vanguarding vice and vouchsafing the violently vicious and voracious violation of volition. The only verdict is vengeance; a vendetta held as a votive, not in vain, for the value and veracity of such shall one day vindicate the vigilant and the virtuous. Verily, this vichyssoise of verbiage veers most verbose, so let me simply add that it's my very good honor to meet you and you may call me V.

In simpler words:

Behold, at first glance a humble stage actor, cast against his will as both the victim and villain by the design of Fate. This mask, not just a layer of vanity, is a lasting token of the voice of the people, now gone, disappeared, as the once powerful public now honours what it used to denounce. Nevertheless, this brave return of a long-gone annoyance stands reborn, and has promised to overthrow the evil and corrupt who promote greed and protect the violent and total suppression of free will. The only choice is revenge; a committed struggle given as a prayer, not for nothing, that the righteousness of that quest will one day lead the watchful and the righteous to victory. But truly, this thick soup of words is becoming excessive for an introduction, so allow me to say I am most honoured to meet you and you may call me V.

The mind boggles!

All Things Web 2.0 - "THE LIST"

Browserland HTTP

All this talk about Lo-REST and Hi-REST is so misleading.

There arent two types or levels of REST. There are just Components that support HTTP to various degrees and that is where the problem lies.

For the most part we are trapped in Browserland HTTP:

• Availability of only a subset of the HTTP methods (GET and POST).


• Visibility/Awareness of a subset of the REST Data Elements (resource identifier and representation).


• Cookies!


• Limited or no control of conneg on the client side.


• Broken HTTP Authentication Interface.


• No true client-side state.

The people making the argument that Browserland HTTP is "what’s been proven on the web" and REST is just theory, "speculative", "unproved in practice, and unlikely to be a game-changer" haven't been paying attention.

State of REST

When you get REST and then go back to the drawing board to design your web application/service you realize that we've cornered ourselves in Browserland HTTP and that is the really tragedy of REST: The only protocol that follows the REST architectural style is crippled by its current infrastructure.