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
Why governments would ever use a private service for critical use baffles me.
Create your own emergency notification system!
They have one, but you also want information to be where people are. Especially if where people are is full of misinformation and rumours.
Japan has various earthquake notification systems. Tweets are just one more way to get the information to the people on a platform they use.
Those never turn out well.
Running their own mastodon instance should be viable though.
I remember seeing that they did have a fediverse account? This seems related to that
Yup see here:
https://lemmy.ca/post/3167523
It’s also in the article linked above:
The Los Angeles/ California earthquake alert system worked just fine today.
Does that go through regular EAS? Wondering.
FWIW, Japan does have emergency alerts on iOS and Android, same thing as the Netherlands and the UK.
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.
Cell phones already have the emergency alert system they could just use that.
Remember when just about every government employee was carrying around a BlackBerry device for official business?
Pepperidge Farm remembers.
That’s different. They had signed contacts and were legally obligated to provide service. Twitter is a free service that can be turned off at any time, with no notice, and is run by a schizophrenic twat with a god complex. It’s just monumentally stupid to put lives on the line through a service like that.
I remember when they all loved the Nextel PTT phones.
This same issue happened during wildfire season in BC, Canada if I recall. A small polite media outrage over it, then forgotten.
Best case scenario would be an independent, international system developed within and for the emergency services community worldwide. Judging by the way firefighters travel internationally to fight forest fires worldwide, the community could be strong enough to support a solution like that, in my opinion.
deleted by creator
For reference, the article I’m referring to:
https://www.cbc.ca/news/canada/british-columbia/twitter-policy-change-hampers-drivebc-1.6894793
“Social media’s reliability in emergencies questioned after Twitter limit blocks DriveBC posts” (Jul 12).
Whether a provincial traffic account posting emergency info counts as news links for these large companies or not, it’s a pretty ugly look for them to have been blocking emergency information, and it doesn’t look any better now 6 months later.
The whole thing is pretty typical (Canadian) government “not enough, and too late” -style regulation regardless, but these social media sites could think twice about playing the villain so readily in response.
Hate to say it but I would commonly get alerts from Twitter in the before times about local issues before I would get notified by my local government. Sadly they switched to encrypted radios so I can’t even keep up that way either these days
Because it’s often easier, cheaper, and more efficient in cases that mirror public needs. Alerting, SMS, cloud storage, all are solved and competitively priced. And don’t get me wrong, there ARE use cases for doing certain things custom or internally. There will need to be a mix of things.
The issue, is having an appropriate SLA and having the ability to hold companies accountable when it’s not met. You need stated provisions that won’t happen. Most commercial enterprises already operate under this model successfully, however many of the tools don’t have SLAs around an earth quake. Most companies are willing to provide those provisions but it totally will come with extra cost which is typically not budgeted or sales teams or contracting officers are not equipped to have these conversations.