Chris TrottierYeah, I think Twitter can go f*ck off with their so-called "developer" agreement.
Here's what devs will actually do.
They'll politely give Twitter the middle finger, and then continue to build out the Fediverse ecosystem.
Elon Musk is going to quickly discover he's not the only game in town, and developers have time and resources to build something else.
The tech press doesn't understand that Twitter just killed the only thing that ever made them innovative:
3rd party access to their API
This should be a bigger story because, in reality, almost all of Twitter innovations came from 3rd parties -- including the word "tweet" itself.
The most impressive thing about Twitter's meltdown is how much Elon Musk doesn't understand its core value.
Again, with no 3rd party API access, there's no technological innovation on Twitter.
testing@atomicpoet
the big publishers who have signed new agreements with twitter do not understand either
the big publishers who have signed new agreements with twitter do not understand either
beSpacific@atomicpoet one could say this mirrors the concurrent disassemblage of the republican party - piece by piece or chunk by chunk - at an increasing velocity - throwing out sparks that are causing massive destructive fires within our society. Mastodon will survive and thrive as folks wish to be here, and respect communication and knowledge sharing.
Voron@atomicpoet Control is priceless. That’s the way those who are billionaires think
Mike Garuccio@atomicpoet idk I think how weirdly unnecessary it is may rank even higher. I get they want to monetize those users, but 10 minutes of thinking about it would yield a ton of ideas that do that better while pissing off way fewer people. Force third party’s to show ads, tie api access for users to blue, or even just charge devs for access. Phase it in carefully and add a feature or two and they probably could have gotten away with all three.
Adam Dalliance@atomicpoet My Twitter-To-RSS thing continues to work ( https://github.com/revpriest/fudz )
But the moment it stops working is the moment I stop reading anything on twitter.
They can revoke it easily, it uses the client-key
AAAAAAAAAAAAAAAAAAAAAPYXBAAAAAAACLXUNDekMxqa8h%2F40K4moUkGsoc%3DTYfbDKbT3jJPCEVnMYqilB28NHfOPqkca3qaAxGfsyKCs0wRbw
Which I took from Nitter's codebase.
Nitter continues to work.
But all they gotta do is revoke that key, and then I stop reading anyone on twitter at all.
GitHub - revpriest/fudz: Fudz: It will fuzz with feeds. Twitter to RSS, Mastodon to RSS, Fiddle with existing RSS feeds.
Fudz: It will fuzz with feeds. Twitter to RSS, Mastodon to RSS, Fiddle with existing RSS feeds. - GitHub - revpriest/fudz: Fudz: It will fuzz with feeds. Twitter to RSS, Mastodon to RSS, Fiddle wit...
Heath@atomicpoet Am I wrong in remembering that 'pull-down to refresh' which has become pretty ubiquitous across the board, not just in twitter apps, was orginally a Tweetie innovation?
Ryan Rampersad@HeathC @atomicpoet Was it tweetie?
@ryanmr I think so
Andrew H – № 2025@atomicpoet and their current app (based originally on tweetie?)
Tanya Harrison@atomicpoet @JonathanMosen Sadly I suspect the new Mr Birdhead is paying the tech press to stay quiet on this 😔