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

41–50 of 187 posts

Re: Twitter to Client Developers: Drop Dead

#41

Post by thought_alarm »

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.

Whenever I get fed up with the complextiy of Facebook or Google+ I'll load up Twitter on an old Apple II, via TTYtter and a serial connection; I'll watch the green text scroll along at 1200 baud and think about how this one simple, geeky text service, pure as a 1980s BBS, somehow made it, worldwide, in 2012.

And now they're hellbent on ruining all of that. Fuck Twitter.

Re: Twitter to Client Developers: Drop Dead

#42

Post by pablasso »

streptomycin wrote: post #15
andrewfelix wrote: post #7

Utter hypocrisy that they're discouraging third party clients, after having acquired one. app.net suddenly looks more attractive.

app.net looks more attractive, until the same shit starts happening there in 5 years. The problem is walled garden social networks. It's a fundamentally bad idea for everyone involved, except the people who own it and can turn a profit. StatusNet/Identica is a much better solution to this problem than yet another walled garden. Free, open source, and federated. How many times does the same shit need to happen before…

The whole point with app.net is that this doesn't happens. They don't mind that you use the data any way because you're paying for the platform, not the client.

Re: Twitter to Client Developers: Drop Dead

#43

Post by glesica »

jmduke wrote: post #11
refulgentis wrote: post #5

Earlier quoted context omitted.

The overall issue with the diagram is, not only are they MBA buzzwords, but it's a silly diagram that has no meaning – they're dressing up 'things we don't want you to do anymore' as a technical diagram in a two-dimensional space that makes little to no sense.

What doesn't make sense about the diagram?

Speaking only for myself, the diagram makes sense, technically speaking, but it is totally unnecessary and adds nothing to my understanding of the article. It's the type of thing I would expect some manager to ask for because there were no pictures on a given page and it needed to be "spiced up".

Re: Twitter to Client Developers: Drop Dead

#45

Post by sequoia »

What client devs have actually stopped development and abandoned/shut down their applications in response to Twitter's client TOS changes? I hear lots of griping and moaning it seems like lots of the major client players are developing nonetheless, which says to twitter "keep doing what you're doing."

Re: Twitter to Client Developers: Drop Dead

#47

Post by Spooky23 »

ziadbc wrote: post #6

Twitter wants to give you access to the data. Their client is their main product. Thus, every 3rd party client is competing with their main product, that seems to be a fact. Theres no way to stop you from building one anyway, twitter knows that. If you go against their rules, you're a revolutionary, and if you win that revolution, they'll have to deal with you. You can't expect however, that the incumbent is going to…

The data is their real product.

Re: Twitter to Client Developers: Drop Dead

#49

Post by maxpow4h »

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.com

Source: https://github.com/maxpow4h/nekomimi

I wrote about the requirements of it here: http://maxpow4h.com/blog/twitter/

edit: you can use any username with any password to sign in to nstatus. It then uses that password for your username. You can even do this from the official iOS Twitter app, just sign in.

Re: Twitter to Client Developers: Drop Dead

#50

Post by andrewfelix »

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.

Post reply on HN