Favstar will shut down as a result of Twitter’s API changes for data streams
techcrunch.com
techcrunch.com
I can't believe they killed off their MacOS Twitter app, told people to use third-party apps, and now are effectively killing them off too.
(All this being said... Twitter is ripe for abuse, and locking down their API is probably one of the best ways to fix this)
I really don't understand why a social media site so large and influential is spending so little on their own product. Twitter won't let anyone develop any clients, but Twitter itself won't develop any clients either. Twitter acts like they wished no one would log in at all, they act like they're just waiting to be acquired and shut down.
These companies hire the best of the best. QED.
https://finance.yahoo.com/quote/TWTR/financials?p=TWTR
https://twitter.com/charliebilello/status/989610534801637382
I don't think moves like this solve Twitter's existential abuse problem, which I believe has far more to do with their 140 characters and unsolicited heckling than it does anything else. It turns your whole reality into gossip and this gossip overpowers any semblance of rational or reasoned discourse. It's intensely toxic and shutting off an API and some client apps changes nothing about that.
* you do something amazing, and start making money. So your source company turns off your access to the data and makes there own version * you never make enough money for them to care/notice you. They remove the source of data for non-competition related reasons/accidentally break the api and don’t care enough to fix it (if you’re not really making money presumably they’re not making money off you)
Shrug - maybe it’s simply a relatively easy way to get to the point where you can say enough buzzwords convincgly to get VC money?
If I had a great idea for software that I could do on my own with the only investments being my time + some AWS resources where hopefully I could make enough money to pay myself a decent wage and pay for the operating expenses, why not ride the wave, make some money and when the bottom falls out, shut down the AWS resources, close shop, throw it on your resume and get job.
Twitter's success is directly attributable to a fantastic native app ecosystem on mobile platforms. If there's a lesson to be learned here, I guess it's "don't make apps for platforms you don't control because they'll drop you like it's hot the moment investors want an exit"...
As an aside, Tweetie/Twitter for iPad's column based interface was one of the absolute best interfaces I'd ever seen and used on a tablet, and one I have yet to see reimplemented in a use-friendly way to this day.
Twitter basically encouraged a third-party ecosystem to blossom, then decided that rather than finding ways to monetize that ecosystem, they should start slowly strangling it to death. I can't imagine that this is happening because investors are insisting on it; yes, they want a positive return on their investment, but who's really saying, "If only you guys knife Tweetbot, the stock price will double!"? There's a very small minority of users who use third-party clients, but those users are disproportionately the highly engaged "super tweeters," if you will. Is supporting them -- ideally better than they do now -- really so expensive that it's easier to just kill them? And if the answer is yes, is it really better to keep pretending that you're not doing that, and instead just make the experience of third-party developers and dedicated Twitter users steadily worse over time?
Investors didn't say "knife the indies" but they certainly said "monetize, monetize, monetize" and Twitter decided the way to "monetize" was to force users into channels that had ads.
Sure, nobody ever told Twitter to go after Tweetbot, but it's not like anybody on the board said "wait a minute..." when this was the direction they announced in 2012. I'm lamenting the tail end of a strategy that started 6 years ago.
[0] https://www.androidauthority.com/falcon-pro-costs-132-161680...
If you want to move with your feet, Mastodon [1] is rapidly growing in popularity, and it's completely open source [2].
Disclaimer: I used to run a mastodon instance, now I run a pleroma [3] instance to save on memory/cpu usage. Feel free to ask me any questions.
[1]: https://joinmastodon.org/
Think about the money and it's not so strange. Everyone has a price.
I'm not saying it's right, but it's not a mystery. The got big off the backs of others and they've been screwing them over ever since. People building stuff on top of Twitter are crazy. They've been developer hostile for years and years now.
Mastodon is really nice, but it's fairly intensive. Precompiling the rails/webpack assets in particular made my tiny VPS choke, even with 4GB of memory I believe. It also requires Sidekiq and other services [1].
Pleroma is newer and written in Elixir/Phoenix purely as an API. It only has itself as a dependency, and it's lean enough to run on a Raspberry Pi. It offers two frontends, pleroma-fe and mastofe, the latter is a port of Mastodon's UX.
---
Features wise, Pleroma doesn't really have a lot beyond the basic functionality of subscribing to people, posting, etc. There aren't real moderation tools (yet), since it's mostly a weekend project for the core devs. Blocking instances requires an IP block still, I think.
Mastodon wins features-wise, hands down. But some things aren't really easy to reconfigure- since the frontend is baked in, changing things like the post character limit (500 chars) is tedious. In pleroma it's a simple config file change.
---
I like Pleroma personally but it's not for everyone (yet). I plan on contributing more soon to help change that.
I also was only running single user instances so I can't really discuss scaling. @technowix@niu.moe [2] would be better to ask about that, considering their instance has ~3k users [3].
[1]: https://github.com/tootsuite/documentation/blob/master/Runni...
Mastodon and Pleroma are both part of the Fediverse [2]. They work with any software that works with OStatus and the newer ActivityPub. This includes things like GNUSocial, etc.
Mastodon doesn't explain any of this well, or at all, to my dismay. (As far as I'm aware, on the joinmastodon page).
https://github.com/tootsuite/documentation/blob/master/Runni...
Ta for bringing this to my attention. I'm ploughing through the docs ...
1) Push notifications will no longer arrive
2) Timelines won’t refresh automatically
If you use an app like Talon, Tweetbot, Tweetings, or Twitterrific, there is no way for its developer to fix these issues.
Stop turning Twitter into Facebook! I'm sure it increases your engagement metrics, but at some point I'll feel overengaged, realize how much time I'm wasting and quit the app completely.
Talon supports the use-case I care about: reading all the tweets from people I follow because I care about them. Twitter and Facebook both make this nearly impossible, so I don't use them directly.
Why can't twitter make a decent app on it's own? This shouldn't be complicated...
They don't want to make a decent app. They've bought great apps and shuttered them. They want you to use the web client.
I use the web app version exclusively -- based on that I don't agree.
Both the Twitter and Facebook Android/iOS web applications constantly push you to download the native client. They even get demanding sometimes. They want to be able to send you push notifications.
but the original “like” on Twitter is back, http://2fb.me for the time being, let's see how it goes.
IMO Jack has to go, he seems to understand Square, but he seems very very out of touch with Twitter.
But every app company loses out.