fin Robert O'Brien
Jaikus from fin
Thursday, 13 March 2008
Tuesday, 11 March 2008
-
And a really good starting point for building the foundations for @constantine scenarios would be for Google to start accepting OpenIds, as a relying party to selected services beyond blog commenting. Jaiku being one of the best potential services for this. The aim: starting to build out normative rules for OpenId Providers...reputation potentially based on the G's knowledge of all the various OpenId enabled sites, blog comment usage etc and more...a page rank for OPs. Helping to avoid an Internet that Jonathan Zittrain warns of. Now that would really kick butt IMHO.
Monday, 10 March 2008
-
Oh shoot. I thought the moniker of M$ was rather fitting for the Context ;-) Control and ownership and all. Relationships and openness verses underhanded tricks. That is not to say that "embrace and extend" is intentionally used for either $ or control. Nor always true of MS or others. Actually in the Identity space it is really nice to see the lead taken by MS.
On the "server" in a pocket...that is why I really like [http://research.nokia.com/research/projects/mobile-web-server/ Nokia's Mobile Web Server] project...
-
@constantine you are perilously close to diving into the quagmire that is identity and privacy. Having a ‘Contact’ service that can manage rich social Context a.k.a. Bar Hopping will eventually come. Pownce’s notion of sets and it’s richer set of privacy settings is a start in that direction. Twitter’s direct messages is another. In terms of owning your contacts: ownership is a right to control or use, or more specifically in this case the right to move/delete something. So it doesn’t matter that an online service helps you manage your contacts as long as 1. You can easily move them and 2. when you do move them from a service (or individual for that matter) they are truly deleted. For 1. To be achieved, as @adewale points out, we need Open API(s) and Data Formats. Data formats being more powerful. Hence Google’s contact API is a good thing especially since it is based on ATOM. Although without having looked at it, I suspect the Contact API extends the ATOM format as the other APIs do rather than use it as neutral envelop. Extending ATOM is an act no different to M$’s embrace and extend strategy unfortunately.
Overall OpenID doesn’t have anything to do with a rich contextually aware contact service or privacy control for that matter. It is up to the OpenID Providers to innovate in this area although the use of Directed Identity and OAuth will help a lot. Nor would PGP solve the problem you describe – ‘you have control over who consumes your information’. Interestingly a few things were announced last week that all point in the direction of solving this in various ways. Google’s Contact API is an attempt at making Google the centre of your contacts. Yahoo!’s FireEagle is more interesting because it is a small specialised component that manages your location and controls access to it. This is a very good example of @malach Unix Pipe+Filter description…small pieces loosely joined. I just wish they had done the API based on ATOM. And Finally M$ acquired Credentica for their U-Prove technology; Zero-knowledge proof technology that may solve the privacy/control scenario.
So back to the question @jyri posed: Rich contextual control of our contact’s and the posts would be a start. But, and a very big BUT, doing this may actually change the types of discussions that occur on Jaiku. Next would be then portability of our contacts and posts would be another engendering the notion of ownership. I guess being a OpenId provider would not hurt, but being an OpenID Relying Party would be fantastic for me. And it would be cool if Jaiku also used, update or provided a similar service and API to Fireeagle - all three should be done :)
Thursday, 6 March 2008
Wednesday, 27 February 2008
Monday, 4 February 2008
Friday, 1 February 2008
Tuesday, 29 January 2008
Wednesday, 16 January 2008
Monday, 14 January 2008
-
So who becomes the friend? ...Garage is friends with Car, Car is friends with Jyri. Now there is a thought a conversation with your car. Kinda like a Auto version of Sandy http://www.iwantsandy.com/. BTW: Someone please make Sandy talk via Jaiku.
Saturday, 12 January 2008
Tuesday, 8 January 2008
-
-
@barneyc The .mobi namespace was/is meant to denote content suitable for mobile devices can be found at that URL. A requirement (not really enforced) is that any dotMobi site must support the XHTML Mobile Profile. This is a different requirement from all the other TLD structures that you refer to. And certainly mTLD have tried to build a "brand promise" around this TLD by laying down good dev practices and traditional branding collateral. The ecosystem of internet properties like FB and GOOG have, however , used mdot. Use trumps perfection everytime.I think mdot is a more suitable "extension" of the existing TLDs that people are already conformable with hence easier to use.
Thursday, 20 December 2007
Wednesday, 19 December 2007
-
@barneyc And I thought you were doing this just to rub it in. I knew I should have just turned off Jaiku today. The entire afternoon has been a reminder the u have a new toy and I don't :-(
Wednesday, 5 December 2007
Jaikus from fin