<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 3/12/19 1:45 PM, William Herrin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP-guGVYGnr914+8CWLf7yN-R_7VNSZSO4+dXkKte-rsKxfEZA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">On Tue, Mar 12, 2019 at 11:57 AM Michael Thomas
<<a href="mailto:mike@mtcc.com" moz-do-not-send="true">mike@mtcc.com</a>>
wrote:<br>
> Yes, that's exactly my point: it should just be a
requirement of the<br>
> hardware platform to implement this. Just like e911.
Enumerating the<br>
> types of devices that are required to implement this is way
easier than<br>
> enumerating the types of apps/sites that need to implement
it. All the<br>
> government needs to do is set up the server infrastructure
to source the<br>
> alerts.<br>
<br>
Hi Mike,<br>
<br>
In many cases, only the foreground app has a clear understanding
of the state of the screen. Not the OS and definitely not the
hardware platform. I'd be super pissed if I died in Overwatch
because the BIOS tried to take over the screen to display an
amber alert.</div>
</blockquote>
<p><br>
</p>
<p>But if you're about to be incinerated in real life -- Paradise --
you want the alert. We're not talking BIOS here, we're just
talking a normal IP client program that has elevated privileges to
take over the outputs as necessary. And, of course, we want to be
able to prioritize things like Amber alerts to zero when we're
sitting at home watching tv. Really, this is nothing more than
Biff over IP.</p>
<p>Mike<br>
</p>
</body>
</html>