Conversation

Notices

1.  (mint@ryona.agency)'s status on Friday, 16-Feb-2024 21:37:42 JST 

   • 💀💀💀 :0080: c̷̨̢̛̲̼̞̞͓̹͚̗̼͓͚͖͒̔̓̃̈̋̂́̏̆̐̐̈́̉͘͜ȑ̴̫͔͂̌̔̆̓͛͗́͐̍̃́̆ÿ̷̤̺̳̖͖͚͈́̄́͌͒͂͊͗̄̔̚p̶̢̧͇̞̯͍͇̤̖͖̙̫̪͋̏̃̃͗̎͜͝t̶͖̉̽̐̇i̴̭̜̼͖̬̽̀͆̃̓̂̚͝ͅc̸̡͙̪͎̫͚̫̘̱͚͔̫̣̣̒̃̋͜͝ 💀💀💀 :verified:
   • kaia
   • :blabcatverified:
   • jeru
   @newt @Jain @kaia @jeru >Isn't there just a separate program for proxying media
   I don't think so, unless you're going to gut Pleroma of everything but its mediaproxy capabilities. Though at this point it might be easier to write a separate script that handles media proxying. That said, Pleroma itself consumes very little system resources when it's not doing any DB writes, and with the only accessible endpoint being mediaproxy, it wouldn't. I use that hack myself so that mediaproxy requests won't circle back and forth between the homeserver and the proxy on my VPS.
   >I reckon, just a clever nginx setup could do this without Pleroma involved.
   Mediaproxy URLs are encrypted with said secret key, supposedly so that it can't be abused as a general purpose proxy. Plus I don't think it's that easy to wrangle nginx into forwarding traffic to arbitrary hosts.
   • :blabcatverified: (jain@blob.cat)'s status on Friday, 16-Feb-2024 21:47:28 JST :blabcatverified:

     in reply to

     • 💀💀💀 :0080: c̷̨̢̛̲̼̞̞͓̹͚̗̼͓͚͖͒̔̓̃̈̋̂́̏̆̐̐̈́̉͘͜ȑ̴̫͔͂̌̔̆̓͛͗́͐̍̃́̆ÿ̷̤̺̳̖͖͚͈́̄́͌͒͂͊͗̄̔̚p̶̢̧͇̞̯͍͇̤̖͖̙̫̪͋̏̃̃͗̎͜͝t̶͖̉̽̐̇i̴̭̜̼͖̬̽̀͆̃̓̂̚͝ͅc̸̡͙̪͎̫͚̫̘̱͚͔̫̣̣̒̃̋͜͝ 💀💀💀 :verified:
     • kaia
     • jeru
     @mint @kaia @jeru @newt
     Theoretically one can change the base url to include the origin domain as url parameter, then write a nginx rule to forward the request to that url parameter. It would be possible to forward a request to any arbitary domain but caching fixes the abuse so for any url called, the origin server would only be called once
      likes this.