Comments on: Expanding on “twitter with a brain” http://stage.vambenepe.com/archives/1127 IT management in a changing IT world Wed, 17 Mar 2010 19:31:41 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: William Vambenepe — Taxonomy of Cloud Computing Benefits http://stage.vambenepe.com/archives/1127#comment-101621 William Vambenepe — Taxonomy of Cloud Computing Benefits Mon, 11 Jan 2010 19:34:03 +0000 http://stage.vambenepe.com/?p=1127#comment-101621 [...] hasn’t yet created a major disaster (let’s see what 2010 has in store). I suggested a band-aid fix earlier, but this needs a real solution (the Cloud Security Alliance provides some guidance in this [...] [...] hasn’t yet created a major disaster (let’s see what 2010 has in store). I suggested a band-aid fix earlier, but this needs a real solution (the Cloud Security Alliance provides some guidance in this [...]

]]> By: William (@vambenepe on Twitter) http://stage.vambenepe.com/archives/1127#comment-100012 William (@vambenepe on Twitter) Tue, 01 Dec 2009 17:38:57 +0000 http://stage.vambenepe.com/?p=1127#comment-100012 Daniel: proxies may or may not be good for Twitter itself, but there is (almost) no way for them to stop them. It's in the hands of people writing apps that call the Twitter API. It's their choice whether to hard-core the Twitter endpoint URL or not. As to whether or not such proxies would be good or bad for Twitter, it's not obvious in my mind. You could also say that all the Twitter clients are bad for Twitter too because they take eyeballs away from twitter.com where they could be fed advertising. But what would Twitter be today w/o them. Daniel: proxies may or may not be good for Twitter itself, but there is (almost) no way for them to stop them. It’s in the hands of people writing apps that call the Twitter API. It’s their choice whether to hard-core the Twitter endpoint URL or not.

As to whether or not such proxies would be good or bad for Twitter, it’s not obvious in my mind. You could also say that all the Twitter clients are bad for Twitter too because they take eyeballs away from twitter.com where they could be fed advertising. But what would Twitter be today w/o them.

]]> By: Daniel http://stage.vambenepe.com/archives/1127#comment-100006 Daniel Tue, 01 Dec 2009 16:26:49 +0000 http://stage.vambenepe.com/?p=1127#comment-100006 While I think the idea has significant merit, it removes contact with Twitterees from the head Twitterer, Twitter itself, and therefore has the potential to limit their advertising business model as the system works now. If Twitter re-factors their system so that they can monitor and and measure activity through proxies that don't directly go to their endpoint, then they can preserve their potential to monetize their user base which is, after all, what most internet business models are about in some form or another. As it stands now, Twitter gains nothing and loses a lot with proxies. While I think the idea has significant merit, it removes contact with Twitterees from the head Twitterer, Twitter itself, and therefore has the potential to limit their advertising business model as the system works now. If Twitter re-factors their system so that they can monitor and and measure activity through proxies that don’t directly go to their endpoint, then they can preserve their potential to monetize their user base which is, after all, what most internet business models are about in some form or another. As it stands now, Twitter gains nothing and loses a lot with proxies.

]]> By: Chuck Shotton http://stage.vambenepe.com/archives/1127#comment-99943 Chuck Shotton Mon, 30 Nov 2009 14:01:45 +0000 http://stage.vambenepe.com/?p=1127#comment-99943 I think the idea of using Google App Engine (or the equivalent -- a Tomcat server somewhere) is a perfect fit for implementing quick and easy-to-deploy proxy "modules". It should even be possible to stack several of them (a la Pipes) to get desired mix/match functionality for your Twitter proxy. I've got lots of the necessary code already implemented in my GAE version of a rssCloud server. It would make an interesting collaborative project to turn it into an open Twitter API platform and see what happens. (Interestingly, it's only a small step from proxy to basic Twitter server...) I think the idea of using Google App Engine (or the equivalent — a Tomcat server somewhere) is a perfect fit for implementing quick and easy-to-deploy proxy “modules”. It should even be possible to stack several of them (a la Pipes) to get desired mix/match functionality for your Twitter proxy.

I’ve got lots of the necessary code already implemented in my GAE version of a rssCloud server. It would make an interesting collaborative project to turn it into an open Twitter API platform and see what happens.

(Interestingly, it’s only a small step from proxy to basic Twitter server…)

]]>