Comment by debugnik
14 hours ago
Last time my city had a water cutoff due to a broken main, the city hall posted on Twitter (and I think Facebook?) where and when to queue for drinking water sooner and much more often than on any other channels, their own website included.
The NYC subway system now writes, on X, "Customer care has moved to the MTA app, chat with us there 24/7. Get service status, arrival times and more all in one place. Visit MTA.info/apps". The web page with similar data is "MTA.info".
There are MTA data feeds, in General Transit Feed Specification format, for program use. Those are for systems that update maps.
The MTA dumped Twitter/X in 2023 because Twitter/X wanted to charge them for using their API, and the MTA refused. [1] The MTA also said that Twitter/X had too much downtime.
When the MTA first got into social media, the person who took the job demanded a desk in the rail control center, so she could see all the displays and immediately hear about problems. If someone mentioned a problem on Twitter, she'd reply immediately. That was the right idea. Few organizations have the guts to put the control room on social media.
[1] https://www.mta.info/press-release/statement-mta-acting-chie...