Phil Windley writes about his experience at the Seaside.

For anyone interested in Seaside, you may also be interested in http://video.google.com/videoplay?docid=1029369558328427746″>this video of where Lukas is taking Seaside.

While I love this work I always seem to come away with a couple of nagging issues. One being the amount of memory required to store state on the server for many requests, which over time will become less of an issue.

Another is user-friendly URLs. I’m always hovering links to see where they’ll take me. Or clicking on search results that appear the most recent because they include the date in the path. While I don’t see this as much an issue combined with session state in URLs - something seaside can do - state alone in my mind reduces usability. Then trying to get my head around bookmarking state such that a year or more down the track a session could be resumed. What then happens when there’s been an application revision. Do we then need tools to store application & session state. That then raises the issue of resumed application state and how can we then cross the divide between old and new to update application sessions. Are we looking down the track at virtual machine images for software revisions. At what point do we get persistent, historical application data through the generations.

Another issue Phil raised in his yet to be implemented session example is the unguessable session keys. How much of a problem might security then be. And what additional measures are required to prevent session hijacking.

We seem to be headed towards tracking everything we do in our digital life. Hell I look at Twitter and think we almost already are, still I think we have a long road ahead of us when it comes to persistent historical storage of our digital lives.

Alex Barnett asks about Web Description Languages for REST. Below is a simple example of my own interpretation based originally upon WADL, something I worked on and never did anything with some months ago. It follows the philosophy of least amount of validation, user and machine readable documentation and graceful depreciation. I got so far as to consider re-writing it as a microformat before I became lost in the concept that was the HTTP Extensions Framework (PEP).

Now I love the idea of having the ability to query a resource to find method queries with documentation I can use to interact with that resource. It’s here I believe a WDL may come in very useful. I say may because I wonder if resources themselves should have a Resource Description Language instead.

One of the problems I have with PEP is that pointing to some external language as it enables, adds another layer of fragility. It’s resources themselves that need to contain everything required to interact with that resource. Have a listen to Alan Kaye’s talk for a better explanation.

So using REST I would then simply perform a

GET / HTTP/1.1
Accept: xml/rdl
Host: example.com

Whereby something like my AWDL example is returned. It could however be an HTTP Form, microformat or XForm returned.
[xml]

xsi:schemaLocation="http://example.com/awdl awdl.xsd"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.com/awdl">

I’ve seen people commenting of their dislike of people using twitter as an instant messaging platform. Meh, let it go, people use technology to fill a need. In twitters case; instant gratification messaging(IGM) or as I like to pronounce it; i-gem. Because it’s all about the users. Me and my comment gems!

Feel the urge to scream but don’t want to wake the neighbours? Twitter it.
Just want to share some quick news but don’t think it warrants the effort of email spamming your friends? Twitter it.
Need to take note of an idea that just popped into your head? Twitter it.
Want to build a spam bot? Twitter with it.
Twitter, twitter, twitter it.

But that’s only part of the picture. You see producers and users are also consumers and Twitter can be useful for those who like to track other people and services live via instant messaging alerts or track through aggregation a users past history.

See a twitter you want to comment on? Twitter it using an @username.
See a twitter you find hilarious? Laugh at it. Then star it. (How long will it be before you can send new stars to all your friends?)
See an interesting twitter link? Click on it. Then star it. (One wonders how long tinyurl will stay tiny!)

Now we have a rudimentary bookmarking service and an instant messaging service with offline messaging capabilities. Just add tags and public and private syntax. What about emotions? Emphasis and emoticons…
But then how much is too much? After all; cross-platform plain-text communication is what Twitter does best. For that reason at most I can see them adding prefix and suffix syntax. Maybe prefix an exclamation to make a message private, etc.

But wait there’s more to Twitter than meets the eye! As the BBC example has shown, news producers can be pushed through alerts and marketed through Twitter. No reason other marketers won’t do the same, and monetise it. People are also using it to solicit requests for recommendations on products or for advice. So we can add rudimentary user-centric Vendor Relationship Management “personal requests” into the mix. No reason not to place ads next to those and monetise them on site in request and question channels…

I could see people starting to claim things about others on there too, similar to what Jyte is doing now, and it will only take time before there are proper groups you can join to assert your affiliation. Some people are already creating open accounts anyone can post to. Others are creating accounts to aggregate groups of friends together, creating custom nodes for like-minded individuals. Then there’s the band of often hilarious fakesters and fantasy writers pretending to be someone or something else.

But as with any communications service, they quickly draw the attention of fraudsters. I wonder how long it will be before the first widely publicised “incident” occurs from unsavoury types surveying peoples habits. Already there’s a rudimentary GeoTwitter tracking users locations. While I’d like to believe that the more open we are the more that benefits society, at the same time, not everyone is created equal and some will use that to their own benefit.

Which brings me to a conclusion.

Twitter just isn’t there for me yet. Not for the lack of anything mentioned above. But for the identity-less nature of the service. Decentralised, user-centric instant gratification messaging is still maturing but it’s not there yet. Twitter is a great start but I’d like to see something like OpenID Attribute Exchange and extensions made use of.

Let me store my messages, my history, on my own archival service in a way that lets me choose who can have access to it and for how long. With our Lifestreams carrying such personal information, it makes a lot of sense to me that I have the ability to control that and disperse my information through a controlled means of Identity Rights Agreements, with some of that information over secure lines. So much more can then be done with that structured data.

Saying that, I think a Twitter-like service could be the kick starter the SemWeb needs to really go mainstream if we can get a basic syntax people can use happening for structuring everyday tasks.

Afterthought: What Twitter really needs to go even more viral than it already is, is a “track me on twitter” widget users can add to their blog/site for visitors to click on and subscribe to immediately if they already have a Twitter account.

p.s. I thought about twittering just that afterthought… argh! it’s addictive.