Figured I'd name each bot by the local airport (e.g. @atl.nws-bot.us) but need to map from the NWS location name to the airport code. I wouldn't mind a little help filling in the list. Also, BSky API seems unstable (lots of inexplicable rate limited errors). docs.google.com/spreadsheets...
Alrighty... First account is live, and seems to be populating properly. bsky.app/profile/was.... Creating the accounts takes a bit of time, but I think it is coming together. Any feedback on post content/format?
unsure if Wilmington, Ohio is Lunken (LUK), Cincinnati/Northern Kentucky (CVG) or Dayton (DAY)
I manage a few bots and have experience with the rate limits. Most importantly (and unadvertised (?)) is you can only create 100 new connections in a 24-hour period. Best practice is create the connection and keep it alive. They stay alive for several days (I think a week?)
Did you ever figure out the rate-limiting issue, or did you want to be connected with other Bluesky devs to see what’s up? I think there’s a Discord, FWIW
Boston is BOS. New York City is KNYC for Central Park, LGA=La Guardia, EWR=Newark
NWS Houston/Galveston could be HOU.
don't the NWS sites already have their own three letter codes? eg Peachtree GA (Atlanta) is FFC: www.weather.gov/ffc/www.weather.gov/dtx/www.weather.gov/apx/www.weather.gov/srh/nwsoffices
I've got all of them, would you like them via DM or a different way? (It doesn't look like I can edit that GDoc from where I am)
Thank you for doing this work. 📌
If you have the time, would it be possible to add Fort Worth/Dallas, please?