PROPOSAL NAME: Emergency Alerts over LAN/WLAN #189
Comments
|
I am all for the web being more capable but this seems like too specific of a use case to warrant a whole web api. |
|
Also would this require a tab constantly open? |
|
What if end-users could subscribe to securely receive alerts from one another (e.g., via ActivityPub/Fediverse) and there was some way for devices (e.g., smartphones, smart TVs) to initialize and configure themselves to automatically subscribe to some accounts per localization? It might, then, be opt-in, ordinarily, but opt-out for a locale-based set of accounts, e.g., emergency-alerts-related accounts. Then, there would need to a protocol to obtain this list of alerts-related accounts given a location. |
|
This just seems too specific for a web standard. I think it could work well as a an app to download but not for the web. |
|
This isn’t a web standard, but more of a protocol of sorts that either is
like Wake on LAN, or a JSON standard like AP.
…On Wednesday, December 4, 2024, Gabe ***@***.***> wrote:
This just seems too specific for a web standard. I think it could work
well as a an app to download but not for the web.
—
Reply to this email directly, view it on GitHub
<#189 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKNKRXGJHDIATQBPJQOVCD32D5KXLAVCNFSM6AAAAABSUG2ZUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGM4TSOBQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Then why make a wicg propsal? |
|
@upintheairsheep , you might want to consider proposing a new Community Group around these ideas and goals. I was exploring Wikipedia, learning more about these topics, and, in my opinion, there could be opportunities to: (1) develop an extensible schema or ontology for emergency messages and non-emergency notifications (e.g., to be relayed per decentralized social media from special, official accounts), and (2) perhaps to expand on existing taxonomies of both of these kinds of messages. From the Specific Area Message Encoding article, here is a table listing event codes in use:
and some future or planned event codes:
Notice, for instance, that the entire category of cyber doesn't occur in those tables. Also, beyond saving lives with emergency messages, there are providing other types of real-time important or helpful notifications to people, e.g., for people to adapt their plans and logistics, perhaps to convenience them in their daily lives. A notification might, for example, indicate that a road is temporarily closed so that people might reroute with respect to their driving plans. At the very least, these emergency and otherwise important messages from special, official decentralized social-media accounts could result in a different audible chime on people's smartphones. Any thoughts on these ideas? |
Introduction
Hello, I would like to suggest a protocol to enable non-cellular internet connected devices to receive emergency alerts, see https://en.wikipedia.org/wiki/Wireless_Emergency_Alerts
Today, only cellular devices like smartphones are required to have EAS, and radios and cable TV have as well. Unfortunately, if you do not have a phone nearby, you will not hear the message and potentially risk your life. This is especially important for places like California that receive Earthquakes, which are extremely urgent, seconds matter. There should be a protocol to enable wireless devices such as smart TVs and WiFi-only tablets to receive EAS messages and display them, preferably please make it use as less resources for the deamon as possible, so it does not impact the performance of low-end or antiquated devices, and can fit on small IoT devices, possibly a specific packet can send a request to the device, but it may open up a security hole. AMBER alerts will be exclusive to internet-connected vehicles, and the insides of certain large buildings like malls and airports (with a tone less urgent than a life-threatening emergency) to prevent desensitization/alert fatigue and to prevent a dislike towards a world with emergency alert points everywhere.
Use Cases (Recommended)
Every device from smart TVs (present to 10+ years old if possible), game consoles (all game consoles capable of multitasking). Future goals include having intercom companies, security system companies, and Voice-EVAC fire alarm companies adding EAS notification by default on all devices in the commercial space, so for example a school with all phones put away using exclusively iPadOS devices, ChromeOS devices, Windows devices in computer science classes, and intercom and fire alarm system all through the school will have emergency messages brodcasted through all fronts. Same goes with an office complex with mixed Windows, macOS, and Linux usage and intercom system. IoT companies will also be able to use any security camera, smart doorbell, smart speaker, smart fridge, and more to act as sirens in cities without sirens. Additionally, smart heating systems, industrial systems smart thermostats, and more can take special precautions like shutting themselves off. Earthquake support is a priority due to their nature.
Goals (Optional)
Be implemented in as many devices as possible, save lives
Non-goals (Optional)
N/A, obvious, it won't be able to access your location and send it to the authorities nor allow you to time travel.
Proposed Solution
Without being too prescriptive, articulate a specific way (procedurally, algorithmically, declaratively) that a new or current web technology solves an existing problem or challenge.
Examples (Recommended)
Share one or more examples of how your proposal would be used by developers.
Alternate Approaches (Optional)
Could this challenge be addressed another way? Including other options you considered can help others understand the limitations or adverse side effects of other approaches.
Privacy & Security Considerations
Security risks depends on the technical implementation, but privacy concerns will be none (it does not take data, only give data).
Let’s Discuss (Optional)
This is a great place to list out questions you'd like others to weigh in on or areas you need feedback on.
The text was updated successfully, but these errors were encountered: