News for hackers. Stuff that matters.
Re:After Carping About NBC’s Olympics Coverage, Journalist S... by vidar on Monday July 30, 2012 @04:12PM (#4314424)
But its fair to say that it would not have been a problem had the coverage been positive. This is the price of playing with the big boys, you have to stick up for your partners.

There is no way you can go the media company route (vs. the api/infrastructure route) and not get this conflict.

Re:After Carping About NBC’s Olympics Coverage, Journalist S... by killerswan on Monday July 30, 2012 @04:22PM (#4314481)
Seems like app.net is worth another look... https://join.app.net/
Re:After Carping About NBC’s Olympics Coverage, Journalist S... by tree_of_item on Monday July 30, 2012 @07:44PM (#4315278)
Why? It's not open source and is vulnerable to the same issues, i.e. a single point of failure should some large entity deem a message undesirable.

It'd be better to take a look at things like status.net, or more low level solutions such as http://scripting.com/stories/2012/07/25/anOpenTwitterlikeEco....

Re:After Carping About NBC’s Olympics Coverage, Journalist S... by seagreen on Tuesday July 31, 2012 @01:50AM (#4315916)
We need LINT! (LINT Is Not Twitter) Any other resource recommendations besides the Winer article?