This site is made possible by member support. ❤️
Big thanks to Arcustech for hosting the site and offering amazing tech support.
When you buy through links on kottke.org, I may earn an affiliate commission. Thanks for supporting the site!
kottke.org. home of fine hypertext products since 1998.
This is a bit old (from March last year), but the most photographed city on Flickr at the time was London followed by New York, but when you take population into account, Vancouver, Amsterdam, and Las Vegas win for photos per capita.
Canon, Sony, and Nikon top the list of the most-used camera on Flickr. Nokia is #11.
This Flickr user really likes photos of people at the dentist. This one’s my favorite. (via janelle)
Judith lost her camera (and most of her pictures) on her trip to Hawaii, so she’s using other people’s photos from Flickr to produce a trip journal.
Some player names I observed while playing Fastr (a multiplayer game based on guessing tags for a selection of Flickr images) last night for about 15 minutes under my usual online nickname “jkottke”:
jkottkesucks
kottkesucks
jkottkesucksass
ihatekottke
yes no one likes kottke
For some reason, this reminds me of one of my favorite scenes from Being John Malkovich where he’s just popped out of his own head and onto the side of the New Jersey Turnpike and a passenger in a passing car says, “Hey Malkovich, think fast!” and pegs him in the head with a beer can.
Some fans of The Matrix films went to Sydney and photographed various locations that were in the first film. Photoset on Flickr.
Retrievr is a simple, amazing use of the Flickr API. You draw a little drawing and Retrievr fetches similar photos from Flickr. Photodisc, the stock photo site, used to have a feature like this back in 1997-98, but then they discontinued it (I have no idea why…it was insanely useful). One feature request…instead of a drawing, let me pick a starting Flickr photo and find me similar ones. (via mh)
Adam from Slice documented all of the pizzerias on his 8.2 mile walk to work this morning (more). (thx, janelle)
Sorry for the lack of updates…we’ve been having some trouble with the internet and I’ve been wrestling with my email for the past two days (I finally pinned it in the 8th round). If you sent me mail, I think I got it, but expect a slower than normal response…most of it will probably wait until I’m back in the States.
Been doing some reading up on Vietnam (we’re heading there in a couple of days). I’m finding that Wikipedia (Vietnam, Vietnamese cuisine) and WikiTravel (Vietnam, Ho Chi Minh City) are good sources for the 50,000 view of things, taken with a grain of salt. The guidebook is better, but it takes a lot longer for you to get the gist. Reading Wikis Pedia and Travel and then the guidebooks seems a good strategy.
Also, we’ve been Flickring photos while we’re in Asia (thank you T-Mobile for finally fixing my International Roaming), check out Meg’s and mine for off-blog goings-on. (Completely off topic, here’s some Flickr photos tagged “comic sans”.)
The funny thing about TagTagger is that it probably would be useful to tag tags; it could help tag ecosystems like del.icio.us and Flickr better determine how tagged items are related. Think of it as defining tags…the tag “andywarhol” could be metatagged something like “andy warhol nyc artist person art popculture modernart”.
A series of art projects based on Flickr. The Flickr tag cloud tshirt is clever; the printing on the shirts is reversed so that you can read them in the mirror…”the [Flickr user’s] narrative is actually addressing himself while claiming to address others”. (via ia)
You can now get prints of your photos from Flickr (in the US, more locations coming soon). You can also do a bunch of other things, like get books printed, back up your photos to DVD, and get stamps printed.
Flickr photos labeled with “cameratoss”, which result from when you set your camera to a long exposure time, click the shutter, and toss it in the air. Looks like spirograph… (via matt)
I know you’ve always wanted to play Memory with pictures of me from Flickr and now you can. Memry works with any Flickr tag.
If you’re a Flickr user, you can now get a book of your photos printed up for display on your coffee table or to put in your bathroom bookshelf. I’ve got one of these and it’s neater than I expected.
Nikon is releasing a pair of digital cameras with built-in wifi. The cameras will only send photos via wifi to a designated Nikon application, but I wonder how long it will be before someone hacks the firmware to send those photos anywhere…like to Flickr on the fly.
Flickr set of glitch art created when digital satellite TV goes a little wonky.
Here’s a fun Flickr set: objects that look like faces.
An alleged pervert on the NYC subway was caught by cameraphone and the picture was posted to Flickr. No word on an identification yet. (thx newley)
Before we get going, here are some alternate titles for this post, just to give you an idea of what I’m trying to get at before I actually, you know, get at it:
Now that your hyperbole meter has pegged a few times, hopefully the rest of this will seem tame in comparison. (And apologies for the length…I got rolling and, oops, 2500 words. But many of them are small so…)
Way back in October 2004, this idea of how the Web as a platform might play out popped into my head, and I’ve been trying to motivate myself into writing it down ever since. Two recent events, Yahoo’s purchase of Konfabulator and Google’s release of a new beta version of Google Desktop have finally spurred me into action. But back to October. At the Web 2.0 conference, Stewart pulled me aside and said something like, “I think I know what Google is doing with Google Browser.” From a subsequent post on his site:
I’ve had this post about Adam Bosworth, Alchemy and the Google browser sitting around for months now and it is driving me crazy, because I want all the credit for guessing this before it happens. So, for the record, if Google is making a browser, and if it is going to be successful, it will be because there is a sophisticated local caching framework included, and Google will provide the reference apps (replying to emails on Gmail or posting messages to Google groups while on the plane).
At the time, Adam Bosworth had been recently hired by Google for purposes unknown. In a blog post several months before he was hired, Bosworth mused about a “new browser”:
In this entry, I’m going to discuss how I imagine a mobilized or web services browser handles changes and service requests when it isn’t connected. This is really where the peddle hits the metal. If you just read data and never ever alter it or invoke related services (such as approving an expense report or booking a restaurant) then perhaps you might not need a new browser. Perhaps just caching pages offline would be sufficient if one added some metadata about what to cache. Jean Paoli has pointed out to me that this would be even more likely if rather than authoring your site using HTML, you authored it as XML “pages” laid out by the included XSLT stylesheets used to render it because then you could even use the browser to sort/filter the information offline. A very long time ago when I was still at Microsoft (1997) we built such a demo using XSLT and tricky use of Javascript to let the user do local client side sorting and filtering. But if you start actually trying to update trip reports, approve requests, reserve rooms, buy stocks, and so on, then you have Forms of some sort, running offline, at least some of the time, and code has to handle the inputs to the “Forms” and you have to think through how they are handled.
A couple weeks later, Google introduced the first iteration of their Desktop Search. To me, the least interesting thing about GDS was the search mechanism. Google finally had an application that installed on the desktop and, even better, it was a little Web server that could insert data from your local machine into pages you were browsing on google.com. That was a new experience: using a plain old Web browser to run applications locally and on the Web at the same time.
So this is my best guess as to how an “operating system” based on the Web (which I will refer to as “WebOS”) will work. There are three main parts to the system:
That’s it. Aside from the browser and the Web server, applications will be written for the WebOS and won’t be specific to Windows, OS X, or Linux. This is also completely feasible, I think, for organizations like Google, Yahoo, Apple, Microsoft, or the Mozilla Foundation to make happen (more on this below).
Compared to “standalone” Web apps and desktop apps, applications developed for this hypothetical platform have some powerful advantages. Because they run in a Web browser, these applications are cross platform (assuming that whoever develops such a system develops the local Web server part of it for Windows, OS X, Linux, your mobile phone, etc.), just like Web apps such as Gmail, Basecamp, and Salesforce.com. You don’t need to be on a specific machine with a specific OS…you just need a browser + local Web server to access your favorite data and apps.
For application developers, the main advantage is that instead of writing two or more programs for multiple platforms (one for the Web, one for Windows, etc.), they can write one app that will run on any machine with the WebOS using the same code base. Bloglines and NetNewsWire both do about the same thing and have radically different codebases (Bloglines uses HTML/JavaScript + some sort of backend programming/scripting language while NNW is a Cocoa app only for OS X), but a version of Bloglines developed for the above platform could utilize a single codebase.
You also get the advantages of locally run applications. You can use them when you’re not connected to the Internet. There could be an icon in the Dock that fires up Gmail in your favorite browser. For applications using larger files like images, video, and audio, those files could be stored and manipulated locally instead of waiting for transfer over the Internet.
There are also disadvantages to WebOS applications, not the least of which[1] is that HTTP+JavaScript+XHTML+CSS+Flash is not as robust in providing functionality and user interaction as true desktop applications written in Cocoa or Visual Basic. But as Paul Graham points out, Web applications may be good enough[2]:
One thing that might deter you from writing Web-based applications is the lameness of Web pages as a UI. That is a problem, I admit. There were a few things we would have really liked to add to HTML and HTTP. What matters, though, is that Web pages are just good enough.
Web pages weren’t designed to be a UI for applications, but they’re just good enough. And for a significant number of users, software that you can use from any browser will be enough of a win in itself to outweigh any awkwardness in the UI. Maybe you can’t write the best-looking spreadsheet using HTML, but you can write a spreadsheet that several people can use simultaneously from different locations without special client software, or that can incorporate live data feeds, or that can page you when certain conditions are triggered. More importantly, you can write new kinds of applications that don’t even have names yet.
And how about these new kinds of applications? Here’s how I would envision a few apps working on the WebOS:
I’m looking at the rest of the most commonly used apps on my Powerbook and there’s not too many of them that absolutely need to be standalone desktop applications. Text editor, IM[3], Word, Excel, FTP, iCal, address book…I could imagine versions of these running in a browser.
So who’s going to build these WebOS applications? Hopefully anyone with XHTML/JavaScript/CSS skills, but that depends on how open the platform is. And that depends on whose platform it is. Right now, there are five organizations who are or could be moving in this direction:
So yeah, that’s the idea of the WebOS (as I see it developing) in a gigantic nutshell. The reality of it will probably be a lot messier and take a lot longer than most would like. If someone ends up doing it, it will probably not be as open as it could be and there will likely be competing Web platforms just as there are now competing search engines, portals, widget applications (Konfabulator, Dashboard, Google Desktop Sidebar), etc., but hopefully not. There’s lots more to discuss, but I’m going to stop here before this post gets even more ridiculously long. My thanks if you even made this far.
[1] Actually, the biggest potential problems with all this are the massive security concerns (a Web browser that has access to data on your local hard drive?!!!??) and managing user expectations (desktop/web app hybrids will likely be very confusing for a lot of users). Significant worries to be sure, but I believe the advantages will motivate the folks developing the platform and the applications to work through these concerns.
[2] For more discussion of Web applications, check out Adam Rifkin’s post on Weblications.
[3] Rumor has it that Google is releasing an IM client soon (more here). I’ll be pretty surprised if it’s not significantly Web-based. As Hotmail proved for email, there’s no reason that IM has to happen in a desktop app (although the alerting is problematic).
[4] Maybe Google thinks they can’t compete with Apple’s current offerings (Spotlight, Dashboard, Safari, iPhoto) on their own platform, but that’s not a good way of thinking about it. Support as many people as you can on as many different architectures as you can, that’s the advantage of a Web-based OS. Microsoft certainly hasn’t thought of Apple as a serious competitor in the OS space for a long time…until Web applications started coming of age recently, Microsoft’s sole competitor has been Microsoft.
One of San Francisco’s steepest streets will be closed later this month…for ski jumping. They’re hauling in 200 tons of snow and a bunch of skiers. I’m sure this will be a much Flickred event.
Using your favorite Flickr photo, you can use this handy widget to make your very own magazine cover. I knocked up an issue of Hello, Cowboy! magazine featuring Tom Coates wearing a gigantic hat. Magazines have never been so much fun.
I thought this was going to be some sort of Flickr/del.icio.us taggy tag mashup, but Flickrlicio.us is a bunch of hot babes found on Flickr. An anonymous reader: other Flickr + hot chicks sites include FlickrBooty, chicksnbreasts, and flickrchicks. NSFW. And where are the Flickr beefcake sites?
flickrTagFight pits tag against tag in a folksonomic battle to the death. fTF has already started a conflict in my household…results of the kottke(145)/megnut(34) tag smackdown are being hotly disputed.
Positive review of Flock, a new Mozilla-based browser with drag and drop blogging and Flickring built in.
New bookmark: interesting Flickr photos from the last 24 hours, automagically determined. PageRank for photos, sorta.
Flickr reaches the 1,000,000 member threshhold. I wish Flickr publicized everyone’s number so that I could lord my early-adopter status over everyone in a more quantitative manner.
Icelandic band Sigur Ros has a Flickr account that they’re updating while on tour.
Stay Connected