Embed Notice
HTML Code
Corresponding Notice
- Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Saturday, 28-Feb-2026 04:02:20 JST
pistolero@vii Think I showed you some of the code when you were out, but I did bash out a shitty JS client that can decode blocks. (CORS prevents it from doing load-balancing so I'll fix that at some point but the proofed concept, I'll do the CORS shit later. It is slow as balls (even when you have all the responses cached, so it's not a network problem; there are some peculiarities of the network setup due to disk space and this introduces latency but the code itself is slow) because I'm not any good at JavaScript. Code is also not obfuscated, but enough of it is "lightly modified copypasta" that it's also not exactly *legible*. But there's a PoC.) You can watch it reassemble the media: https://media.freespeechextremist.com/fucko.html?id=8ef98ad13a369b6592f50989db45ee60c6fd264c691354c8b09dda08a3bf91b2 . (cc @i , this was partially due to you suggesting some more blog post, I figured I'd document that in a place that wasn't "random extemporaneous notes on fedi".) 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. But, hey, it can also reassemble itself: https://media.freespeechextremist.com/rvl/full/c2067b9198017e469888213b35ee1a3336adc27594add8f434b05039a262dbd0?id=c2067b9198017e469888213b35ee1a3336adc27594add8f434b05039a262dbd0 . I fucking hate JavaScript.
> I’m also curious where it is because you’re always excited by it
I'm setting down a concrete pad today but I think I'm at "final set of changes to the P2P code that will make media.fse stop being slow" and then it's a matter of fleshing out the AP endpoints (the easy stuff) and the client endpoints and some of the weird stuff designed to cope with structural AP stuff (e.g., domain agreements; 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). Instead of going nuts with queues, I have started going nuts with Bloom filters; we'll see if I've gotta back out of that but I think I have a workable system now.