Japanese disaster prevention X account can’t post anymore after hitting API limit - Dexerto
www.dexerto.com
Japanese disaster prevention app NERV can't post to the platform after hitting X's API rate limitations.

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

  • AbidanYre@lemmy.worldEnglish
    5821·
    11 months ago

    Create your own emergency notification system!

    Those never turn out well.

    Running their own mastodon instance should be viable though.

    • Otter@lemmy.caEnglish
      46·
      11 months ago

      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:

      Luckily, the creators of the NERV App, Gehirn Inc, have created an app-based alternative for users to get information in real-time, as well as running a Mastodon account.

    • BrkdncrEnglish
      17·
      11 months ago

      The Los Angeles/ California earthquake alert system worked just fine today.

      • Flaky@iusearchlinux.fyiEnglish
        9·
        11 months ago

        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.

    • hansl@lemmy.worldEnglish
      86·
      11 months ago

      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.

        • hansl@lemmy.worldEnglish
          53·
          11 months ago

          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.

      • Mane25@feddit.ukEnglish
        72·
        11 months ago

        Is Twitter/X viable for that? They can decide, and have, to randomly put information behind login walls.

        • hansl@lemmy.worldEnglish
          21·
          11 months ago

          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.

          • Mane25@feddit.ukEnglish
            4·
            11 months ago

            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.

            And if X isn’t viable there are other platforms that are.

            I mean yes obviously, there are much more viable platforms like Mastodon, or even a self-hosted website.

            • hansl@lemmy.worldEnglish
              12·
              11 months ago

              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.