From: Dave Taht <dave.taht@gmail.com>
To: "Livingood, Jason" <jason_livingood@comcast.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] [Bloat] OT: National test of the emergency broadcast system
Date: Wed, 11 Oct 2023 07:59:38 -0700 [thread overview]
Message-ID: <CAA93jw6HaC7bcx_BPikd39LxLCKP5y8Vszi15SYeTVXivTjM-Q@mail.gmail.com> (raw)
In-Reply-To: <2AB4C2EF-0E4B-4B30-9248-496CE72F287D@comcast.com>
On Wed, Oct 11, 2023 at 6:52 AM Livingood, Jason
<jason_livingood@comcast.com> wrote:
>
> The technology used for these alerts is really ancient. It'd be nice to see these alerts move to IP networks in some manner - perhaps by requiring streaming sites to carry them (since the % of legacy cable video service is getting so low).
Chat protocols and web notifications, also come to mind.
> On 10/4/23, 14:43, "Bloat on behalf of Dave Taht via Bloat" <bloat-bounces@lists.bufferbloat.net <mailto:bloat-bounces@lists.bufferbloat.net> on behalf of bloat@lists.bufferbloat.net <mailto:bloat@lists.bufferbloat.net>> wrote:
>
>
> I was really comforted at what appeared to me at least, to be a very
> successful test of the USA emergency broadcast system. The alarms went
> off in multiple places in the coffee shop in Santa Cruz within a few
> seconds of each other, and while startled, everyone looked at the
> message, and went back to work.
>
>
> I have been wondering how far along shakealert.org has got? While I
> was not there for the big one in 1989, having a robust alerting
> feature like this everywhere, would help.
>
>
> --
> Oct 30: https://urldefense.com/v3/__https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html__;!!CQl3mcHX2A!AABv45iWm2k6HTI8Wy264dMo-3M0jTind_0pTuvgOhFazAwVGHqBntMvpPqr0LNJDXra7SjvcfmV4egGmikEiClUf8zH1w$ <https://urldefense.com/v3/__https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html__;!!CQl3mcHX2A!AABv45iWm2k6HTI8Wy264dMo-3M0jTind_0pTuvgOhFazAwVGHqBntMvpPqr0LNJDXra7SjvcfmV4egGmikEiClUf8zH1w$>
> Dave Täht CSO, LibreQos
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net <mailto:Bloat@lists.bufferbloat.net>
> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!AABv45iWm2k6HTI8Wy264dMo-3M0jTind_0pTuvgOhFazAwVGHqBntMvpPqr0LNJDXra7SjvcfmV4egGmikEiCnSExcBIA$ <https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!AABv45iWm2k6HTI8Wy264dMo-3M0jTind_0pTuvgOhFazAwVGHqBntMvpPqr0LNJDXra7SjvcfmV4egGmikEiCnSExcBIA$>
>
>
>
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
prev parent reply other threads:[~2023-10-11 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 18:43 [NNagain] " Dave Taht
2023-10-11 13:52 ` [NNagain] [Bloat] " Livingood, Jason
2023-10-11 14:59 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6HaC7bcx_BPikd39LxLCKP5y8Vszi15SYeTVXivTjM-Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=jason_livingood@comcast.com \
--cc=nnagain@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox