is anybody using one of the jetstream schedulers to consume and getting "websocket: close 1006 (abnormal closure): unexpected EOF" right as it gets ready to switch from playback to live tail?
for atproto to achieve its potential, there have to be projects that absolutely blow up on the launchpad
if nothing ever fails that probably means the swings aren't big enough
huzzah, I figured it out
my router has some "Advanced Security" feature I didn't know about that was redirecting my HTTPS requests to "safebrowse.io" as a warning, likely because my PDS is on the .xyz TLD
once I turned that off, requests started going through again
thanks everybody who helped!
RE:
good news: doing a "DNS cutover" onto a new PDS was easier than anticipated
bad news: the dumb SSL errors that I thought this "DNS cutover" would fix are still happening :(
something somewhere has to be broken on this machine...
decided I just didn't want to deal with the juggling necessary to make this a smooth transition, so I'm going to buy a new domain and point it at the new server and migrate each account one by one
less to do with the relay, and more with the autoposters I have on there
RE:
anybody ever move their PDS to a new server/IP but keep the same domain?
wondering if [bsky.network](https://bsky.network ) will struggle picking up the change
shouldn't though, right?
do account flags need to be declared in Ozone first before you can use `c.AddAccountFlag` in an automod rule?
I'm seeing the account in Reports, but I'm not seeing any flags applied to it
