Hi Folks. I've been silent for a bit. I had some hardware failures and some issues with not having any time. Well now I have some of the latter and I'm looking to alleviate some of the former. Watch this space -- I've learned a lot and I'm going to be back with a new way of doing things soon.

There have been some obvious persistent issues with the service including hardware issues and because of that the feed is going to be offline indefinitely while I procure more hardware and fix things. But this is not my job and my actual job is very busy and I have a baby. I’m gonna try my hardest.

It’s become clear that the current method of collecting data from users who want to use the feed is too fragile for a production level system and the engineer in me cannot cotton that any longer. Between persistent little bugs in the software to changes in firehose format, I can’t keep this up. 1/

@skeetstats.xyz !optin

I see the feeds have pooped the bed but I’m about to get on a plane I’ll look later

I guess I have to say this now: watchedsky will continue to run as long as I can get real data from NOAA for free. If it becomes paid as has been suggested through things like project 2025, I’m going to have a hard time paying for something I already paid for via my tax $ even if I can afford it.

While watchedsky uses free technology and will remain free for its users for its lifetime, it’s not free to run. If you find it useful, consider sponsoring me on GitHub. This isn’t my day job and offsetting the costs will help me innovate: github.com/sponsors/wat...

Kinda like this

I meant to announce -- if you get your WatchID from watchedsky.social/app/findme, you can just @ me (or reply to any message of mine, either way) that code, and my bot will record it for you and let you know that you can delete the skeet

We’re back baby! A couple of inputs changed from the bsky app side that caused feeds to go pear shaped. Hopefully next time we’ll catch it earlier. Anyone from the bsky dev team or at proto or whatever else I can do to tag to get attention here, how can I as a dev get notified of upcoming changes?

I'm going to have to take a crack at this again in a couple of hours, my latest debugging effort didn't do what I expected. Dad duty calls; be safe out there everyone.

Hey @pfrazee.com et al on the development side, why did the JWTs for feeds start using `ES256K` for signing some time in the last 24 hours? Was this announced somewhere that I can subscribed. It effed the @watchedsky.social feed until I can get that implemented. Not great during a hurricane.

Apparently when weather go brrrt, my stuff freaked out a bit. Trying to sort through it now. Sorry bout that!

I guess I should also say that for right now, this service is US-based. Mostly because I’m American and I know about the National Weather Service. If you’d like your country covered, tell me (but be prepared to answer questions I have!)

If, like me, you are Security Focused (paranoid), the Watch ID Iyou add your profile is not in any way associated with your user account, aside from being in your profile. It’s a randomly generated ID that correlates to the areas you’re interested in. If someone else wanted …

I am alive! After months of nighttime work after my baby has gone to bed, watchedsky.social is ready for use! There are still some bugs to be worked out so bear with me, but you can go to watchedsky.social/app/findme and get a code, then add it to your profile…

If you see this post in your Watchedsky feed, it means we couldn't read your profile or you didn't have a Watch ID in it. Get your Watch ID at watchedsky.social/app/findme

If you see this post in your Watchedsky feed, it means there was an error connecting to the Watchedsky database. Please let @jaygles.bsky.social know!

If you are seeing this message in the Watchedsky feed, it means there have been no severe weather alerts in your specified areas. That's probably good, right? Set up your areas at watchedsky.social/app/findme