Japan prefectures drift away from posting disaster warnings on X

Post by JohnFen » Thu, Aug 10, 2023, 4:17 PM UTC

housemusicfan wrote: post #19

slyall wrote: post #15

Personally I found the shuffles with the API a huge pain. I have a small bot and I previously just used a command line client to post my automated tweets. With the API changes and new keys those clients all stopped working and the maintainers were uninterested in fixing them. So now I have to implement oauth myself. Which as a busy person and poor programmer is a significant amount of work. I went with paying IFTT a…

> Personally I found the shuffles with the API a huge pain. Why is it when Apple does this nearly every year right on schedule, they're lauded as stewards of progress?

Post by JohnFen » Thu, Aug 10, 2023, 4:24 PM UTC

housemusicfan wrote: post #10

bsder wrote: post #5

Um, good? Facebook and Twitter should never have been allowed to become the default for this, anyway . These services should have an always up web page. With an RSS feed. So anybody can connect to it and shove the warnings out however they want.

RSS is a great, albeit forgotten, technology. The problem is the social media-obsessed NPCs of the world don't know how to use it. It didn't help that all the major browser vendors removed the technology and you need a standalone client these days.

Post by diebeforei485 » Tue, Aug 15, 2023, 7:08 PM UTC

ehnto wrote: post #32

diebeforei485 wrote: post #14

Earlier quoted context omitted.

It's difficult for most transit agencies to maintain the sort of uptime that a social media company does. But there should be no login wall on posts from government agencies (grey check).

A third party service who's contracted to do it would be the right move in that case. Operating critical processes through a company with no obligation to provide that service is dumb. The evidence is in the outcome here. We trust the metro companies to run critical infrastructure for our cities, I am sure they can organise a website.