Comments on: Twitter DoS and single points of failure http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/ Sat, 13 Feb 2010 12:35:10 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Matt Katz http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26642 Matt Katz Wed, 12 Aug 2009 19:52:31 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26642 I've been trying to encapsulate the argument for this issue, because a decent phrase can make the difference in a discussion. I've come down to this. The best defense against Distributed Denial of Service is Distributed Delivery of Service. The web of services can be resilient in ways that no single site can. I’ve been trying to encapsulate the argument for this issue, because a decent phrase can make the difference in a discussion. I’ve come down to this.

The best defense against Distributed Denial of Service is Distributed Delivery of Service.

The web of services can be resilient in ways that no single site can.

]]> By: Srini Vemula http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26622 Srini Vemula Tue, 11 Aug 2009 22:17:34 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26622 Correction to the above url it is http://www.poboxpress.com Correction to the above url it is http://www.poboxpress.com

]]> By: Srini Vemula http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26620 Srini Vemula Tue, 11 Aug 2009 22:14:07 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26620 We are working with Jaikuengine team and also pubsubhubbub team to bring a functionality where user's tweets can flow into http://www.pboxpress.com and also users xPressions from poboxpress.com move to twitter or subscribed to any system. We are using pubsubhubbub to speed up the ATOM and RSS feeds. We are running this on Cloud (Google Appengine) Our aim is to build open, decentralized microblogging system. Any suggested use cases to buid more open, federated system? Thanks Srini Vemula We are working with Jaikuengine team and also pubsubhubbub team to bring a functionality where user’s tweets can flow into http://www.pboxpress.com and also users xPressions from poboxpress.com move to twitter or subscribed to any system. We are using pubsubhubbub to speed up the ATOM and RSS feeds.

We are running this on Cloud (Google Appengine) Our aim is to build open, decentralized microblogging system.

Any suggested use cases to buid more open, federated system?

Thanks
Srini Vemula

]]> By: ~Jake http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26612 ~Jake Tue, 11 Aug 2009 17:23:51 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26612 Have you had a look at where people are taking web hooks? Beyond the push content concept inPubSubHubbub to distributed loosely coupled applications which act on information and call other applications. http://www.slideshare.net/progrium/web-hooks-and-the-programmable-world-of-tomorrow-presentation For a social network application all I need is for my callback/publisher url to be my openID server and we have some protocols around privacy e.g many to many encryption so I don't need to trust intermediate hubs, and hope someone funds commodity hubs to handle the traffic. Have you had a look at where people are taking web hooks? Beyond the push content concept inPubSubHubbub to distributed loosely coupled applications which act on information and call other applications.

http://www.slideshare.net/progrium/web-hooks-and-the-programmable-world-of-tomorrow-presentation

For a social network application all I need is for my callback/publisher url to be my openID server and we have some protocols around privacy e.g many to many encryption so I don’t need to trust intermediate hubs, and hope someone funds commodity hubs to handle the traffic.

]]> By: Jean Russell http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26470 Jean Russell Thu, 06 Aug 2009 19:56:14 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26470 Thanks! You might appreciate this awesome post today from and Chief Scientist of Social Network Analysis at Orgnet.com --- No Tweets for You at http://www.thenetworkthinker.com/2009/08/no-tweets-for-you.html Backs up your argument here. Thanks! You might appreciate this awesome post today from and Chief Scientist of Social Network Analysis at Orgnet.com — No Tweets for You at http://www.thenetworkthinker.com/2009/08/no-tweets-for-you.html

Backs up your argument here.

]]> By: Michael Lewkowitz http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26468 Michael Lewkowitz Thu, 06 Aug 2009 19:31:55 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26468 There's no question we need a layer underneath Twitter - to support public micro-messaging as a medium. There's also the PubSubHubBub stuff. No one has services that have been proven yet to scale to the network-grade capacity we will need as this medium grows. It's a tough problem but not one that can't be solved (e.g. telecoms and financial services have network-grade systems). This medium has the potential as most accessible, participatory public medium in history. What underpins it needs to support that and be held in the interests of the people that use it. While I love the initial efforts of the laconi.ca, SMOB, OpenMicroBlogging, and PubSubHubbub folks - I'd love a more weighty, dedicated effort that came to this from the perspective of it as a public medium. And really, what better investment could their be for public benefit? With what little has gone into Twitter we've seen some incredible impacts in reporting, transparency, and disaster response. If the state department is willing to ask Twitter to stay live and treat it effectively like an essential public infrastructure, why wouldn't a couple of leading foundations (Knight, Shuttleworth, for example) step up and support this. It would undoubtedly be the best 'investment' in public benefit they could ever make. There’s no question we need a layer underneath Twitter – to support public micro-messaging as a medium. There’s also the PubSubHubBub stuff. No one has services that have been proven yet to scale to the network-grade capacity we will need as this medium grows. It’s a tough problem but not one that can’t be solved (e.g. telecoms and financial services have network-grade systems).

This medium has the potential as most accessible, participatory public medium in history. What underpins it needs to support that and be held in the interests of the people that use it. While I love the initial efforts of the laconi.ca, SMOB, OpenMicroBlogging, and PubSubHubbub folks – I’d love a more weighty, dedicated effort that came to this from the perspective of it as a public medium.

And really, what better investment could their be for public benefit? With what little has gone into Twitter we’ve seen some incredible impacts in reporting, transparency, and disaster response. If the state department is willing to ask Twitter to stay live and treat it effectively like an essential public infrastructure, why wouldn’t a couple of leading foundations (Knight, Shuttleworth, for example) step up and support this. It would undoubtedly be the best ‘investment’ in public benefit they could ever make.

]]> By: Tom http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26467 Tom Thu, 06 Aug 2009 19:03:24 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26467 I don't know why you mentioned laconi.ca instead of plurk or jaiku. I think you meant to mention the OpenMicroBlogging protocol: http://en.wikipedia.org/wiki/OpenMicroBlogging I don’t know why you mentioned laconi.ca instead of plurk or jaiku. I think you meant to mention the OpenMicroBlogging protocol: http://en.wikipedia.org/wiki/OpenMicroBlogging

]]> By: Ben Werdmuller http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26466 Ben Werdmuller Thu, 06 Aug 2009 18:45:02 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26466 Josh: <a href="http://benwerd.com/2009/05/google-wave-is-exciting-and-transformative/" rel="nofollow">I completely agree</a> :) Josh: I completely agree :)

]]> By: Josh Russell http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/comment-page-1/#comment-26465 Josh Russell Thu, 06 Aug 2009 18:42:55 +0000 http://benwerd.com/2009/08/twitter-dos-and-single-points-of-failure/#comment-26465 Wave. if FB, Twitter, livejournal (maybe?) build on the Wave *protocol* then we not only get decentralisation, but also interoperability. that's why google opensourced it, because it's too big an idea for one company to take responsibility for. quite rightly so, when taking into account identity management, digital rights, content ownership etc.. mark my words! :) Wave.

if FB, Twitter, livejournal (maybe?) build on the Wave *protocol* then we not only get decentralisation, but also interoperability.

that’s why google opensourced it, because it’s too big an idea for one company to take responsibility for. quite rightly so, when taking into account identity management, digital rights, content ownership etc..

mark my words! :)

]]>