dan @danabra.mov@bsky.brid.gy
Public

i just don't understand how to use this thing i'm not running Tap continuously. i'm developing locally. obviously it's not running when i'm not developing. obviously i don't need it to "catch up" on "91 million events" when it only monitors a single account. i'm fine having it resync it if needed

There's your problem. Tap is ~56 hours behind the firehose head. It's processing events from ~2 days ago. Your edits are at the head of the firehose, so tap won't see them for a very long time at its current processing rate of ~455 events/sec. The firehose has ~91 million events queued up ahead of tap's cursor. At this rate it would take over 2 days to catch up (and it never will since new events keep coming). Options: 1. Delete tap.db and restart — fresh start, tap will enumerate repos via the signal collection and resync from scratch, then start consuming the firehose from the current head 2. Manually advance the cursor — jump tap's cursor close to the head, then let the resyncer handle the repos that are out of date Want me to do option 1 (nuke and restart)?
0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://bsky.brid.gy/convert/ap/at://did:plc:fpruhuo22xkm5o7ttr2ktxdo/app.bsky.feed.post/3mgiyna6j5s2s on your instance and quote it. (Note that quoting is not supported in Mastodon.)