Comments on: Raw Data Now; The big fight for the Social Web http://almaer.com/blog/raw-data-now-the-big-fight-for-the-social-web blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Jonathan Gray http://almaer.com/blog/raw-data-now-the-big-fight-for-the-social-web/comment-page-1#comment-41581 Jonathan Gray Thu, 06 Aug 2009 14:23:44 +0000 http://almaer.com/blog/?p=2383#comment-41581 You might also be interested to see Rufus Pollock’s original post on this on the Open Knowledge Foundation blog [1] - which Tim Berners-Lee cites as the origin of the “Raw Data Now” meme [2]. [1] http://blog.okfn.org/2007/11/07/give-us-the-data-raw-and-give-it-to-us-now/ [2] http://www.w3.org/2009/Talks/0204-ted-tbl/#(34) You might also be interested to see Rufus Pollock’s original post on this on the Open Knowledge Foundation blog [1] – which Tim Berners-Lee cites as the origin of the “Raw Data Now” meme [2].

[1] http://blog.okfn.org/2007/11/07/give-us-the-data-raw-and-give-it-to-us-now/

[2] http://www.w3.org/2009/Talks/0204-ted-tbl/#(34)

]]> By: Steven Eberling http://almaer.com/blog/raw-data-now-the-big-fight-for-the-social-web/comment-page-1#comment-40731 Steven Eberling Mon, 20 Apr 2009 09:25:13 +0000 http://almaer.com/blog/?p=2383#comment-40731 Users should not have to remember what data they've entrusted to what companies in order to perform some operation on their data. People should be able to consume data and republish with ease (no post or sync required). I agree with P2P federation in the browser -- and I think it would be good to enable clients to act both as clients and servers. Any web application with permissions should be able to access any of my local data while my computers are up and running (and most people have at least one or two). I'm curious why browsers didn't get into the business of collecting and hosting user data earlier. Users should not have to remember what data they’ve entrusted to what companies in order to perform some operation on their data.

People should be able to consume data and republish with ease (no post or sync required). I agree with P2P federation in the browser — and I think it would be good to enable clients to act both as clients and servers. Any web application with permissions should be able to access any of my local data while my computers are up and running (and most people have at least one or two).

I’m curious why browsers didn’t get into the business of collecting and hosting user data earlier.

]]> By: Ray Cromwell http://almaer.com/blog/raw-data-now-the-big-fight-for-the-social-web/comment-page-1#comment-40721 Ray Cromwell Fri, 17 Apr 2009 16:47:28 +0000 http://almaer.com/blog/?p=2383#comment-40721 I wrote about something similar last year (client side storage, peer-to-peer social networking, http://timepedia.blogspot.com/2008/05/decentralizing-web.html) My basic idea then was "Gear-to-Gear" social networking, using federated rendezvous servers. Store all your social data locally in the browser, but encrypt it and replicate it across several rendezvous servers, which are simple publish and subscribe mailbox queues. Other users can obtain access to your data by posting a encrypted friend request to your queue. The next time your gears client syncs, you process the queue. If you agree to friend someone, you encrypt the profile information you want him to have, and deposit it in his mailbox queue where he'll get it on next login. Activity feeds would simply be another round-robin queue (with a different broadcast encryption technique) The only potential gatekeeper bottleneck in the system is the rendezvous servers and how to discover them. But fundamentally, nothing more is needed than the ability to update an address book, queue up activities, and sync to the cloud, but some encryption protocols. That's why I don't get caught up in the hype of Facebook, et al, because to me, this phase is merely a bubble. These things are glorified commodities that sooner or later will be vastly simplified to a fundamental network platform that no one can own. I wrote about something similar last year (client side storage, peer-to-peer social networking, http://timepedia.blogspot.com/2008/05/decentralizing-web.html)

My basic idea then was “Gear-to-Gear” social networking, using federated rendezvous servers. Store all your social data locally in the browser, but encrypt it and replicate it across several rendezvous servers, which are simple publish and subscribe mailbox queues. Other users can obtain access to your data by posting a encrypted friend request to your queue. The next time your gears client syncs, you process the queue. If you agree to friend someone, you encrypt the profile information you want him to have, and deposit it in his mailbox queue where he’ll get it on next login. Activity feeds would simply be another round-robin queue (with a different broadcast encryption technique)

The only potential gatekeeper bottleneck in the system is the rendezvous servers and how to discover them. But fundamentally, nothing more is needed than the ability to update an address book, queue up activities, and sync to the cloud, but some encryption protocols. That’s why I don’t get caught up in the hype of Facebook, et al, because to me, this phase is merely a bubble. These things are glorified commodities that sooner or later will be vastly simplified to a fundamental network platform that no one can own.

]]>