I think most people would put their steam box to sleep when not playing.

What I think would be cool is if you could host a PDS on your router. That shit's always on.

Will that really work though?

Most people don't have static IP addresses, nor the ability to easily set up DNS to point to their home.

Also, a gaming rig is likely to be a pretty big power hog, much more so that a Raspberry Pi or similar.

I just can't handle that it's also when I'm getting ready for Christmas and have my family to hang out with.

But seriously, the ABC and @australia.theguardian.com have pictures of Trump being a massive tool as their headline stories; while really important laws and events are barely covered.

Isn't it amazing how electing a government of well meaning people with experience results in positive policy changes.

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.