From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
"Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] OT: National test of the emergency broadcast system
Date: Wed, 4 Oct 2023 11:43:05 -0700 [thread overview]
Message-ID: <CAA93jw4Th+W5jv5dCMuUMK3pTBv53GR37=Ue8VW12gdrTXUa2w@mail.gmail.com> (raw)
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://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
next reply other threads:[~2023-10-04 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 18:43 Dave Taht [this message]
2023-10-11 13:52 ` [NNagain] [Bloat] " Livingood, Jason
2023-10-11 14:59 ` Dave Taht
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='CAA93jw4Th+W5jv5dCMuUMK3pTBv53GR37=Ue8VW12gdrTXUa2w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--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