thats cool but i had issues with both a plc (@whey.party) and web (@dw.whey.party) acc so im not entirely sure my issues was entirely did:web related

um well its just a single aelf contained index.html file that i asked gemini to quickly make, but if its useful then i can put it on tangled

hmm my own relay which runs the new 'relay' codebase (non archival sync1.1 relay) is also failing to serve those two accounts

hashtag awesome

for me at least i usually share music with a yt link just because its the most accessible format. a spotify / some other platform specific link requires either installing the app or a subscription to hear the full thing

also do yall have any other independent jetstream instances that i can add to this tool? preferably the jetstream should be ingesting from an independent relay

what the hell is going on

I should add that it happened after a migration

Thanks for the offer, i think ill try to fix this first though. Also i think its not just the bsky appview, i recently found out that all relays that ive checked on eventually stopped relaying both accs, so i dont think its an appview problem

All that just to avoid refollowing everyone

i might try to go into this a bit deeper later today. maybe ill set up a relay thatll only listen to my own PDS and wait for the exact moment it gives up on those two accs and check the logs

when i migrated:
1. jetstream.fire.hose.cam never saw the new accs on the new pds
2. jetstream1.us-east.bsky.network saw and relayed info from the new accs for a while then stopped relaying
3. jetstream.whey.party was made after i moved the accs, then stopped relaying