Japanese disaster prevention X account can’t post anymore after hitting API limit - The issue has arisen after major Tsunami warnings have been issued in areas of Japan following a strong earthquake::undefined
Japanese disaster prevention X account can’t post anymore after hitting API limit - The issue has arisen after major Tsunami warnings have been issued in areas of Japan following a strong earthquake::undefined
Is Mastodon even viable for time sensitive information? You need to wait for your instance to propagate the post from their instance which can take time.
As opposed to waiting until next month for your API call limit to reset?
I’d suggest they join a system that has users, proper SLA and an open frontpage.
As much as you might like Mastodon for being open, there are no SLA between instances. Bluesky or Threads likely do.
Not saying they shouldn’t start their own Mastodon, but not for emergency and time sensitive things. Or just for people who can’t access those other services. More options also mean more reach.
They made their own: https://unnerv.jp/@UN_NERV
Is Twitter/X viable for that? They can decide, and have, to randomly put information behind login walls.
They technically still have an SLA, but it’s unclear how much they respect it. And if X isn’t viable there are other platforms that are.
SLA? If that means something like “service level agreement” (I don’t know, you didn’t specify, I’m guessing) then I can still find examples where it falls well below what I would expect from a public service such that if there was an agreement in place that I would definitely be opposed to it as a tax payer.
I mean yes obviously, there are much more viable platforms like Mastodon, or even a self-hosted website.
And again, which was the point of my original comment, Mastodon may not do great when you need to propagate the post to other platforms. Unless you know something I don’t, Mastodon is horrible for time sensitive information, since it can take hours to get to your instance.