[+]Twitter Add to Google! Add to My Yahoo! Subscribe with Bloglines

September 2006

Google’s New Reader Still Sucks

29

September

With great anticipation I logged in to give the new Google Reader a try and I have to say I'm disappointed.

I'm finding it slow and lacking in any real feed management. Yes I have labels… but delete an entire labels group of feeds easily? No chance. I can't even do a label:labelname search to narrow subscriptions by label to delete them. Only keyword searching seems to work. Bugger that for a joke.

The whole reader feels slow too. A couple of times my browser displayed the dreaded blank icon in firefox's titlebar.
I can't river of news read my feeds by label either - only by the time they came in. Crap.

The ONLY feature that I can see that I like and came up with the idea of a long time ago - is the "mark as read" as you go. That would be invaluable for me in Bloglines which is so much nicer to read in.

The reader also forces me read one item at a time. I hate that. I friggin scan everything I read because I read that much so the fading out slightly of messages not currently in focus is a pain. Not to mention the way the feed entries are individually wrapped inside a border. There are too many little things to distract the eye. Those silly stars, those little expand post arrows. Those borders.

It's not a nice experience.


Tim Bray talks with Scoble

27

September

Tim talk's where the action is at!

Atom (APP)
Dynamic Scripting Languages (Python's my favorite)
Concurrency (Whee Twistedmatrix)
Stevey talks up Javascript and Rails

I like his points about JSON. Makes me think about YAML and the recent talk of the Semantic Web failures. I keep thinking of a not-well-thought-out queriable JSON datastore.

Rails may well be all that, but it ain't it all. Personally the Ruby syntax sucks enough for me to avoid it until I have to use it. Performance and libraries feel lacking.

Thinking out loud.

JSON > Content Repository > JSON > Client

SQL > Content Repository > JSON > Client

XML > Content Repository > JSON > Client

Binary > Content Repository > Client

XMPP > Content Repository > XMPP > Client

XMPP > Content Repository > Bayuex > Client


Bored - Nothing Interesting Happening in the World of the Web Today.

20

September

Seems like it has been a slow week. I'm not feeling challenged and I'm questioning whether I'm maybe over all this. All the pieces as to the future of the web are feeling like they've been filled in. All that's left now is to pull all the widgets apart and throw them together in more interesting ways. As things are they're plain dull. I can't get anything done…saying that I have been exceedingly depressed all week so could be biased. :)

The only subject I haven't really written about I had been meaning to (I think I have a draft of it unfinished - yeah, I do) is the web vs desktop app schmozzle.

Everything boilds down to the fact that while we have different desktop platforms without any form of networkable standard and different brower rendering engines and interfaces (waves at XUL), that's how things will stay. A schmozzle.

Unless one of the big desktop companies wake up (hello microsoft and XAML) and standards push something, developers are doomed to cross-browser web development and all that limits them.

Now with Firefox 2 finally having storage coming, and others likely to follow suite, we can expect a bigger emphasis on scripting languages inside of the browser and, eventually, the browser becoming the next desktop. A javascript derivative to interface them all. Yet another layer upon that layer in the form of subscripting languages as processors, process on new levels.

God, why bother even writing this shit.

All I really ever wanted the web to do was connect me better, which with all the layers of complexity now feels even more alienating in doing than it was previously.

With so many distractions, people don't have the time to write anymore. 


Human Augmentation though User Experience (UX)

11

September

Increasingly I find myself discussing the future of where decentralised technologies are headed. Increasingly I find myself discussing User Experience - my loathe for it with many of the current technologies.

With layer upon layer being added to the technology front, and tools such as those for rapid development taking steps to easing the burden on web developers, user experience is emerging as increasingly important to me.

Applications and user interfaces are becoming increasingly complex, cramming feature after feature into smaller spaces, and now with mobile techology really taking flight, increasingly I see the need for seamless user experience development environments.

Creating a seamless layer between application developer and application designer will become evermore imporant.

I've been reading a lot about REST lately, REST being at the heart of how I see decentralised systems evolving. The first step in the process towards what Rohit Khare calls AR+REST+ED Development(PDF). Asychronous, Routed, Representational State Transfer, Estimated, Distribution. I can't help but mention the WAKA protocol Roy T. Fielding has published some thoughts on here. What a cool name for a protocol.

What has occurred to me is the connector based approach of such a system. As standards emerge and are pushed, asychronous technologies such as the Bayuex Protocol and Comet for ajax, XMPP for messaging. JCR170 & JCR283 for Content Repositories, XML, RDF, Atom and many others. It has occured to me how much of a pivotal role user interfaces will have in tieing all of these technologies together in a manner that becomes a seamless experience for application designers in rapid appication environments. The technolgy is increasingly becoming transparent, accessed through universal connectors allowing increased productivity and creativity, its the interfaces that can take these to the next level.
This for me is the future of the internet. Creating seamless User Experiences in aide of augmenting humans. A lot of pioneering work in the area being done by Doug Englebart. The mother of all demo's a must see. As is Hyperscope.

It's creating that layer of seperation that has me excited as to where things are headed for ease of use and wide-spread adoption of technologies that allow users to communicate their ideas with like-minded others effectively. Creating connections and meaning in the process.


The Identity Event Horizon and Aggregating User Attention Data

11

September

An area I'm been working on recently has to do with storing my own personal attention data in a way that affords me ease of management through a centralised event history.

It works in a way that is much like Dave Winers concept of a river of news. The newest events appearing at the top of the list, an area I like to call "the event horizon." Recently I read Dave's interpretation on Mobile Rivers and it had me thinking. Thinking; "thats only partly how I want to do things."

Here's an excerpt from his example:

How mobile Rivers work

A scenario
Here's a scenario. Taking a trip. The plane lands, out comes the Blackberry. Check the voicemail, check email, then… What's next? For me it would be to check the news, find out if anything happened while I was in the air. Did a scandal break? Another terrorist attack? Any interesting Apple rumors?

Not how I want to do things because if infers seperation between my attention data (phone, email, news) and their alert interfaces. I want them all in one interface. Increasingly I've begun to curse my email reader, news reader, and other seperation. The sheer volume of information to wade through is becoming unmanagable. What with the 10's of mailing lists I'm now subscribed to in addition to the feeds I read in my news reader - jogging back and forth between email, mailing lists, news, SMS, missed calls is becoming a pain to manage. I want it all in one. The problem is how to manage it together.

Increasingly I find myself gravitating to my feed reader in a river of news fashion for consuming as much of my attention data as I can. This has me thinking about the interface a lot and what I really need in there. What information is important to me and how best to present it.

The more I think about the idea of an Event Horizon extending my news reader, the more I like it.

Here's how it works.

All of a users attention data is aggregated into a single event history feed. Recent email, news feeds, missed phone calls, identity requests for link contracts, calender appointments, todo events, bill payment alerts. All in a river of news format. Newest events at the top of the list in the event horizon.

Events could be made sticky by type based on filters, additionally event types could be filtered by type through tags. eg. only listing recent email. With personal meme engines (like Sam Rubys) integrated as types of data streams and given event horizon priority aswell. Not to mention other statistical information aggregation based upon ones personal attention data should the user want that.

I see something like this integrating as a central point with a users identity broker. A users event horizon stickying recent requests for identity link contracts. An interface for sharing certain private data using Identity Rights Agreements.

The beauty for me with this system is that users could access their news reader, emails, missed calls, identity information all through the one prioritised river of news or the filters. All on a mobile device if they so choose to.

Want to approve a purchase and trust your credit card to someone whether it be a retailer or online service? Simply tell them your digital identity, an example being an i-name;

=firstname.lastname

(if only XRI would have native browser support soon :)

Their identity broker then sends your identity broker a payment details request that appears in your event horizon allowing you to use either your mobile device or a terminal to approve/disprove your credit card details transaction. Creating a link contract in the process based upon an Identity Rights Agreement

Perhaps using your thumbprint on a device that your identity broker has approved for thumbprint authentication.
By clicking on differnet types of requests in your aggregator, you could be either diverted to the appropriate client for that type of event, whether that be your email client, news reader, calender or Identity Rights Agreement broker. Personally I'd like them all integrated in an Ajax style interface manner whereby I click reply to reply there and then in my river of news to an email thats just come in, or an SMS that has. Or to expand to read comments on a post and reply. I'd like to see the latter done using something like Atom's Threading Extension and the Atom Publishing Protocol to post those comments.

This all requires a way to send XML data securely across networks. On that topic, Jason Kolb has been discussing his future of the internet, a discussion I have been following with interest. He has the idea of using XMPP as the messaging protocol between identity servers. It will be interesting seeing how this can be done securely. i-names, XDI is doing something silimar as I understand it, and something I'd like to understand better.

When it comes to security, I can't help but think that data-mining will surely play a role here.

In conclusion, I want one interface for events, an interface to action those events important to me.

The Event Horizon.


Identity Rights Agreements

11

September

Jon Udell discusses digital identity with Phil Windley.

Among many topics discussed, one of particular interested to me was what Phil calls Identity Rights Agreements:

IRAs are patterned after the Creative Commons [CC05], which gives users an easy way to assert ownership of intellectual property (IP) and to selectively claim specific rights associated with that IP. Creative Commons (CC) uses a four layer stack to communicate the claims:

  1. Easily recognizable logo
  2. Human readable agreement
  3. Legal document layer
  4. Machine readable metadata

This stack provides superior usability because of layers one and two, but couples those in a structural way with the legal language and machine readable metadata. One key difference: CC is based on copyright law, whereas IRAs would be based on contract law.

Like CC, IRAs would come in a limited set of configurations. This limited set of configurations allows users to quickly and easily assert (or accept) a well-known and understood set of terms regarding the use of their data. For example, here is a potential spectrum of choices that might be represented by a set of standard identity rights agreements.

  • Post publicly (broadcast)
  • Share with anyone, but may not broadcast
  • Share with partners with whom you have a legal contract to honor this agreement
  • Share with no one
  • Store encrypted
  • Use for this purpose and destroy

The above are just examples. The Identity Commons community is working to gather requirements and legal advice for the initial set of IRAs. Still, the idea should be clear: a simple taxonomy of increasing protection requirements that users can assert about their identity data.

Getting this right will be a crucial part to seeing adoption through a simple User Experience anyone can understand. I hope they consult their mums on this. :)


