ruby's had this problem for ~2 decades now. like, the "rockstar dev" archetype literally became big directly because of ruby's popularity and perception at the time
I haven't been active in/near the ruby space for a number of years now so I can't speak to the modern details well at all, but I wouldn't be too surprised to learn that the various branches of it haven't really learned how to deal. I will say that I have seen some improvement over that period, but... yeah
from when I last looked into this: twitter 100% has[0] (unstated) web API ratelimits for various subservices[1], but getting direct API creds became a "give us your actual phone number" thing even before felon took it over...
so I just decided to tombstone my account by making it private, updating bio, and never logging in again
not willing to give them what they want for API access. might at some point go write some web automation to recurringly click a delete button? idunno
[0] - ....well, 4 years ago, "had". probably maybe still does, on whatever parts of the haproxy or whatever config didn't get absolutely fucking destroyed in felon's mania to rebrand it to "x" overnight (a process which failed hilariously badly for weeks and I still think fondly of to laugh at)
[1] - when going through the "your interests" list (hidden deep in settings), if you unticked too many boxes too quickly you'd hit a webserver-enforced ratelimit on request limits and then half the webapp would get a bit fucky for an hour. ratelimit was something like 30/min with a 1/m type token-bucket refresh. quite the shitshow