microcosm.blue
in the PDS section of the view on a PDS or account it would be useful to show the current seq number each relay has for the PDS and/or if its behind, matches or ahead of the latest seq number from the PDS itself (probably easiest to get that with a subscribeRepos?cursor=0
Diagnostics for atproto PDS hosts, DIDs, and handles: https://debug.hose.cam
feature request: show seq numbers / seq mismatches #1
open
opened by
nel.pet
nel.pet
nel.pet
(author)
PDS is definitely a bit of a tricky case yea. I was thinking cursor=0 would be fine but i didnt think about how that's going to be insane amounts of messages for bigger PDSs.
hmm lowest seq from relays -1 is going to work for ref impl PDS but i doubt it'll play that well with cocoons timestamp seq numbers ... (or any other non-linear seq format alternative PDS implementations might choose to use).
yep this makes sense! easy to get from the relay, but PDS seems tricky. cursor=0 will replay whatever window is available right? which can be a lot on mushrooms.
maybe we could get any known seq from a relay and then try to subscribeRepos on the PDS with that-minus-1.
would be nice if PDSes implemented
com.atproto.sync.getHostStatusthough