Open stucka opened 1 month ago
@fishcharlie suggests it might be good to build a bridge to Mastodon from Bluesky, but it might be better to just post directly. Need to rethink password storage and the logistics get weirder. Charlie's bridge idea is at https://bsky.app/profile/charlie.fish/post/3l57xcrv3uw2g
Roadmap should be paused as this may be senselessly duplicative. See https://bsky.app/profile/wandrme.paxex.aero/post/3l5aygerk4o2p or https://nws-bot.us/
This program was started entirely to handle tornado warnings at a national level.
There's an opportunity here to make it more flexibile, largely through expanding the existing config schema. Each config entry should include a list of event types; geographic zones; offices; severities; and output types. A list entry of "Any" should add flexibility in the checks, e.g., national tornado warnings would have events of ["Tornado Warning"] and the rest as ["Any"]. Miami office stuff might have the office set properly and severities of severe or extreme.
If NWS will allow regular pulls of this data nation we can do more with them, e.g., start publishing per-weather-office outputs for severe weather.
This would require mapping zones to weather offices, and perhaps updating that weekly or so. It's not clear to me from the documentation whether nwsapy has that part of the API working as far as we need it, but that might be an easy pull request if not.
Output type could be a list of dictionaries, pointing to maybe either "All" or "New" ... which would allow Bluesky posts of only new stuff, but perhaps JSON or HTML output of all entries to power embeds or other data products.