3 ms·
What's in it for the user? I saw talk about APIs and anger over promoted tweets. Users don't know what an API is. They know when their favorite app doesn't inte
by nsxwolf 14y ago
What's in it for the user? I saw talk about APIs and anger over promoted tweets. Users don't know what an API is. They know when their favorite app doesn't integrate with their favorite service, but this hypothetical Twitter rival has to already be a favorite service.
How do you accomplish that? "Service You Don't Use is now deeply integrated with all your favorite apps". So what?
And I don't think many users are that outraged about promoted tweets.
You can ship a Twitter alternative after a weekend of coding. Then you can sit back and listen to the crickets.
I don't see a huge problem with the Twitter idea or its feature set. The big problem I see is that it's yet another data silo. One of the hottest communication technologies to come around in years is owned by a single entity.
Maybe a decentralized competitive technology is a more interesting place to go. Something that works more how email or the web does. It so far hasn't worked for Diaspora*, but how about the same concept vs. Twitter?