Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Thursday, 10-Nov-2022 04:32:28 JST Alex Gleason

   • feld
   @meowski @feld Cloudflare Workers are built on the Service Worker API which is an open web standard, and can be self-hosted on the open source workers runtime, workerd: https://github.com/cloudflare/workerd
   
   This allows you to choose between convenience and freedom which is a win-win.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Thursday, 10-Nov-2022 04:39:28 JST Alex Gleason

     in reply to

     • feld
     • void

     @void @feld @meowski You’re missing the point of this. It takes the beautiful simplicity of Pleroma’s media proxy and makes it available to any application.

   • Embed this notice
     void (void@bikeshed.party)'s status on Thursday, 10-Nov-2022 04:39:34 JST void

     in reply to

     • feld

     no, pleroma media’s proxy pipeline should get improved and no-one should rely on this workers shit.

   • Embed this notice
     void (void@bikeshed.party)'s status on Thursday, 10-Nov-2022 04:58:53 JST void

     in reply to

     • feld
     @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.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Thursday, 10-Nov-2022 04:58:53 JST Alex Gleason

     in reply to

     • feld
     • void
     @void @feld @meowski Thanks for explaining the back story. I was inspired by your work, and you should take it as a compliment and not an insult, even if it's not exactly how you imagined. It does have a purpose. You're mean, but you're a genius.
   • Embed this notice
     void (void@bikeshed.party)'s status on Thursday, 10-Nov-2022 05:01:32 JST void

     in reply to

     • feld
     @alex @feld Oh and if you want to "make it available to any application",
     
     https://imgproxy.net
     https://thumbor.readthedocs.io/en/latest/
     
     etc- and a shit ton exists specifically for cloudflare workers.
     
     The pleroma stuff was to be entirely embedded in the app.
     Alex Gleason likes this.
   • Embed this notice
     void (void@bikeshed.party)'s status on Thursday, 10-Nov-2022 05:18:14 JST void

     in reply to

     • feld
     @alex @feld @meowski by all means-- replace all this with a dumb nginx & cloudflare worker if you ever run this on trump's social network, <3
     Alex Gleason likes this.