@p

> You can watch it reassemble the media:

Oh shit you can! Okay, okay this may be stupid but this is the first time I've seen revolver do what it says on the tin and I'm actually really impressed. I only know so much, but I can see what you mean about it being slow, and it using the backend to reassemble.

> And that's actually, like, if you turn it into a service worker or something, it could theoretically propagate blocks between other servers and act as a lightweight bridge peer but I don't think it's completely workable and it'll be better to use the actual code and use the /rvl/full endpoint.

Okay, only tangentially related but I have been wondering about a fedi server that acts more like postfix, and has separate cli tools and transport and side-effect management. You saying this got me thinking about it again.

> I'm setting down a concrete pad today but

:truehero:

> I don't know if you were around when I proposed the idea but "owner of domain agrees to relay your posts to AP servers and agrees to be your 'home' by serving your keys/outbox and accepting posts to your inbox from AP servers" was embarrassingly trivial when it came up

I wasn't but this is exactly the kind of shit I got into activitypub for in the first place. Like, we all kind of accept that this is how we use this field or that field or this inbox or outbox but like... Google's not gonna tell us we're in violation of a spec they don't care about. It's whether we're causing problems for the network and their graphs that seems to be what actually matters.

> Instead of going nuts with queues, I have started going nuts with Bloom filters

... Oh this is great and I need to do some more research before I speak on it but if you have more to share I am a captive audience.