A growing number of prefectures have stopped posting disaster warnings on the platform due to limits on the number of free posts allowed.
Imagine posting a hurricane coming your way and the message is:
-
blocked because Musk called it woke propaganda
-
hit the API ceiling and causes a server error
-
blocked since people need to an account and follow Elon first
-
new Twitter update breaks services… For the twelfth time.
-
filtered because the user has seen to many tweets in the past few hours
-
didn’t have Twitter Blue/Red/Ultron so the message was supressed
-
It sounded weird that they’d have reached the 1500 monthly tweet limit so quickly, but apparently there’s also a limit of 50 tweets per 24-hour period. In one prefecture that they use as an example, there are 45 cities, towns and villages, and each one needs it’s own specific warning. So if a big storm comes through, they’d use up all their daily tweets on the first warning, and there’d be no room for updates. So that’s what the issue was.
Makes sense, a bunch of stuff on twitter is broken. We’ve had embedded twitter feeds (most recent 2 or 3 posts) on our work websites for years and they broke that functionality in June. I guess they didn’t want the extra traffic from website embeds?
Eh; I can trigger 429 errors that log me out of the service by just keeping the page open. I’m not sure of anyone is supposed to keep using the service for free in any official capacity.
Toyko Drift
RSS!!!
Tokyo drifts?
