lost whey

@lost.whey.party

taking intermittent refuge at bar samsara all relays randomly refuse to serve new content from @whey.party and @dw.whey.party (even though im on the same pds as both of them??) so i was here for a while

maybe the fact that this acc is now properly indexed by the microcosm relays is a hint? idk 5 hrs ago this acc was working fine but it never hit the microcosm relays. but now, now that the 2 broken accs are working, this (already working) acc is now returned by the microcosm jetstreams

5 hrs ago this acc was working fine but it never hit the microcosm relays. but now, now that the 2 broken accs are working, this (already working) acc is now returned by the microcosm jetstreams

Could probably make a generic service thatll proxy feeds for you across apps. Let users log in with both the source and target accs, pick the feed from the source acc to forward, and then get a private feed on your target acc that mirrors what the source acc would see in that feed

lost whey@lost.whey.party · 10mo ago

I think ill make a custom feed just for me thatll make the following feed from @whey.party and @dw.whey.party visible to me on this acc. I already got Fresh feeds so it shouldnt be that hard to make two new variants

I actually can still use my main accs just fine, i can still scroll feeds which means auth service proxy still works, so its just the firehose thats broken. But yesterday, the issue was pds wide, which makes sense. Yet this time its those two accs

If only theres some sort of PDS interop tests, a tool thatll validate a PDS and its accounts and show exactly whats wrong. Id like to know when its my fault vs when its bsky's fault specifically where my account works on my own relay but not theirs