3 ms·

So instead of getting the API limit raised, you should start another Twitter? Really?

stesch 14y ago
Seeing how many companies are unhappy with Twitter's new policies, it seems a bit strange that they don't band together and make something different/new.
bjelkeman-again 14y ago
We don't need another Twitter. The model where one company owns an information channel like this is "broken". It is the CompuServe of short messages. We need a distributed architecture, so that nobody owns it. Like SMTP... oh wait, spam. Hmmm. I think that there must be an architecture that solves that problem. Getting it adopted though, is a whole different ball game.
grey-area 14y ago
Someone's already done that, all you have to do is use it (maybe as well as twitter if you want): https://app.net/ https://app.net/ https://tent.io/ https://tent.io/ Here's why you shouldn't depend on Twitter or other closed platforms long term: http://daltoncaldwell.com/what-twitter-could-have-been http://daltoncaldwell.com/what-twitter-could-have-been
- mehrzad 14y ago
  Just saying, Tent is great. Good community, great third party developer support, and though for now it's just a Rails app you can run on your server, it's going to be something more abstract like IRC. The co-founders also really know their stuff.
  - Titanous 14y ago
    I'm one of the Tent architects. Thanks for the kind words :) Tent is actually a protocol, so anyone can implement their own server. We don't use Rails, but we do have reference server implementation called tentd that is written in Ruby: https://github.com/tent/tentd https://github.com/tent/tentd
- bjelkeman-again 14y ago
  Isn't app.net a Twitter clone, i.e not a federalised service, like tent.io seems to be? Twitter could charge me a subscription fee for tokens that I could use on whatever application I wanted. That would remove some of the issues. Twitter makes money, I can use it however I want. But I still think something like tent.io is where we should go.

Seeing how many companies are unhappy with Twitter's new policies, it seems a bit strange that they don't band together and make something different/new.

bjelkeman-again 14y ago

We don't need another Twitter. The model where one company owns an information channel like this is "broken". It is the CompuServe of short messages. We need a distributed architecture, so that nobody owns it. Like SMTP... oh wait, spam. Hmmm. I think that there must be an architecture that solves that problem. Getting it adopted though, is a whole different ball game.

grey-area 14y ago

Someone's already done that, all you have to do is use it (maybe as well as twitter if you want): https://app.net/ https://app.net/ https://tent.io/ https://tent.io/ Here's why you shouldn't depend on Twitter or other closed platforms long term: http://daltoncaldwell.com/what-twitter-could-have-been http://daltoncaldwell.com/what-twitter-could-have-been

mehrzad 14y ago
Just saying, Tent is great. Good community, great third party developer support, and though for now it's just a Rails app you can run on your server, it's going to be something more abstract like IRC. The co-founders also really know their stuff.
- Titanous 14y ago
  I'm one of the Tent architects. Thanks for the kind words :) Tent is actually a protocol, so anyone can implement their own server. We don't use Rails, but we do have reference server implementation called tentd that is written in Ruby: https://github.com/tent/tentd https://github.com/tent/tentd
bjelkeman-again 14y ago
Isn't app.net a Twitter clone, i.e not a federalised service, like tent.io seems to be? Twitter could charge me a subscription fee for tokens that I could use on whatever application I wanted. That would remove some of the issues. Twitter makes money, I can use it however I want. But I still think something like tent.io is where we should go.