Marc Canter, Evan Prodromou, Kevin Marks, and Brad Williams talk bearhugging with Steve Gillmor. Recorded August 15, 2008.
This entry was posted
on Friday, August 15th, 2008 at 7:43 pm and is filed under Gillmor Gang.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
[...] has some additional comments on this change to Twitter’s API, and points to the latest Gillmor Gang where he interviews the author of Identi.ca. Steve says he makes a strong argument there to keep [...]
IMO, here is a simple arch of open mesh that does not require a bunch of new standards:
1) Every social service publishes atom feeds. Feeds contain entries and/or other Feeds. Feeds within feeds is the tree. Every feed and entry in a feed is addressable by its unique URI.
2) Every service supports user-created search feeds. In effect, this is a “track” feed with sql-like where predicates. Users can create and delete as desired.
3) Feed Entries must contain at least the following fields (schema):
EntryURI (unique entry URI)
ReplyURI (null or the entry being replied to)
To (users or user-feeds (i.e. groups) to send msg to)
From (user URI who sent this entry)
UTCDate (msg date in UTC)
Comment (msg string)
Attachments (null, Entry URIs)
4) Every service must support at least one User Attachment feed to store attachments (i.e. pictures, docs, etc). Service specified storage limits. Attachments pushed from the client are stored as separate Entries with a URI as normal. The Attachments field then contains the blob data as base64 wrapped in an XML infoset. This could be an opt-in feature of the service if they don’t support user space.
5) EntryURI must be unique. The EntryURI serves as both the path to the entry as well as the key across the Net.
6) Services must support RESTfull DB queries (i.e. Astoria like).
What this provides:
1) Simple and common. All entries from all services are static and addressable.
2) REST and ATOM are the lowest common denominator. No other standards need to be made. All platforms supported by nature of atom and REST. No proprietary APIs required.
3) Minimum set of fields (above) are requirement. Order not important and any derived schemas supported. Clients just ignore unknown fields.
4) Client frameworks can aggregate and relate feed collections anyway they want.
5) Attachments are simple links to attachment entries stored at the service. By convention, the client software pushes attachments to the user’s Attachment Feed that is addressable by others. Alternatively, if the user manually supplies attachment URL(s), they are passed in place and no attachments are stored at service.
[...] “identi.ca”: Business-Power gegen Open Source-Power. Vor einigen Tagen auch noch ein Podacst zum Thema von der Gilmor Gang – diesmal mit: Marc Canter, Evan Prodromou, Kevin Marks, und Brad Williams mit Steve Gillmor [...]
[...] neuen Welle. Sie hat angefangen. Jawohl. Und wo ich gerade bei Podcast war – hier ein weiterer: Marc Canter, Evan Prodromou, Kevin Marks, und Brad Williams mit Steve Gillmor. Natürlich hat nicht nur Deutschland Identi.ca entdeckt – auch internationale Reaktionen gab [...]