It makes sense really. About a week ago there was “code red” storm in the Netherlands, and first phone alarm contained something along the lines of “for more details see this Twitter account”.
Then they removed any mention of twitter from from the second message.
Doesn't sound like they needed a microblogging platform, just a web page that could be easily updated. Their use of Twitter in the first place would appear to be the crux of the problem.
Twitter has a built in notification system. People can subscribe to get alerts from it. Theoretically people can do that with RSS but, let's be honest, most people don't use RSS. I saw in another comment that they do have an RSS feed though if that's your cup of tea
I've gone so far as to create a separate autossh user with separate key, with no shell access (by setting the user's shell to /bin/false). It still permits tunneling (call ssh with -N), but does not allow shell sessions. Perfect for when you want to access remote systems via a remote tunnel but do not want to give shell access on the relaying machine to the tunnel origin. It trusts that the machine originating the tunnel will not initiate a reflection attack (by making a local forward to the remote port itself on the originating machine and causing some log messages to appear until all file descriptors are in use)[1], but that's not so unreasonable.
Then they removed any mention of twitter from from the second message.