Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter to Client Developers: Drop Dead

daringfireball.net

Post reply on HN
Print view View original

71–80 of 187 posts

Re: Twitter to Client Developers: Drop Dead

#71

Post by virmundi »

ricardobeat wrote: post #58

> To prevent malicious use of the Twitter API and gain an understanding bla bla bla... Translation: so that we can charge even light API users. This will surely backfire - some services will switch from API usage to screen-scraping, resulting in an even higher load on twitter's servers.

At that point Twitter will simply block IP address, or some such. Sure there will be a game of catch me if you can, but the end is that no one really wins, and Twitter may suffer because people will use it to bad mouth Twitter. Enough user sentiment, even if it start from the devs of a few highly used apps, and Twitter might want to reconsider.

Re: Twitter to Client Developers: Drop Dead

#73

Post by maxpow4h »

seagreen wrote: post #70
maxpow4h wrote: post #49

From here, I think we should move to a distributed model, like email and xmpp. It needs to be Open Source so anyone can run it and everyone owns their data. It needs to be compatible with current Twitter apps so all it requires is setting the API root. It needs to be distributed so anyone can follow anyone anywhere. There is no owner or root, there is no place to shut down. Proof of concept: https://nstatus.herokuapp…

What would its advantages be over status.net/identi.ca?

status.net is great, but I would have federation where you can add a server as a source rather than just a user. Then if that server has a @fred, @fred would always be resolved to the @fred on that server. In conflicts, you should be able to resolve these conflicts and proxy names yourself. (my proof of concept doesn't do this)

Maybe even taking Diaspora and taking out everything except 140char status updates AND adding an API compatible with Twitter apps would be a better approach.

edit: clarity to first sentence.

Re: Twitter to Client Developers: Drop Dead

#76

Post by colmvp »

andrewfelix wrote: post #50
dinkumthinkum wrote: post #40

Twitter's developer problem is probably at about level 9 right now. My question is what's really the big deal. Twitter can do what they want and really more to the point, I don't think Twitter should be the primary focus of innovation from our community. It's a stream of mostly nonsensical 140 char messages. I get it it, it's amazing ... but come on, we can get past Twitter.

>It's a stream of mostly nonsensical 140 char messages. This maybe true for a lot of tweets. But my stream is filled with live updates of interesting stuff from around the world. Twitter has been instrumental in getting news out of war zones for example.

Yeah I don't know why Twitter gets so much hate. It is similar to Reddit: What you get is what you subscribe to.

Re: Twitter to Client Developers: Drop Dead

#77

Post by pedalpete »

joering2 wrote: post #51

Sometimes I tend to see the dark side of human in everything they do. Sorry, its just the way I am. I say when twitter was still this little chick, their approach was "we love all users, we welcome engineers; build amazing tools and surprise us!". I think the reason for that was to speed up the process of spreading the word - a simple fact that geek working on twitter 3rd party is still a human with plenty of friends…

Square doesn't have a network effect, it doesn't really matter if one store uses square, and the neighboring store uses google wallet, dwolla, or something else.

Re: Twitter to Client Developers: Drop Dead

#78

Post by azakai »

dm8 wrote: post #52
cletus wrote: post #36

This doesn't surprise me at all. When you develop on someone else's platform, you have to walk a fine line between not being successful at all and being too successful such that the platform provider co-opts your business (maybe you get lucky and get bought out). This is nothing new. Such moves as this were (IMHO) inevitable. They'll slowly chip away at anything they see as taking revenue from them. The part I disagr…

Everyone cites Myspace. Either Twitter or Facebook does something controversial and we hear everyone citing Myspace. Myspace didn't lose it's user base due to amazing UX for end-user. They lost their user base due to combination of bad UX and "mobile" user base. Majority of Myspace users were teenagers and by the time they went to college they had hot new social network in form of Facebook, which was exclusively for…

> I think App.net can have number of use cases like firehose of realtime feeds for devs

Devs already have a twitter-like firehose, and it's even open source, identi.ca

Re: Twitter to Client Developers: Drop Dead

#79

Post by AVTizzle »

thought_alarm wrote: post #41

Of all the social media and web services that have cropped up in the last 5 years, Twitter was the one that really filled me with joy. It's so simple! It's just plain text in bite sized pieces at a time. And it's universal! It works just as well on state of the art hardware as it does on a crappy SMS dumbphone or green-screen serial terminal. And it's as compelling in Egypt or Pakistan as it is in New York or London.…

Would love to see a screenshot (or picture?) of that!
Post reply on HN