"We're utilizing open standards such as microformats and the HTTP protocol, the fabric of the web. We considered using the XMPP protocol, but our requirement to run on most shared hosting environments killed that idea."
On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > In reading up on Marshall's post on Action Links today, I came across > this on a comment on RWW:
> "We're utilizing open standards such as microformats and the HTTP > protocol, the fabric of the web. We considered using the XMPP > protocol, but our requirement to run on most shared hosting > environments killed that idea."
> "We're utilizing open standards such as microformats and the HTTP > protocol, the fabric of the web. We considered using the XMPP > protocol, but our requirement to run on most shared hosting > environments killed that idea."
On Mon, Mar 1, 2010 at 1:51 PM, Chris Messina <chris.mess...@gmail.com> wrote: > In reading up on Marshall's post on Action Links today, I came across > this on a comment on RWW:
> "We're utilizing open standards such as microformats and the HTTP > protocol, the fabric of the web. We considered using the XMPP > protocol, but our requirement to run on most shared hosting > environments killed that idea."
The big difference between 6d and the other projects above, from what I've seen (and I'm not trying to say this disparagingly), is that we aren't trying to create a new protocol or any new standards. We kept it as simple as possible by using HTTP and REST to communicate to other 6d sites. So when you start from the most basic layer it makes it easy to build additional layers on top to communicate to any of those disparate closed networks that let you access them via their API or protocol. We view it as the internet and HTTP was designed for decentralized social networking already. Why try and reinvent the wheel?
On Mar 1, 2:19 pm, "Yonas Y." <yona...@gmail.com> wrote:
> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > > In reading up on Marshall's post on Action Links today, I came across > > this on a comment on RWW:
> > "Centralizing You By Decentralizing Social Networking" > >http://www.get6d.com
> > I thought this sounded pretty familiar:
> > "We're utilizing open standards such as microformats and the HTTP > > protocol, the fabric of the web. We considered using the XMPP > > protocol, but our requirement to run on most shared hosting > > environments killed that idea."
So what specific protocols are you using? HTTP and REST only get you so far so can you elaborate on what expect people will be able to do with 6D?
Have you taken a look at ActivityStreams, Portable Contacts, or the OpenSocial APIs?
And, when do we get to see the source code!
@jg: in the early days of Diso, we thought that XMPP could be a part of this effort... turned out it was a bit too much to administer on commodity hosting providers, so we abandoned it. 6D says more or less the same thing on their site.
On Mon, Mar 1, 2010 at 6:27 PM, Erik Bigelow <erik.w...@gmail.com> wrote: > The big difference between 6d and the other projects above, from what > I've seen (and I'm not trying to say this disparagingly), is that we > aren't trying to create a new protocol or any new standards. We kept > it as simple as possible by using HTTP and REST to communicate to > other 6d sites. So when you start from the most basic layer it makes > it easy to build additional layers on top to communicate to any of > those disparate closed networks that let you access them via their API > or protocol. We view it as the internet and HTTP was designed for > decentralized social networking already. Why try and reinvent the > wheel?
> On Mar 1, 2:19 pm, "Yonas Y." <yona...@gmail.com> wrote: > > There seems to be a atleast four groups that are trying to do the same > > thing:
> > On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > > > In reading up on Marshall's post on Action Links today, I came across > > > this on a comment on RWW:
> > > "Centralizing You By Decentralizing Social Networking" > > >http://www.get6d.com
> > > I thought this sounded pretty familiar:
> > > "We're utilizing open standards such as microformats and the HTTP > > > protocol, the fabric of the web. We considered using the XMPP > > > protocol, but our requirement to run on most shared hosting > > > environments killed that idea."
> > > Anyone have any insight into the project, or how far along it is?
> > > Chris
> -- > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
There's 2 of us building 6d. I'm the other person and wanted to respond.
We're not using any other protocols. We've organized the code according to our understanding of REST and defined properties like post::title, post::body, post::source, friend::name, friend::url, etc. based on what we've found to be common terms used in apps like Wordpress, Twitter and Facebook. While fully recognizing that this may change since we'll want to incorporate more open and standardized protocols in the future.
The problems we wanted to tackle are sharing posts, thoughts, videos, and photos with your friends in a decentralized network. We've haven't addressed activity streams yet, but we've been talking about it.
It's been hard to describe what you can do with 6d in a generic way without seeming like Wordpress or Tumblr. At first glance, the 6d UI is a blog. There's a public facing site where you can make posts. As the authorized person, you can create and edit your posts, manage your address book and follow other people who have 6d sites. Currently, there's only 1 authorized person since theoretically, everyone will eventually have their own (6d;)site that can send and receive messages.
Behind the scenes, every post that's made public right now gets sent via an HTTP POST to everyone in your address book. We're adding the ability to pick and choose who to send the post right now instead of broadcasting it to everyone, but it's not current functionality. Each person you authorize to follow you gets sent a public key with which we'll be using for encrypting the data (not done yet). This is just a first stab at trying to identify who's sending you a message.
I've structured the code to include themes so you'll be able to theme your site as easy as defining css for the default views. But it also allows you to override the default views with your own views (markup).
Yes, we've taken a look at ActivityStreams, Portable Contacts and a little at the OpenSocial APIs. But right now, we're focusing on getting a working app first. We believe by using a RESTful approach to organizing the code, incorporating those standards and/or features will be easy. We do want to follow open standards, but we're trying to get a functioning app up and running as soon as possible.
Yeah, we discussed using XMPP a lot in the beginning. We imagined a bunch of XMPP servers as Web Servers that communicated with each other in xml fragments and that vision was really cool. But we came to the same conclusion given our desire to run on shared hosting environments. Although, I personally believe that we'll get there in the future, Web Servers communicating with each other for presence notification and real time updates. I think that's the next evolution where the default server configurations will have software that does that just like Apache is a part of many a servers default configuration. It's good to hear that others came to the same conclusion. I think the ability to run on commodity servers is one of the reasons why Wordpress is so popular, and PHP for that matter.
Our intent is to open source this code base. I've already open sourced the RESTful framework (http://www.restfulchinchilla.com) that the app is using and we'd like to get to beta status before releasing the rest. Also, we plan on starting a business around it 6d, so we're discussing how to do it now. We'll definitely send you the code base to see what we're doing, but I'd like to clean up some things before sending it to you;) The code changes a lot right now.
On Mar 1, 8:47 pm, Chris Messina <chris.mess...@gmail.com> wrote:
> So what specific protocols are you using? HTTP and REST only get you so far > so can you elaborate on what expect people will be able to do with 6D?
> Have you taken a look at ActivityStreams, Portable Contacts, or the > OpenSocial APIs?
> And, when do we get to see the source code!
> @jg: in the early days of Diso, we thought that XMPP could be a part of this > effort... turned out it was a bit too much to administer on commodity > hosting providers, so we abandoned it. 6D says more or less the same thing > on their site.
> Chris
> On Mon, Mar 1, 2010 at 6:27 PM, Erik Bigelow <erik.w...@gmail.com> wrote: > > The big difference between 6d and the other projects above, from what > > I've seen (and I'm not trying to say this disparagingly), is that we > > aren't trying to create a new protocol or any new standards. We kept > > it as simple as possible by using HTTP and REST to communicate to > > other 6d sites. So when you start from the most basic layer it makes > > it easy to build additional layers on top to communicate to any of > > those disparate closed networks that let you access them via their API > > or protocol. We view it as the internet and HTTP was designed for > > decentralized social networking already. Why try and reinvent the > > wheel?
> > On Mar 1, 2:19 pm, "Yonas Y." <yona...@gmail.com> wrote: > > > There seems to be a atleast four groups that are trying to do the same > > > thing:
> > > On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > > > > In reading up on Marshall's post on Action Links today, I came across > > > > this on a comment on RWW:
> > > > "Centralizing You By Decentralizing Social Networking" > > > >http://www.get6d.com
> > > > I thought this sounded pretty familiar:
> > > > "We're utilizing open standards such as microformats and the HTTP > > > > protocol, the fabric of the web. We considered using the XMPP > > > > protocol, but our requirement to run on most shared hosting > > > > environments killed that idea."
> > > > Anyone have any insight into the project, or how far along it is?
> > > > Chris
> > -- > > You received this message because you are subscribed to the Google Groups > > "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to > > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/diso-project?hl=en.
While people from different projects are here, I'd like to take this opportunity to discuss about how are we tackling with the problem of keeping a user signed-in across the network? I've outlined the problem in this wiki - http://code.google.com/p/kopal/wiki/Challenge
On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote:
> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > > In reading up on Marshall's post on Action Links today, I came across > > this on a comment on RWW:
> > "Centralizing You By Decentralizing Social Networking" > >http://www.get6d.com
> > I thought this sounded pretty familiar:
> > "We're utilizing open standards such as microformats and the HTTP > > protocol, the fabric of the web. We considered using the XMPP > > protocol, but our requirement to run on most shared hosting > > environments killed that idea."
I don't have the link on me now, but Chris posted a link today to a Drupal consultancy that built an system for keeping users logged in across services by using *pubsubhubbub* to push signin data around. That's *still* messing with my head it's so awesome.
On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> wrote: > While people from different projects are here, I'd like to take this > opportunity > to discuss about how are we tackling with the problem of keeping a > user signed-in across the network? > I've outlined the problem in this wiki - http://code.google.com/p/kopal/wiki/Challenge
> On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: >> There seems to be a atleast four groups that are trying to do the same >> thing:
>> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: >> > In reading up on Marshall's post on Action Links today, I came across >> > this on a comment on RWW:
>> > "Centralizing You By Decentralizing Social Networking" >> >http://www.get6d.com
>> > I thought this sounded pretty familiar:
>> > "We're utilizing open standards such as microformats and the HTTP >> > protocol, the fabric of the web. We considered using the XMPP >> > protocol, but our requirement to run on most shared hosting >> > environments killed that idea."
>> > Anyone have any insight into the project, or how far along it is?
>> > Chris
> -- > You received this message because you are subscribed to the Google Groups "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/diso-project?hl=en.
On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote: > I don't have the link on me now, but Chris posted a link today to a > Drupal consultancy that built an system for keeping users logged in > across services by using *pubsubhubbub* to push signin data around. > That's *still* messing with my head it's so awesome.
> --Steve
> On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> > wrote: > > While people from different projects are here, I'd like to take this > > opportunity > > to discuss about how are we tackling with the problem of keeping a > > user signed-in across the network? > > I've outlined the problem in this wiki - > http://code.google.com/p/kopal/wiki/Challenge
> > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: > >> There seems to be a atleast four groups that are trying to do the same > >> thing:
> >> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > >> > In reading up on Marshall's post on Action Links today, I came across > >> > this on a comment on RWW:
> >> > "Centralizing You By Decentralizing Social Networking" > >> >http://www.get6d.com
> >> > I thought this sounded pretty familiar:
> >> > "We're utilizing open standards such as microformats and the HTTP > >> > protocol, the fabric of the web. We considered using the XMPP > >> > protocol, but our requirement to run on most shared hosting > >> > environments killed that idea."
> >> > Anyone have any insight into the project, or how far along it is?
> >> > Chris
> > -- > > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > . > > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
> On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote: > I don't have the link on me now, but Chris posted a link today to a > Drupal consultancy that built an system for keeping users logged in > across services by using *pubsubhubbub* to push signin data around. > That's *still* messing with my head it's so awesome.
> --Steve
> On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> wrote: > > While people from different projects are here, I'd like to take this > > opportunity > > to discuss about how are we tackling with the problem of keeping a > > user signed-in across the network? > > I've outlined the problem in this wiki - http://code.google.com/p/kopal/wiki/Challenge
> > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: > >> There seems to be a atleast four groups that are trying to do the same > >> thing:
> >> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > >> > In reading up on Marshall's post on Action Links today, I came across > >> > this on a comment on RWW:
> >> > "Centralizing You By Decentralizing Social Networking" > >> >http://www.get6d.com
> >> > I thought this sounded pretty familiar:
> >> > "We're utilizing open standards such as microformats and the HTTP > >> > protocol, the fabric of the web. We considered using the XMPP > >> > protocol, but our requirement to run on most shared hosting > >> > environments killed that idea."
> >> > Anyone have any insight into the project, or how far along it is?
> >> > Chris
> > -- > > You received this message because you are subscribed to the Google Groups "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > > For more options, visit this group at http://groups.google.com/group/diso-project?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/diso-project?hl=en.
> This email is: [ ] shareable [X] ask first [ ] private
> -- > You received this message because you are subscribed to the Google Groups "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/diso-project?hl=en.
We've been talking about using ID's at different sites and haven't come up with any satisfactory solutions and for our 6d project it's not something that's the forefront in the list of things to do just yet. While we've looked at foaf+ssl and like it for it's RESTful nature it will require users to buy an ssl certificate which we don't really like. :(
OpenID is something we'd really like to support, and I've been doing some searching about how possible that is in a shared host environment. The thing that I want to look at more when I have more time is phpMyID which seems to be a pretty good solution for single- user/site openID support but it doesn't seem to work with openID 2.0 at this time. :(
> > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote: > > I don't have the link on me now, but Chris posted a link today to a > > Drupal consultancy that built an system for keeping users logged in > > across services by using *pubsubhubbub* to push signin data around. > > That's *still* messing with my head it's so awesome.
> > --Steve
> > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> wrote: > > > While people from different projects are here, I'd like to take this > > > opportunity > > > to discuss about how are we tackling with the problem of keeping a > > > user signed-in across the network? > > > I've outlined the problem in this wiki -http://code.google.com/p/kopal/wiki/Challenge
> > > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: > > >> There seems to be a atleast four groups that are trying to do the same > > >> thing:
> > >> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > > >> > In reading up on Marshall's post on Action Links today, I came across > > >> > this on a comment on RWW:
> > >> > "Centralizing You By Decentralizing Social Networking" > > >> >http://www.get6d.com
> > >> > I thought this sounded pretty familiar:
> > >> > "We're utilizing open standards such as microformats and the HTTP > > >> > protocol, the fabric of the web. We considered using the XMPP > > >> > protocol, but our requirement to run on most shared hosting > > >> > environments killed that idea."
> > >> > Anyone have any insight into the project, or how far along it is?
> > >> > Chris
> > > -- > > > You received this message because you are subscribed to the Google Groups "Diso Project" group. > > > To post to this group, send email to diso-project@googlegroups.com. > > > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > > > For more options, visit this group athttp://groups.google.com/group/diso-project?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/diso-project?hl=en.
> > -- > > Chris Messina > > Open Web Advocate, Google
> > This email is: [ ] shareable [X] ask first [ ] private
> > -- > > You received this message because you are subscribed to the Google Groups "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/diso-project?hl=en.
> On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com > <mailto:steve...@gmail.com>> wrote:
> I don't have the link on me now, but Chris posted a link today to a > Drupal consultancy that built an system for keeping users logged in > across services by using *pubsubhubbub* to push signin data around. > That's *still* messing with my head it's so awesome.
> --Steve
> On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary > <nas...@gmail.com <mailto:nas...@gmail.com>> wrote: > > While people from different projects are here, I'd like to take this > > opportunity > > to discuss about how are we tackling with the problem of keeping a > > user signed-in across the network? > > I've outlined the problem in this wiki - > http://code.google.com/p/kopal/wiki/Challenge
> > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com > <mailto:yona...@gmail.com>> wrote: > >> There seems to be a atleast four groups that are trying to do > the same > >> thing:
> On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote:
>> I don't have the link on me now, but Chris posted a link today to a >> Drupal consultancy that built an system for keeping users logged in >> across services by using *pubsubhubbub* to push signin data around. >> That's *still* messing with my head it's so awesome.
>> --Steve
>> On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> >> wrote: >> > While people from different projects are here, I'd like to take this >> > opportunity >> > to discuss about how are we tackling with the problem of keeping a >> > user signed-in across the network? >> > I've outlined the problem in this wiki - >> http://code.google.com/p/kopal/wiki/Challenge
>> > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: >> >> There seems to be a atleast four groups that are trying to do the same >> >> thing:
> -- > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
It's absolutely brilliant. I had some early chats with the fine folks @ DevSeed when they were putting this together and was *very* impressed with the solution.
> On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote:
>> I don't have the link on me now, but Chris posted a link today to a >> Drupal consultancy that built an system for keeping users logged in >> across services by using *pubsubhubbub* to push signin data around. >> That's *still* messing with my head it's so awesome.
>> --Steve
>> On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> >> wrote: >> > While people from different projects are here, I'd like to take this >> > opportunity >> > to discuss about how are we tackling with the problem of keeping a >> > user signed-in across the network? >> > I've outlined the problem in this wiki - >> > http://code.google.com/p/kopal/wiki/Challenge
>> > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: >> >> There seems to be a atleast four groups that are trying to do the same >> >> thing:
>> >> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: >> >> > In reading up on Marshall's post on Action Links today, I came across >> >> > this on a comment on RWW:
>> >> > "Centralizing You By Decentralizing Social Networking" >> >> >http://www.get6d.com
>> >> > I thought this sounded pretty familiar:
>> >> > "We're utilizing open standards such as microformats and the HTTP >> >> > protocol, the fabric of the web. We considered using the XMPP >> >> > protocol, but our requirement to run on most shared hosting >> >> > environments killed that idea."
>> >> > Anyone have any insight into the project, or how far along it is?
>> >> > Chris
>> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Diso Project" group. >> > To post to this group, send email to diso-project@googlegroups.com. >> > To unsubscribe from this group, send email to >> > diso-project+unsubscribe@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/diso-project?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Diso Project" group. >> To post to this group, send email to diso-project@googlegroups.com. >> To unsubscribe from this group, send email to >> diso-project+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/diso-project?hl=en.
> This email is: [ ] shareable [X] ask first [ ] private
> -- > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
Re buying TLS certs, startssl has IE support for gratis and cacert is cool too
Sent from my Android phone. Topposted :-(
On Mar 3, 2010 11:27 AM, "Erik Bigelow" <erik.w...@gmail.com> wrote:
We've been talking about using ID's at different sites and haven't come up with any satisfactory solutions and for our 6d project it's not something that's the forefront in the list of things to do just yet. While we've looked at foaf+ssl and like it for it's RESTful nature it will require users to buy an ssl certificate which we don't really like. :(
OpenID is something we'd really like to support, and I've been doing some searching about how possible that is in a shared host environment. The thing that I want to look at more when I have more time is phpMyID which seems to be a pretty good solution for single- user/site openID support but it doesn't seem to work with openID 2.0 at this time. :(
Anyway, it's in our minds but up in the air for now.
On Mar 2, 4:37 pm, "Peter H. Reiser" <peter.rei...@gmail.com> wrote:
> How about this onehttp://esw.w3.org/topic/foaf+ssl > Peter > > On Mar 2, 2010, at 11:19 PM, Chris Messina wrote: > > > Voila: > > >http://developmentse... > > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote: > > I don't have the link ... > > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com>
wrote: > > > While people ...
> > > For more options, visit this group athttp://
PuSH is cool but still relies on a hub as your NotificationCenter. We're trying to avoid dependence on a hub for notifications. Think of 6d more along the lines of peer to peer messaging without the presence notifications. The PuSH implementation is addressing a different user story.
On Mar 3, 1:37 pm, Andrew Wetzel <andwet...@gmail.com> wrote:
> > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com > > <mailto:steve...@gmail.com>> wrote:
> > I don't have the link on me now, but Chris posted a link today to a > > Drupal consultancy that built an system for keeping users logged in > > across services by using *pubsubhubbub* to push signin data around. > > That's *still* messing with my head it's so awesome.
> > --Steve
> > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary > > <nas...@gmail.com <mailto:nas...@gmail.com>> wrote: > > > While people from different projects are here, I'd like to take this > > > opportunity > > > to discuss about how are we tackling with the problem of keeping a > > > user signed-in across the network? > > > I've outlined the problem in this wiki - > > http://code.google.com/p/kopal/wiki/Challenge
> > > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com > > <mailto:yona...@gmail.com>> wrote: > > >> There seems to be a atleast four groups that are trying to do > > the same > > >> thing:
BuddyPress is still a centralized solution for creating a social network. You have to setup an account in a central database to belong that a network. 6d is focusing on a distributed implementation for broadcasting messages instead of having to create an account on every network that you want to be a part of.
On Mar 3, 3:25 pm, Robert <langb...@gmail.com> wrote:
> > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com> wrote:
> >> I don't have the link on me now, but Chris posted a link today to a > >> Drupal consultancy that built an system for keeping users logged in > >> across services by using *pubsubhubbub* to push signin data around. > >> That's *still* messing with my head it's so awesome.
> >> --Steve
> >> On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary <nas...@gmail.com> > >> wrote: > >> > While people from different projects are here, I'd like to take this > >> > opportunity > >> > to discuss about how are we tackling with the problem of keeping a > >> > user signed-in across the network? > >> > I've outlined the problem in this wiki - > >>http://code.google.com/p/kopal/wiki/Challenge
> >> > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote: > >> >> There seems to be a atleast four groups that are trying to do the same > >> >> thing:
> > -- > > You received this message because you are subscribed to the Google Groups > > "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to > > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/diso-project?hl=en.
conceptually yes, there is a distinction between the content publisher and the hub. However, in practice they can be one and the same. For example, take a look at the announcement about WordPress yesterday[0]... the plugin that they wrote[1] doesn't depend on a separate hub, it's built in, so it's basically a peer-to-peer model. Depending on how you actually implement this model you could still run into problems (ie. whether or not you are queing up pings, or trying to send them all at once), but it's certainly supported in pubsubhubbub.
On Thu, Mar 4, 2010 at 9:28 AM, jg <guerra.j...@gmail.com> wrote: > PuSH is cool but still relies on a hub as your NotificationCenter. > We're trying to avoid dependence on a hub for notifications. Think of > 6d more along the lines of peer to peer messaging without the presence > notifications. The PuSH implementation is addressing a different user > story.
> > > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com > > > <mailto:steve...@gmail.com>> wrote:
> > > I don't have the link on me now, but Chris posted a link today to a > > > Drupal consultancy that built an system for keeping users logged in > > > across services by using *pubsubhubbub* to push signin data around. > > > That's *still* messing with my head it's so awesome.
> > > --Steve
> > > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary > > > <nas...@gmail.com <mailto:nas...@gmail.com>> wrote: > > > > While people from different projects are here, I'd like to take > this > > > > opportunity > > > > to discuss about how are we tackling with the problem of keeping > a > > > > user signed-in across the network? > > > > I've outlined the problem in this wiki - > > > http://code.google.com/p/kopal/wiki/Challenge
> > > > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com > > > <mailto:yona...@gmail.com>> wrote: > > > >> There seems to be a atleast four groups that are trying to do > > > the same > > > >> thing:
> -- > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
I see that. I think that's awesome to have the ability to push your posts to a roster. That's definitely what we're trying to accomplish with 6d. I've deliberated with myself about taking the approach of building this functionality on top of Wordpress. But ultimately decided that I wanted to build a new app (6d) that we can build a business model around AND promote this technique across apps like Wodpress instead. I'm really excited to see these implementations actually coming to reality. I like the vision of a distributed real time web. It just seems like the natural step to the web's evolution.
On Mar 4, 1:13 pm, Will Norris <w...@willnorris.com> wrote:
> conceptually yes, there is a distinction between the content publisher and > the hub. However, in practice they can be one and the same. For example, > take a look at the announcement about WordPress yesterday[0]... the plugin > that they wrote[1] doesn't depend on a separate hub, it's built in, so it's > basically a peer-to-peer model. Depending on how you actually implement > this model you could still run into problems (ie. whether or not you are > queing up pings, or trying to send them all at once), but it's certainly > supported in pubsubhubbub.
> On Thu, Mar 4, 2010 at 9:28 AM, jg <guerra.j...@gmail.com> wrote: > > PuSH is cool but still relies on a hub as your NotificationCenter. > > We're trying to avoid dependence on a hub for notifications. Think of > > 6d more along the lines of peer to peer messaging without the presence > > notifications. The PuSH implementation is addressing a different user > > story.
> > > > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com > > > > <mailto:steve...@gmail.com>> wrote:
> > > > I don't have the link on me now, but Chris posted a link today to a > > > > Drupal consultancy that built an system for keeping users logged in > > > > across services by using *pubsubhubbub* to push signin data around. > > > > That's *still* messing with my head it's so awesome.
> > > > --Steve
> > > > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary > > > > <nas...@gmail.com <mailto:nas...@gmail.com>> wrote: > > > > > While people from different projects are here, I'd like to take > > this > > > > > opportunity > > > > > to discuss about how are we tackling with the problem of keeping > > a > > > > > user signed-in across the network? > > > > > I've outlined the problem in this wiki - > > > > http://code.google.com/p/kopal/wiki/Challenge
> > > > > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com > > > > <mailto:yona...@gmail.com>> wrote: > > > > >> There seems to be a atleast four groups that are trying to do > > > > the same > > > > >> thing:
> > -- > > You received this message because you are subscribed to the Google Groups > > "Diso Project" group. > > To post to this group, send email to diso-project@googlegroups.com. > > To unsubscribe from this group, send email to > > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/diso-project?hl=en.
And Google Wave also, if we emphasize decentralized and deempasize the rest ;-)
Good thing I never started my own project to do exactly the same thing. But they are all here for a reason; we see that these social networks aren't cutting it anymore. They're not as free as they should be, they're not decentralized like our beloved Internet.
PuSH is cool, especially with Google working on implementing this into search, but it's still solving a different user story. It's pushing public stories around real-time. What if I only want my friends to see it and not the rest of the world?
I want to build 6d because I want it to be my online identity. Anyone else that has a 6d site it will be their online identity. If they want to turn it into their aggregator for other networks, that's great. Or, because our idea of one user per 6d site, if ReadWriteWeb gave each of it's editors a 6d site, and turned ReadWriteWeb into sorta a "hub" 6d site where the editors work would all be pushed and published, then they could.
6d is all about owning your information and identity, and getting to choose exactly what you want to do with it. Facebook controls way to much in their little mini-internet and can do whatever they want with my info and I don't like that. We'd really like each instance to be that person's OpenID server also, to log into other sites, sites that make sense to stay centralized. That was one of my other reasons to build 6d. I really hate having to register at every site I go to.
My vision with 6d is being able to pass messages back and forth with my friends and peers. Publish posts to the world. And access other sites by having that site authenticate me through my site.
Yes we'll support Activity Streams and other protocols that make sense, but some of those things will be a layer on top of the basic functionality of 6d. You can almost think of 6d as your email over HTTP with the ability to make things as public or private as you want.
On Thu, Mar 4, 2010 at 2:22 PM, jg <guerra.j...@gmail.com> wrote: > I see that. I think that's awesome to have the ability to push your > posts to a roster. That's definitely what we're trying to accomplish > with 6d. I've deliberated with myself about taking the approach of > building this functionality on top of Wordpress. But ultimately > decided that I wanted to build a new app (6d) that we can build a > business model around AND promote this technique across apps like > Wodpress instead. I'm really excited to see these implementations > actually coming to reality. I like the vision of a distributed real > time web. It just seems like the natural step to the web's evolution.
> On Mar 4, 1:13 pm, Will Norris <w...@willnorris.com> wrote: >> conceptually yes, there is a distinction between the content publisher and >> the hub. However, in practice they can be one and the same. For example, >> take a look at the announcement about WordPress yesterday[0]... the plugin >> that they wrote[1] doesn't depend on a separate hub, it's built in, so it's >> basically a peer-to-peer model. Depending on how you actually implement >> this model you could still run into problems (ie. whether or not you are >> queing up pings, or trying to send them all at once), but it's certainly >> supported in pubsubhubbub.
>> On Thu, Mar 4, 2010 at 9:28 AM, jg <guerra.j...@gmail.com> wrote: >> > PuSH is cool but still relies on a hub as your NotificationCenter. >> > We're trying to avoid dependence on a hub for notifications. Think of >> > 6d more along the lines of peer to peer messaging without the presence >> > notifications. The PuSH implementation is addressing a different user >> > story.
>> > > > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com >> > > > <mailto:steve...@gmail.com>> wrote:
>> > > > I don't have the link on me now, but Chris posted a link today to a >> > > > Drupal consultancy that built an system for keeping users logged in >> > > > across services by using *pubsubhubbub* to push signin data around. >> > > > That's *still* messing with my head it's so awesome.
>> > > > --Steve
>> > > > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary >> > > > <nas...@gmail.com <mailto:nas...@gmail.com>> wrote: >> > > > > While people from different projects are here, I'd like to take >> > this >> > > > > opportunity >> > > > > to discuss about how are we tackling with the problem of keeping >> > a >> > > > > user signed-in across the network? >> > > > > I've outlined the problem in this wiki - >> > > > http://code.google.com/p/kopal/wiki/Challenge
>> > > > > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com >> > > > <mailto:yona...@gmail.com>> wrote: >> > > > >> There seems to be a atleast four groups that are trying to do >> > > > the same >> > > > >> thing:
>> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Diso Project" group. >> > To post to this group, send email to diso-project@googlegroups.com. >> > To unsubscribe from this group, send email to >> > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> >> > . >> > For more options, visit this group at >> >http://groups.google.com/group/diso-project?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/diso-project?hl=en.
On Thu, Mar 4, 2010 at 2:13 PM, Will Norris <w...@willnorris.com> wrote: > conceptually yes, there is a distinction between the content publisher and > the hub. However, in practice they can be one and the same. For example, > take a look at the announcement about WordPress yesterday[0]... the plugin > that they wrote[1] doesn't depend on a separate hub, it's built in, so it's > basically a peer-to-peer model. Depending on how you actually implement > this model you could still run into problems (ie. whether or not you are > queing up pings, or trying to send them all at once), but it's certainly > supported in pubsubhubbub.
> On Thu, Mar 4, 2010 at 9:28 AM, jg <guerra.j...@gmail.com> wrote:
>> PuSH is cool but still relies on a hub as your NotificationCenter. >> We're trying to avoid dependence on a hub for notifications. Think of >> 6d more along the lines of peer to peer messaging without the presence >> notifications. The PuSH implementation is addressing a different user >> story.
>> > > On Tue, Mar 2, 2010 at 2:14 PM, Steve Ivy <steve...@gmail.com >> > > <mailto:steve...@gmail.com>> wrote:
>> > > I don't have the link on me now, but Chris posted a link today to >> a >> > > Drupal consultancy that built an system for keeping users logged >> in >> > > across services by using *pubsubhubbub* to push signin data >> around. >> > > That's *still* messing with my head it's so awesome.
>> > > --Steve
>> > > On Mon, Mar 1, 2010 at 10:57 PM, Vikrant Chaudhary >> > > <nas...@gmail.com <mailto:nas...@gmail.com>> wrote: >> > > > While people from different projects are here, I'd like to take >> this >> > > > opportunity >> > > > to discuss about how are we tackling with the problem of keeping >> a >> > > > user signed-in across the network? >> > > > I've outlined the problem in this wiki - >> > > http://code.google.com/p/kopal/wiki/Challenge
>> > > > On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com >> > > <mailto:yona...@gmail.com>> wrote: >> > > >> There seems to be a atleast four groups that are trying to do >> > > the same >> > > >> thing:
>> -- >> You received this message because you are subscribed to the Google Groups >> "Diso Project" group. >> To post to this group, send email to diso-project@googlegroups.com. >> To unsubscribe from this group, send email to >> diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/diso-project?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to > diso-project+unsubscribe@googlegroups.com<diso-project%2Bunsubscribe@google groups.com> > . > For more options, visit this group at > http://groups.google.com/group/diso-project?hl=en.
I guess people started discussing something else rather than the discussion I intended to start. What I'm trying to ask is quite different than broadcasting or doing simultaneous sign-in on 5 different sites. I was actually asking about the problem of how to sign-in automatically when you visit _any_ new domain on a distributed network. And while community here has taken a different route of discussion, I'd rather start a new thread instead of polluting this discussion. Here is the link - http://groups.google.com/group/diso-project/t/d30532cfb85a3889
On Mar 2, 10:57 am, Vikrant Chaudhary <nas...@gmail.com> wrote:
> While people from different projects are here, I'd like to take this > opportunity > to discuss about how are we tackling with the problem of keeping a > user signed-in across the network? > I've outlined the problem in this wiki -http://code.google.com/p/kopal/wiki/Challenge
> On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote:
> > There seems to be a atleast four groups that are trying to do the same > > thing:
> > On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: > > > In reading up on Marshall's post on Action Links today, I came across > > > this on a comment on RWW:
> > > "Centralizing You By Decentralizing Social Networking" > > >http://www.get6d.com
> > > I thought this sounded pretty familiar:
> > > "We're utilizing open standards such as microformats and the HTTP > > > protocol, the fabric of the web. We considered using the XMPP > > > protocol, but our requirement to run on most shared hosting > > > environments killed that idea."
Wouldn't that involve giving any new domain my personal information by default? Even if we're just talking about handing over a pseudonym from a big IdP with no attached attributes, that sounds like much more than I'm interested in giving to every site. Cookies are bad enough, eh?
Maybe I'm not seeing the use case you're fond of? -- j
On Mar 5, 2010, at 5:01 AM, Vikrant Chaudhary wrote:
> I guess people started discussing something else rather than the > discussion I intended to start. > What I'm trying to ask is quite different than broadcasting or doing > simultaneous sign-in on 5 different sites. > I was actually asking about the problem of how to sign-in > automatically when you visit _any_ new domain on a distributed > network. > And while community here has taken a different route of discussion, > I'd rather start a new thread instead of polluting this discussion. > Here is the link - http://groups.google.com/group/diso-project/t/d30532cfb85a3889
> On Mar 2, 10:57 am, Vikrant Chaudhary <nas...@gmail.com> wrote: >> While people from different projects are here, I'd like to take this >> opportunity >> to discuss about how are we tackling with the problem of keeping a >> user signed-in across the network? >> I've outlined the problem in this wiki -http://code.google.com/p/kopal/wiki/Challenge
>> On Mar 2, 1:19 am, "Yonas Y." <yona...@gmail.com> wrote:
>>> There seems to be a atleast four groups that are trying to do the same >>> thing:
>>> On Mon, 2010-03-01 at 11:51 -0800, Chris Messina wrote: >>>> In reading up on Marshall's post on Action Links today, I came across >>>> this on a comment on RWW:
>>>> "Centralizing You By Decentralizing Social Networking" >>>> http://www.get6d.com
>>>> I thought this sounded pretty familiar:
>>>> "We're utilizing open standards such as microformats and the HTTP >>>> protocol, the fabric of the web. We considered using the XMPP >>>> protocol, but our requirement to run on most shared hosting >>>> environments killed that idea."
>>>> Anyone have any insight into the project, or how far along it is?
>>>> Chris
> -- > You received this message because you are subscribed to the Google Groups "Diso Project" group. > To post to this group, send email to diso-project@googlegroups.com. > To unsubscribe from this group, send email to diso-project+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/diso-project?hl=en.
