But composable moderation or just block the tool.

Yeah, nah.

The Orange Princess of the Ballroom was calling on Republicans to end the filibuster to take away Health Care.

But the Senate's morons just couldn't let them own it... and did absolutely nothing for the country in meantime.

The filibuster will still be there but health care won't. Everyone loses.

By capitulating at this time, Democrats gave weight to the Republican talking point that the shutdown was their doing.

By capitulating they admitted that they don't actually care about their constituents health care.

Where could I purchase this?

P.S. I’m Australian.

Can you list repos periodically, then just hit the websockets of the 200 or so?

For this use case, if you don’t need very low latency, I would just call list by collection at a regular cadence.

You can then just grab the records from each PDS and make sure you’re in sync.

I would think you could use the hash in the merkle tree to make sure no records are missed.

After you catch up all the repositories, you start listening to the firehose again.

I believe com.atproto.sync.listReposByCollection is the missing part of the puzzle.

I don't think that cursor=0 is guaranteed to work anyway, as the relays can configure the window they retain.

It shouldn’t matter too much if there’s multiple instances running, right?

AT proto views can offer eventual consistency.

I’m thinking about a birding app.

I’ve had one a day about my electricity bill for years.

You're making these right? Not slop?

I noticed this when I tried to run an instance; I couldn’t see my repos (and saw a lot of database failures on foreign key constraints).

Backfilling is also crucial!

I should be able to start my own instance and have it be (eventually) consistent!

I believe that stream.place has a small embedded PDS which it uses for storing its lexicons.

Is this using the Bluesky code or is there a rust version in the works?

I’ve noticed tangled.org/@parakeet.at..., which looks promising very.