My Favorite Tech Buzzwords

08

September

Just for fun, here's a list of my favourite tech buzzwords at the moment:

  • waka
  • HTTP
  • ReST
  • ARReSTED
  • JSR170
  • OCC
  • APP
  • XMPP
  • BitTorrent
  • RDF
  • Atom
  • OWL
  • SPARQL
  • RDFa
  • microformats
  • WSGI
  • Python
  • Twisted
  • MVC
  • transcode
  • OpenID
  • Yadis
  • JSON
  • YAML
  • AJAX
  • Comet
  • Live Clipboard
  • Thingamy
  • Hyperscope
  • CoDIAK
  • SPADE
  • Widget
  • API
  • UX
  • PUI

Others I considered including: XRI, XDI, i-names, SSE, RSS, OPML, WebDAV, llup, XML, XSLT, XML Encrypt, XML Signatures, XHTML, CSS, tagURI,

Two months ago I hadn't heard of 90% of these. So much to learn.

Do you have any you think should be on my list? Please add them in my comments!


Recent Links

Recent Links

-->
Recent Comments
  • Craig Overend: Fixed, thanks Josh. English and explaining myself clearly has never been a strength of mine. Glad you...
  • Josh: Hey, just wanted to point out it should be "you're", as in "you are". Otherwise, wow - very in depth post....
  • Joe Andrieu: Craig, As I've mentioned elsewhere, user-driven is a solid improvement over user-centric, both...
  • Niall Kennedy: Asking the site visitor to opt-in would defeat the purpose in my particular case. I am trying to...
  • Craig Overend: Without qualifying yourself I find that comment facetious. If your playing on my use of the term...