| Display name: |
|---|
Your comment:
Please enter the text in the image above here:
2010/9/17
Dark Patterns is a list of deliberately deceptive or user-hostile website/interface design patterns, used by unscrupulous operators to deceive or exploit unwary users. These range from honest-but-hamfisted attempts to corral user behaviour into profitable channels (i.e., making it inconvenient to compare prices; sites which use JavaScript-based navigation to frustrate opening links in other windows do this) to various more underhanded tricks, ranging from sneaking unwanted items into shopping baskets, adding unsolicited recurring charges to spamming your friends under false pretexts to generally making it hard for the user to unsubscribe or do anything that reduces turnover. Featured offenders include the likes of Ryanair, various travel and consumer electronics retail sites, and Facebook (who get their own entry):
“The act of creating deliberately confusing jargon and user-interfaces which trick your users into sharing more info about themselves than they really want to.” (As defined by the EFF). The term “Zuckering” was suggested in an EFF article by Tim Jones on Facebook’s “Evil Interfaces”. It is, of course, named after Facebook CEO Mark Zuckerberg.
(via Boing Boing) ¶ 0 Share
2010/6/18
The age of vector graphics on the web is drawing closer; Raphaël is a JavaScript library which gives you a portable way of drawing vector graphics, not only on all modern browsers but, amazingly enough, on Internet Explorer from version 6 upwards. (It uses SVG on modern browsers and VML on Microsoft's ones.) Anyway, Raphaël code looks like:
var paper = Raphael(10, 50, 320, 200);
var c = paper.circle(50, 50, 40);
c.attr({fill: "#000", stroke: "none"});
c.node.onclick = function() {
c.attr("fill", "red");
});
It also handles images, text, and paths (using the SVG path notation). And here is a set of free icons, all implemented as path strings for use in Raphaël; they look fairly neat and modern, though, being single path objects, are monochrome. Being paths, though, they scale seamlessly.
So how soon can you use this in your web sites? Well, it runs with most of the web browsers in use these days, though needs a 55Kb (20Kb gzipped) JavaScript file. You'll probably need to host this file yourself, neither Google nor Yahoo! seem to have added it to their public CDN systems yet (though perhaps it's only a matter of time).
2010/6/16
Some good news from London: Transport For London, who run the city's public transport networks, have announced that they will be opening access to all their data by the end of June. The data will include station locations, bus routes and timetable information, and will be free from restrictions for commercial or noncommercial use.
The data will be hosted at the London DataStore, a site set up to give the public access to data from public-sector organisations serving London. A few sets are already up, as well as a beta API which returns the locations of Tube trains heading for a specific station. Which could probably be worked into a mobile app to tell you when to start walking to the station. If they had something like this giving the positions and estimated arrival times of buses (whose travel times are considerably more chaotic than those of trains, and which often run less frequently, especially at night), that would be even more useful. (Some approximation of this facility exists in the LED displays, which are installed at some bus stops and sometimes are operational; a XML feed and a mobile web app would probably be a more cost-effective way of getting this information into the hands of commuters.)
Another thing that would be useful would be an API for the Transport for London Journey Planner; being able to ping a URL, passing an some postcodes or station names, a departure/arrival time and some other constraints, and get back, at your option, a maximum journey time or a list of suitable journeys, in XML or JSON format, would be useful in a lot of applications, from device- or application-specific front ends (i.e., a "take me home from here" mobile app) to ways of calculating the "inconvenience distance" between two points by counting travel time and changes (i.e.,in terms of travel convenience, Stratford is closer to Notting Hill than Stoke Newington, despite being further in geographical terms, as it's a straight trip on the Central Line).
2010/6/4
Some increasingly impressive things are being done with modern web browsers these days, taking advantage of new features in HTML5. A guy named Ben Joffe has developed a number of demos, including a full-featured 3D function plotter (using the canvas element) and a toroidal Tetris game. Another developer, going only by the name "Mr. doob", has developed some nifty 2D physics demos, including Ball Pool and Google Gravity. (Google, of course, entered the fray recently with their pure HTML5 implementation of Pac-Man.) Meanwhile, Apple, who are fighting their own (quite laudable, IMHO) battle against the dominance of Flash, have their own showcase of HTML5's capabilities, though it's coded to refuse to run on non-Safari browsers.
Chrome or Safari are recommended for the above demos; Firefox is still lagging behind in speed, though that's likely to improve in the near future. Firefox also has a new, experimental, API for manipulating audio data in JavaScript. (Apparently people are going to be doing FFTs in JavaScript in the future, which presumably won't make your browsing experience any faster.) It requires custom developer builds of Firefox (i.e., it's only for the hardcore at the moment), but people are already starting to experiment with it. Potentially most impressive so far is a project to port the Pd graphic audio programming language to JavaScript and have it run entirely in a browser. Meanwhile, here are some more audio API dems, including ones combining the audio APIs with WebGL to present 3D landscapes which respond to the beat in music and and graphic equalizer, sampler and speech synthesiser written entirely in JavaScript. I wonder how long until someone writes an entirely HTML5-based Ableton Live-style sequencer.
Typography is also shaping up nicely under HTML5, with a standard embeddable font format agreed upon. Google have released a web font embedding API, and made available several free font libraries through their content distribution system. They look, well, like free fonts; for those wanting more (and willing to pay for it), other groups of type foundries are jumping on the bandwagon; fonts.com has fonts from major foundries like Linotype, Monotype and ITC (at last, you can set your site in authentic Helvetica for people who aren't Mac owners), and über-cool Berlin-based outfit FontShop have joined the game as well (bringing the clean European stylings of the likes of FF DIN and FF Meta to the web). One notable omission, though, are 1990s grunge-typography hellraisers Emigre, who haven't yet made the leap.
Finally, here is an article on some of the things one can do with CSS3, from transformations (i.e., rotating entire elements, including text and layout) to keyframe animation, all done without a single line of JavaScript.
2010/2/25
The momentum towards proper typography on the web continues: now the FontFont type foundry, best known for clean, European typefaces like FF Meta and FF DIN as well as several Neville Brody geometrics, is selling web embeddable versions of its typefaces. The fonts are sold in DRM-free WOFF (the new open standard, currently in Firefox 3.6, but undoubtedly soon to make it into the WebKit browsers) and EOT (the Internet Explorer font format), which may be linked from style sheets. How much you pays depends on what license you get, and how many page views your site gets, and users are expected to configure their web servers to only give access to the fonts if the referrer matches the site (which won't stop anyone with a copy of curl or wget and half a clue from illicitly downloading them, but will stop other websites from casually sponging off your site's fonts). More details are here.
Which is a good start. Now if a few others like Emigre would join the @font-face party, then things would get more fun. (If Adobe made their fonts available for CSS embedding, non-Mac users might see this blog in Gill Sans, but that's probably not going to happen, as it's in Adobe's interest to keep HTML nobbled and divert those wanting more control to PDF or Flash.)
2010/1/13
What purports to be an interview with an anonymous Facebook employee, shedding some light on the inner workings of Facebook, technical improvements, privacy, and the more unusual dealings with its millions of users:
How do you think we know who your best friends are? But that’s public knowledge; we’ve explicitly stated that we record that. If you look in your type-ahead search, and you press “A,” or just one letter, a list of your best friends shows up. It’s no longer organized alphabetically, but by the person you interact with most, your “best friends,” or at least those whom we have concluded you are best friends with.
I’m not sure when exactly it was deprecated, but we did have a master password at one point where you could type in any user’s user ID, and then the password. I’m not going to give you the exact password, but with upper and lower case, symbols, numbers, all of the above, it spelled out ‘Chuck Norris,’ more or less. It was pretty fantastic.
I found a fake account created from Berkeley that used the profile picture and information from the brother of one of my very good friends. We looked up the guy who created the original profile, and he had never ever heard of him, never ever met him, obviously had never seen him. But this guy had evidently added him as a friend, and sadly he accepted it, but literally stole all of this guy’s information, created a fake account, and was communicating with himself from the fake account. He was writing on his wall and posting back to the “other person’s” wall. We found out the guy actually had about fifteen fake accounts that he created, stealing other users’ pictures and information to create the accounts, and was actually communicating back and forth with himself. Just to try to make himself appear cool, I guess?The unnamed Facebook employee also says that they're working on something named Hyper-PHP, which will compile PHP (which Facebook is written in) to machine code, which, they claim, will reduce CPU usage by 80%.
2009/11/3
Type foundries and browser makers have agreed on an open embeddable font format for the web. The Web Open Font Format, developed in collaboration by parties including the Mozilla project and geekier-than-thou type foundry LettError (which was cofounded by one Just van Rossum, whose brother created a somewhat popular programming language), is essentially a repackaged, compressed variant of TrueType/OpenType.
Somewhat surprisingly, it not only contains no DRM (which would have been a deal-breaker for open formats; Microsoft tried introducing an IE-only DRM-locked TrueType variant, but wasn't successful), but also contains all the data that a desktop font does, only slightly rejiggered to make it unusable in existing desktop systems. (I'll give them a week before someone writes a script that rips WOFF fonts to TrueType fonts.) This is surprising because the commercial font industry, producing something that's labour-intensive and skill-intensive but infinitely copiable, has until now jealously guarded its intellectual property, refusing to license its fonts for embedding in desktop formats. Instead, now they're keen to license them in slightly obfuscated versions, with the understanding that browsers enforce a same-origin linking policy unless there is additional license information. (I was thinking that, if the industry wasn't keen on letting its vector fonts out onto the web, it could have been possible to devise a resolution-limited font format, based on several sizes of bitmaps, with vector hints (i.e., "pixels 36-40 are a vertical stroke"), and generate all intermediate sizes using an interpolation algorithm. Such fonts would, of course, degrade if scaled above the maximum resolution in the file.) Another rationale could be that the market for web fonts could eclipse that for print fonts, and web font licensing would be easier to enforce (web sites, after all, are findable, and presumably unlicensed fonts would be easy enough to detect).
Licensing issues aside, WOFF promises to provide more than merely letting you put your favourite fonts on your web site. While Firefox 3.6 will have basic WOFF support, the next version of the specification promises to give more control, allowing web designers to fine-tune typographical parameters, selecting alternate forms including ligatures, different types of figures (lining and old-style, tabular and proportional), proper small caps, alternate figures (such as swash capitals) and such.
2009/10/19
Travel search engine of the day: Adioso. This is a new natural-language-based flight search system. It differs from sites like Kayak in that, rather than accepting simple queries in a set of fields (origin, destination, dates), it accepts queries as natural-language sentences, and allows a good deal of fuzziness. So, for example, if you want to go from London for a weekend in Barcelona in late November, you can ask for "London to Barcelona weekend late November", or if you just want to get out cheaply, you can ask for "London to anywhere under GBP100".
Well, you can if your destination is supported. The site appears to be Australian, and thus Australia and popular destinations from there (south-east Asia, the UK and US, and places along the "Kangaroo Route" to London) are well supported, while Europe (minus sunny holiday spots) is a bit patchy. The site found no flights from London to either Berlin or Stockholm, and drew a blank altogether at Reykjavík (the closest match it could find was Tel Aviv; I guess that sort of sounds like Reykjavík, if you're shouting across a noisy room or something). Flights across Australia it handles well, though, finding better prices than Kayak. In any case, the site claims to be in beta (though whether it's an old-fashioned beta or a Google-style permanent beta is uncertain), so with any luck, they'll improve it.
2009/10/15
2009/8/8
HTML5 Canvas and Audio Experiment. Twitter posts presented as a clickable particle swarm, with background music, and absolutely no Flash used. It's done entirely in HTML5, and, of course, needs a cutting-edge web browser to run on (Firefox 3.5 and Safari 4 both work, and so do Chrome and Opera, apparently).
The demo seems to be based on something named processing.js, which is, apparently, a port of Processing (i.e., a Java-like language for software artists) to JavaScript.
2009/7/14
Web interface of the day: A Chinese company has unified isometric pixel art and Google Maps-style draggable maps to make pixelicious city maps.
They have a map of Hong Kong in English, and maps of other Chinese cities (Chinese only; Google translation here). Not sure if it's much more useful than a 2D map, but it sure looks pretty.
Now perhaps someone can commission eBoy to do one of Berlin. Or of the internet.
2009/6/11
Two years after last.fm was bought out by CBS, who ran it as an autonomous unit, the three founders have handed in their resignations; they will stay on as consultants until September, after which control will be handed over entirely to CBS. After that, we can probably expect the servers to be boxed up and shipped to the US and the site to be rebranded as "MTV Online" or something, plastered with intrusive ads, and generally stripped of anything that made it cool in the first place.
So where do you go after last.fm? How do you display the superlative coolness of your musical taste to the world once last.fm is no longer fit to point people at? Well, there's libre.fm, which is still in alpha, doesn't look very good and has next to nobody using it. Libre.fm, though, is open-source, so you could easily run your own server. Perhaps the future will consist of people running their own scrobblers, or social networks providing scrobbling services to their users; your music stats will be available as standard XML feeds, with a XFN-style microformat link from your profile/homepage, letting the world know that this is what you've been listening to. Of course, one advantage a centralised site like last.fm had was that it could easily crunch the data and find recommendations or determine the compatibility of musical tastes, though if it's a web service, someone could write a third-party site to crunch exported music profiles. (Perhaps that someone will be Google or Facebook? Or perhaps Murdoch's struggling MySpace will leap at the opportunity, implement scrobbling, and then make a hash of it with obnoxious in-your-face Flash ads and a garishly unpleasant user experience.) As for finding upcoming gigs, event sites like upcoming.org, or Facebook's Event facility, could be expanded to be aware of band/artist names and search by user profiles.
2009/4/8
We haven't had a Wayne Kerr post for a while, so one is overdue. Anyway, I am Wayne Kerr, and if there's one thing I hate... it's websites attempting to coerce you into registering.
A while ago, there was an online newspaper named the International Herald Tribune. Owned by the New York Times but published in Paris, it was quite a good paper, with fairly incisive articles not too far from Economist territory. Then someone at head office decided to kill the brand and roll it into the New York Times brand, and iht.com became global.nytimes.com. And, with that, inherited the New York Times' draconian insistence on users requiring to register and log in to view their their precious content.
The New York Times, you see, is not satisfied with the standard online news business model (make their content freely viewable and linkable and sell ads to those surfing in on web links from wherever in the world they may be); that may be good enough for rabble like their London namesake, but the NYTimes' content is worth more than that. At the start, they even tried charging for online access to it. Of course, as Clay Shirky points out, this is not a viable business model for online news (current events cannot be copyrighted or monopolised, and someone can always do it cheaper), so the NYTimes soon dropped the demands for subscription. However, they have doggedly kept the other part of the equation: the insistence on users subscribing, remembering yet another username and password, and giving a valid, verified email address, as well as some juicy demographic information. Of course, there are ways around this; the most popular site on BugMeNot, a website for sharing free usernames/passwords to such sites, is the New York Times. However, such accounts usually have a very short lifespan; either they perish when the email verification period lapses or, failing that, the Times' web admins hunt them down and kill them, like an ongoing game of Whack-a-Mole.
The New York Times, however, is not the most irritating example of coercive registration; that accolade would probably go to a site named, ironically, Get Satisfaction. This is an external tech support site, used by a number of web 2.0-ish sites, including SoundCloud and ping.fm. As a web site, it is the very model of a modern website; rounded corners, quirky retro fonts (oh so San-Francisco-via-Stockholm), pastel-hued gradients, animated fades, you name it, it ticks the box; it would be perfect, but for one fatal flaw in the human interface design.
What somebody neglected to notice is the typical use case of such a site. One doesn't go to Get Satisfaction to socialise with friends, share photos or music, find a date or a flat, or do anything one does on a typical social web site; one goes there when one has gone to such a site and found that it doesn't work properly, and wants to notify somebody to fix this. Now when that happens, the last thing one wants it to have to think up another username and password, and be cheerfully invited to fill in one's profile and choose a user icon representing one's personality. As far as support forums go, less should be more, and Get Satisfaction, for all of its pretentions to being some kind of online clubhouse, falls short.
Not everything that isn't charged for is without cost; there is a cost, in time and finite mental resources, to keeping track of usernames and passwords. (Of course, you could use the same password across all sites, but that replaces a psychological/time cost with the security risk of all one's passwords being compromised.) And sites which put registration speed bumps in their users' way could find users going elsewhere where offers a smoother ride.
2009/1/28
Remember Muxtape, the web site where you could upload MP3s of songs you liked to make a virtual mix tape to send people, until the RIAA decided that it was too useful for them to not get paid for it and shut it down? Well, it's back, sort of. Or rather, there is a new site at muxtape.com. This time, you can't upload your stolen MP3s for anyone to criminally enjoy, but if you're in a band or make music, you can put your own music up for people to stream. Just like MySpace, only without the spammy Flash ads and generally atrocious user experience.
I was thinking that "Muxtape 2.0. Less sucky than the new Napster" would be a good slogan for it, but on reflection, this sounds needlessly sarcastic. How about: "Muxtape 2.0: less sucky than the new Napster or MySpace"?
2009/1/25
Some interesting notes from a talk about the scalability of social software delivered at the Web 2.0 Expo last September by Joshua Schachter of del.icio.us:
There are 3 Kinds of scale: technological, social, and personal. We’re going to briefly go through the technical stuff... Common access pattern is to have a screen, make a modification, requery the data, and then resend the results. We’re building a lot of these systems to be synchronous which is a huge performance hit. What you need is a queue not a database for processing messages asynchronously. Decouple interactive performance from the rest of the system. Huge win for Delicious. Now that we’ve got technical stuff out of the way…
Don’t go too far and expose too much information. A long time ago you could see how many friends you had and how many followers you had and compare who it was that was following but not a friend. The system allowed me to get angry at two people. People got freaked out by people ‘follow’ing them on delicious.
Wanted delicious to be a harmonious system. That’s why there were no conversations. Didn’t want people to come in and have religious wars. You have to be willing to deal with abuse, spam, porn, etc. His last year this got really bad.
Pretty urls are important. It’s prime advertising space. People will copy paste and link.
(via
substitute) ¶ 0 Share
2009/1/7
LiveJournal sacks almost its entire US workforce, including all US-based engineers, leaving only a few financial and support staff. Panic ensues, with perverts worldwide stocking up on emergency supplies of Harry Potter slash fiction in case it disappears.
Chances are, the obligatory jokes about disturbing online subcultures aside, LiveJournal won't disappear overnight. For one, the cuts are in the US office, and LiveJournal is now Russian-owned, and is much bigger in Russia (in America, the typical LiveJournal user is a thirtysomething goth-scene veteran with an IT job, whereas in Russia, it's a mainstream media site). Given that most of the money and ad revenue come from the Russian operation, it presumably won't cost them much to keep running an English-localised rump site on the same servers.
In any case, I hope LiveJournal survives, because it has one thing none of the other sites have: no, not Harry Potter slash fiction; fine-grained social-network-based access control, i.e., the means to specify that posts are not just friends-only but only accessible to a subset of friends. Which might sound like a symptom of some kind of geek social neurosis, but is actually useful. (Consider, for example, a Facebook friends list, containing everyone from coworkers to family members to people you met at a party or festival; as on Facebook, you can't control who can read a posted item (it's all your friends or no-one), there are a lot of things you cannot or should not post; from boasting about faking illness to planning surprise parties for contacts, to discussing personal situations, so your Facebook stream becomes a stream of lowest-common-denominator banalities.) Something with Facebook-level usability and LiveJournal-level access control would actually be useful; maybe once the world emerges from the New Depression, someone will write something like that?
2008/12/10
The latest experimental technology to emerge from Google's labs is something called Native Client. This is an experimental means of running web content in native machine code in a web browser. It's X86-specific (so users of PowerPC Macs and the numerous ARM-based portable devices are out of luck here), though other than that, completely portable; the binaries are in a special format, and get a limited number of system calls standardised across Linux, OSX and Windows. There is even a version of Quake which will run in a browser, in any of these systems, should you have the plugin enabled.
Of course, by now, you're probably thinking "Are they crazy? That's the worst idea since nuclear-powered airliners". Google, though, claim that they have a robust security model. The instruction set available is restricted, with constraints placed on the format of the code, allowing a code inspection process to detect any dangerous instructions. Google argue their case in a research paper; I'm not sufficiently familiar with recent x86 assembly language to verify their claims, but it looks like they certainly put some thought into it. Of course, there are a lot of very bright people in places like Russia, Romania and China who would also put a lot of thought into it, to entirely different ends, so there are reasons to be concerned.
Why are Google doing this? Well, firstly, it must be said that this is an experimental project, and not a finished product. However, I doubt that this is to allow better animated web ads. For most user interface content (video, animation, &c.), Flash and such are sufficient. Where this is a big win is in CPU-intensive processing tasks, which are too expensive to do in JavaScript (even if compiled to native code through Google Chrome's V8 just-in-time compiler) or Flash. (At the moment, with fast machines, one can just about do audio synthesis/processing like Hobnox Audiotool in ActionScript; however, this is quite expensive in terms of resources.)
Where something like Native Client would really come in useful would be for coding web-based applications that do real heavy lifting without handing tasks off to a well-resourced server or relying on them being coded into Flash; for example, image editing or video editing as a web service. Google's paper presents a diagram of how such services would look; the front end would be written in JavaScript and/or Flash, whilst the native x86 code would sit in a separate, sandboxed Native Client process, performing the gruntwork on demand: rendering graphics, processing video, synthesising sound, animating the exploding heads of zombies or whatever is required. C/C++, in this case, is kept firmly under the stairs, with the UI code being left to higher-level languages.
Of course, such an idea opens all sorts of strategic possibilities for Google; if it works, it would reduce the desktop operating system to a commodity. If any kind of application can be used as a web service, why buy a copy of Windows (or a PC with the Microsoft Tax in the price)? In fact, why bother installing a full-scale Linux? They're already starting to make PCs with cut-down instant-on operating systems (typically Linux-based) in the ROM, so that if you can't wait for your Vista box to finish booting, you can boot into the instant OS and get a web browser. Now, imagine a box like this, only with the OS being able to run web apps at native speed, perhaps in an application-oriented browser like Chrome. Could this be the much talked about "Google OS"?
2008/11/19
Melbourne's community radio station 3RRR now has a new website. The new site appears to look somewhat more polished than the previous one, both visually and in terms of the design. (The URLs, for one, are clean, rather than being PHP scripts with CGI arguments tacked onto the end.)
The playlists linked from the program guide now go all the way back to the dawn of time (or 2004, in any case). (They had those playlists online in the old site, but the only way to get at them was to manually try different numbers in the aforementioned CGI arguments; here, they're indexed in nicely paginated indices going as far back as necessary.) Here is the first International Pop Underground playlist they posted online; it's interesting to note that Carew played My Favorite's Homeless Club Kids and various Stephin Merritt-related projects that week.
Also, RRR's website will have a subscribers-only section, which will apparently include expanded audio archives. Not sure what exactly this will entail, or indeed what Australian copyright law will allow.
2008/11/10
Are you trying to write something (a novel, perhaps, or a thesis) but are having trouble sitting down and getting the words out? Write Or Die could be useful. It's a web toy which uses operant conditioning to force you to keep churning out the words, or else...
Consequences:I wonder how long this is integrated with other forms of productivity tools, such as software development project trackers. Perhaps we'll soon see a "Code Or Die" plugin for Trac?
- Gentle Mode: A certain amount of time after you stop writing, a box will pop up, gently reminding you to continue writing.
- Normal Mode: If you persistently avoid writing, you will be played a most unpleasant sound. The sound will stop if and only if you continue to write.
- Kamikaze Mode: Keep Writing or Your Work Will Unwrite Itself
2008/9/3
WIRED has a piece by Steven Levy looking behind the scenes of Google's Chrome web browser project:
Because Chrome was supposed to be optimized to run Web applications, a crucial element would be the JavaScript engine, a "virtual machine" that runs Web application code. The ideal person to construct this was a Danish computer scientist named Lars Bak. In September 2006, after more than 20 years of nonstop labor designing virtual machines, Bak had been planning to take some time off to work on his farm outside Århus. Then Google called.
Bak set up a small team that originally worked from the farm, then moved to some offices at the local university. He understood that his mission was to provide a faster engine than in any previous browser. He called his team's part of the project "V8." "We decided we wanted to speed up JavaScript by a factor of 10, and we gave ourselves four months to do it," he says. A typical day for the Denmark team began between 7 and 8 am; they programmed constantly until 6 or 7 at night. The only break was for lunch, when they would wolf down food in five minutes and spend 20 minutes at the game console. "We are pretty damn good at Wii Tennis," Bak says.
Speed may be Chrome's most significant advance. When you improve things by an order of magnitude, you haven't made something better — you've made something new. "As soon as developers get the taste for this kind of speed, they'll start doing more amazing new Web applications and be more creative in doing them," Bak says. Google hopes to kick-start a new generation of Web-based applications that will truly make Microsoft's worst nightmare a reality: The browser will become the equivalent of an operating system.
Google also brought in reinforcements to implement the multiprocess architecture that allowed each open tab to run like a separate, self-contained program. In May 2007, it acquired GreenBorder Technologies, a software security firm whose technology was designed to isolate IE and Firefox activities into virtual sessions, or "sandboxes," where malware intrusions couldn't mess with other activities or data on your computer. When the deal was announced publicly, tech pundits wondered whether it meant that Google was going into the antivirus business. Only after the acquisition did GreenBorder's engineers learn that their job was to construct sandboxes for the tabs of a new browser. "It was confusing," says Carlos Pizano, one of the GreenBorder hires. "They would not say what they wanted to sandbox."Meanwhile, the Chrome beta's licensing agreement apparently gives Google rights to use anything you create using it for promoting its services. This alarming clause appears, however, to be the result of an oversight; the licensing terms appear to have been copied from Google's web applications, and make little sense for a BSD-licensed open-source web browser (after all, anyone who doesn't like the EULA could produce an EULA-free though otherwise identical version of the browser merely by recompiling it from the source).
2008/9/2
Google are apparently working on a new web browser. Named Chrome, the browser is designed more like an operating system which happens to be based on web technologies like DOM and JavaScript than a traditional browser; different pages are separate processes (and about time, too) and privileges are compartmentalised to fortify security. Meanwhile, the web rendering implementation is based on WebKit (the Apple/KDE open-source web engine), with a JIT-compiling JavaScript engine optimised for application from a Danish company named V8 (I wonder how it compares to Apple's Squirrelfish and Mozilla's new engine). Alas, there's no code available (and the URL given returns a 404); instead, Google have given us a beautifully drawn 38-page comic by Scott McCloud, illuminating the technical innovations and the reasons for them, in great detail and with no small amount of humour:
That's all the detail that seems to exist so far. There is a possibility that it's just an elaborate feint; Google could, in theory, have paid McCloud some huge sum to draw a comic to specification, peppered with technical versimilitude, purely in order to send Microsoft/Apple/Yahoo!/whoever's development teams on a wild goose chase. Though I suspect that there is an actual product there. For one, Google are known to use WebKit on Android.
More importantly, though, a browser designed as a web application operating system (with the expectations of performance and stability that implies), rather than an information viewer with programmability grafted on as an afterthought (as is the case with current browsers), would line up rather nicely with Google's strategy to make the web into a first-class application platform.
There are no details on what platforms Chrome will run; it is open-source (and other projects, or those willing to fork those, will probably have a field day with this), and the comic does mention Windows in one place, so presumably a Windows version is planned. I'm guessing that Google aren't doing this to help Microsoft sell Windows licences, though, so presumably this is not the only version planned. A Linux desktop version, running on top of X, is probably likely. Another possibility is it running over something lighter than the average Linux desktop, making a robust web-browsing appliance on which the browser meets the conventional definitions of an operating system; either Android or some other lightweight OS.
The other option, of course, is that this is an elaborate hoax, akin to the Photoshopped "spy photos" of new Apple Mac tablets and other fantastic gear that are a regular feature of gadget blogs. The fact that Google's Chrome page doesn't yet exist (at time of writing) does suggest this possibility. Though this would imply that the hoaxers had an enormous amount of time on their hands, excellent comic drawing skills and an uncanny mastery of the drawing style of Scott McCloud.
Update: Google have confirmed Chrome. It's initially a Windows product (presumably to win market share before IE8 comes along and shuts off Google's oxygen with its advertising cookie blocker), though Mac and Linux versions are in the works. The Windows version will apparently be out tomorrow.
2008/8/26
OpenTape is a open-source (PHP-based) implementation of the late lamented Muxtape, a web app which allowed people to make streamable online mix tapes. Now you too can get taken down by the RIAA.
2008/7/23
A few years ago, a few geeks in the UK, displeased with the Ordnance Survey's hoarding of taxpayer-funded mapping data, decided to do something about it, and so OpenStreetMap was born. Based on the same principle as Wikipedia, it used the power of internet-based grass-roots organisation to allow people to make their own maps, walking roads with GPS units, uploading the traces and giving them names. Out-of-copyright vintage maps and donated satellite data, among other things, helped a bit.
As you can imagine, in the early days, it wasn't much to look at. There were networks of roads, though most of them weren't named, and a lot were missing. You could sort of make out where you were, if you knew the place well. The interface was also somewhat slow and clunky, compared to Google Maps (a variation on whose draggable-tiled-map theme it was).
After a year or two, I looked at OpenStreetMap again today, and the story couldn't be more different. Where once was a slow, unusably incomplete tangle of rectilinear spaghetti, now there are street maps, as comprehensive and neatly rendered as Google and Yahoo!'s efforts, animated with a fast, responsive JavaScript interface (nothing you won't be familiar with if you haven't used Google Maps). Scrolling around the UK and zooming in on London brought familiar street plans, albeit in a new rendering. In fact, the (rather nifty) real-estate search mashup Nestoria even have a parallel version of their site which uses OpenStreetMap; the user experience is virtually identical to the main, Google Maps-based one. (For what it's worth, Nestoria uses something called Mapstraction, a browser-side JavaScript library that allows different mapping providers to be used interchangeably, but I digress.)
And as cool as a free-as-in-libre map of Great Britain might be (to one who lives there: pretty cool; your mileage may vary), that's not the extent of it. The OpenStreetMap project's scope is global; the developers created a canvas the size of the Earth's surface, with land masses and the locations of cities filled in, and allowed volunteers to contribute to it, wiki-fashion. Soon, OpenStreetMap had maps for Europe, North America and Australia like the commercial competitors. More interestingly, places which, to the big boys, are terra incognita often show up (in varying degrees) on OpenStreetMap.Some are impressively comprehensive; for example, OSM's maps of Reykjavík (and, indeed, Iceland's second city, Akureyri) and Buenos Aires are as thorough as anything you'd expect from Google, were they to bother. Harare, whilst looking quite sparse, is more detailed than on Google's maps, and the Papua New Guinean capital of Port Moresby seems fairly comprehensively drawn. Even Pyongyang has a surprising amount of detail (though one probably can't blame OpenStreetMap for most of the streets being seemingly unnamed); I imagine that as soon as North Korea allows unrestricted tourism, long before the first McDonalds goes up, tourists will be dragging cached OpenStreetMap tiles on their jailbroken iPhones as they negotiate its broad Stalinist boulevards.
Being based on free data, OpenStreetMap has other advantages over its commercial cousins. Each map comes with an Export tab, which lets you grab the displayed area in a variety of formats, from rendered pixmaps to SVG or PostScript to the actual raw data. With it being under the Creative Commons, you are free to do as you like with the data (subject to a "share alike" proviso if you commercialise it). And with it having the agility of the Wiki age, OpenStreetMap is starting to steal a march on its competitors; for example, it was the first map to show Heathrow Terminal 5 correctly.
Of course, OpenStreetMap is by no means perfect. parts of the world are still uncovered (much of the Russian interior), or only covered with major roads (much of Africa). And their rendering algorithm doesn't seem to do Chinese or Japanese characters, rendering most of China's place names as rows of boxes. (If one is picky, one could request transliterations of foreign character sets; perhaps this could be done as user-selectable layers.) There is no route-finding capability (of the sort that Google Maps has). But all in all, OpenStreetMap is very impressive, and a spectacular success.
2008/7/11
In an attempt to combat the more-megapixels-is-better delusion, the popular camera review site Digital Photography Review has added a new statistic to its camera specification databases: pixel density:
Pixel Density is a calculation of the number of pixels on a sensor, divided by the imaging area of that sensor. It can be used to understand how closely packed a sensor is and helps when comparing two cameras with different sensor sizes or numbers of photosites (pixels). Because the light collecting area and efficiency of each photosite will vary between technologies and manufacturers, Pixel Density should not be used as an absolute metric for camera quality but instead to get an impression for how tightly packed the imaging chip is.Tellingly, looking at the specs of the compact cameras I've owned, pixel density is one thing that's only getting worse. My current compact, a Canon PowerShot A570IS, clocks in at 29 MP/cm2, considerably behind its predecessor, a PowerShot A620 (19MP/cm2). Though it still does better than its immediate successor (with 32), and even Canon's high-end compact, the PowerShot G9, gets a marginally better 28. In contrast, my venerable old four-megapixel PowerShot G2 got 10 MP/cm2—which is almost in the DSLR ballpark—and it showed in the dynamic range and colour reproduction. Granted, it didn't fit into a pocket (unless one was wearing a large overcoat), but the photos did look good...
Hopefully the megapixel race-to-the-bottom will soon end as the public becomes aware of the fact that there is such a thing as pixel density and that it affects photo quality. Then maybe we'll see a new crop of 6-megapixel compacts, and a public that's aware that they actually take better pictures than higher-density ones.
(via
reddragdiva) ¶ 0 Share
2008/6/17
The New York Times has a piece on the works of Paul Otlet, a Belgian who, between the late 19th century and World War 2, invented early forms of hypertext, search engines, the semantic web and even social software. Of course, not having digital computers to work with, his "Mundaneum" had a vaguely Terry-Gilliam's-Brazil quality about it, relying on telegraphs, vast numbers of index cards, armies of clerks and analogue terminals referred to as "electric telescopes".
The government granted them space in a government building, where Otlet expanded the operation. He hired more staff, and established a fee-based research service that allowed anyone in the world to submit a query via mail or telegraph — a kind of analog search engine. Inquiries poured in from all over the world, more than 1,500 a year, on topics as diverse as boomerangs and Bulgarian finance.
Since there was no such thing as electronic data storage in the 1920s, Otlet had to invent it. He started writing at length about the possibility of electronic media storage, culminating in a 1934 book, “Monde,” where he laid out his vision of a “mechanical, collective brain” that would house all the world’s information, made readily accessible over a global telecommunications network.Alas, when the Nazis took Belgium, they destroyed most of what he had achieved and he died a broken man, all but forgotten until a graduate student found what remained of the Mundaneum in 1968. 10 years ago, a museum dedicated to Mr. Otlet's singular vision was established:
The archive’s sheer sprawl reveals both the possibilities and the limits of Otlet’s original vision. Otlet envisioned a team of professional catalogers analyzing every piece of incoming information, a philosophy that runs counter to the bottom-up ethos of the Web.
Just as Otlet’s vision required a group of trained catalogers to classify the world’s knowledge, so the Semantic Web hinges on an elite class of programmers to formulate descriptions for a potentially vast range of information. For those who advocate such labor-intensive data schemes, the fate of the Mundaneum may offer a cautionary tale.
2008/5/4
Microsoft has abandoned its attempt to buy Yahoo!, having failed to reach an acceptable price and decided against a hostile takeover (which would have involved the legal equivalent of house-to-house combat and probably ended up with most of Yahoo's best people leaving for Google or someone). Across the world, millions of Flickr and del.icio.us users (particularly those who don't use Windows) breathe a little more easily.
Of course, it's not necessarily over; Yahoo's share price will almost certainly slump in the short term, and if their attempts to turn their business around don't bear fruit, Microsoft could come back a few months later and pick them up for less. Unless, of course, they buy AOL instead.
2008/3/26
Muxtape.com is a new web application which allows users to make online mix tapes by uploading MP3s, which then can be arranged into a "mix tape" people can listen to online. It gets bonus points for the interface, which has a minimal elegance about it and does everything other than the actual music playing in DHTML. On the down side, you only get to put 12 MP3s in your mix, and are not supposed to have more than one mix.
(For what it's worth, my one's here.)
2008/1/18
Yahoo has announced that it will be an OpenID provider, allowing users to log into OpenID-enabled sites using their Yahoo ID. Of course, as Yahoo want everyone to have a Yahoo ID (which gives them clout in targeted advertising), they have no plans "at this time" to accept OpenID logins from other providers.
2008/1/9
Something I didn't know until today: the Facebook API includes a complete SQL-style query language for querying one's social graph, which allows you to do things like:
SELECT name, pic, status, music FROM user WHERE uid in (select uid2 from friend where uid1 = 1234567890)FQL, as it's called, can be called from the Facebook API, or you can play with it here (using the fql.query method).
2007/12/29
| Display name: |
|---|
Your comment:
Please enter the text in the image above here: