rdale
EF5
Actually that's not quite true, tornado warnings will interrupt other programming in progress instantly. But point is the same. NWR usage is too low to be relevant.
That's not how it started, but when people started saying that this was a bad decision, and the community will regret it, blah blah that's what it turned into.
Ehh, that would be a quick discussion: Sirens are useful only in areas where outdoor notification is otherwise hard to do. Only useful when local alerting agencies use them correctly. End of discussion
There are many free apps for alerting already - if people aren't taking the time to download those, they aren't really that interested. And also remember that every newer phone is automatically getting Tornado Warnings based their cell location, and those are really the only important convective warnings the public needs or cares about.
You wouldn't track each user, although they already do that for specialized advertising. Maybe track it at a state level, and then just send an event to every user, and if that user's client determined that it matched the criteria, a small chunk of script on the page would display a warning. Cost would be comparatively minimal, but Facebook doesn't really seem to be a team player unfortunately. I'm also guessing the problems with browser-based location services and the lack of demand are why this hasn't been done. Still, kudos to Google for doing it.