I think originally, attacks on infrastructure (I’m speaking for attacks on french telcos at least) were mostly by some kind of nuts leftists anarchs/luddites, but I think in the recent years, since COVID, it’s mostly a far-right thing. But both nutjobs do that.
There was already some attacks (two or three in the past year, IIRC) in France that targeted big fiber paths. Definitely concerning.
And knowing how centralized some of theses parts are (coughs TH2 Paris Voltaire) it’s quite scary. A more serious bad actor could really fuck things up wide.
@lain@kaia@xue yet he’s barely at 50+% of the capital (afaik; maybe even actually less) so I kinda feel like his situation is really precarious re: being twitter’s boss.
There’s probably a shit ton of ways where the others can league and dethrone the prince, especially if $TSLA derails
CF released their worker runtime so anyway the problem you're raising doesn't exist. (Also, since my solution included nginx: there's also a lot of lua scripts doing this).
(just fucking complete the media proxy in pleroma and all this discussion is null) (but honestly, let truth social use js workers, lame tech for lame networks. i'm fine with that.)
@alex@feld@meowski You're missing the point of the origin and goal of that piece of Pleroma.
When I committed it, it was a small part of a larger piece (and only focused on reverse-proxy). The project from which I extracted that reverse proxy from was already doing media manipulation (in a shitty way). I let pleroma do their way on manipulation because I still didn't had myself a correct way (and other personal reasons) - and their way was as bad as the source, just different.
That's why we got the horrors like the fifo insanity and the Qt media rewrite (and don't even get me started on libmagic).
In parallel, the original extract advanced, libmagic efforts got results, etc - but this happened outside of pleroma.
But in any way: the reverse proxy wasnt intended to just be a stupid dumbfuck proxy, it was always intended as a fully fledged media manipulation proxy.
A js worker cloudflary isn't what it was meant to be.
And if you just want to do it that way: stop using that piece of code. Just do it with pure workers, or heck, even a 10 lines nginx config will do it.