Conversation

Notices

1. jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:08:49 JST jaf
   okay let's see if it caches
   
   •  likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 01-Aug-2023 02:09:44 JST 

     in reply to

     • pwm
     @jeff Still seeing Pleroma headers and redirect to /notice/. @pwm got it working, ask him for a config. Cute bun btw.
   •  (mint@ryona.agency)'s status on Tuesday, 01-Aug-2023 02:11:36 JST 

     in reply to

     • pwm
     @jeff @pwm Don't, those are frontend-specific paths.
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:11:37 JST jaf

     in reply to

     • 
     • pwm
     @mint @pwm i'll cache notice too i guess
   • pwm (pwm@crlf.ninja)'s status on Tuesday, 01-Aug-2023 02:15:35 JST pwm

     in reply to

     • 
     • pwm
     @jeff @mint full section
     ```
     location /objects {
     proxy_cache objects_cache;
     proxy_cache_key "$host$request_uri";
     proxy_cache_valid 200;
     proxy_no_cache $cookie_sessionid;
     proxy_ignore_headers Cache-Control;
     proxy_set_header Accept application/activity+json;
     proxy_pass http://phoenix;
     add_header x-cache "$upstream_cache_status from nginx";
     }
     ```
     I think I may have some directives that are not exactly kosher but it does what I wanted
      likes this.
   • pwm (pwm@crlf.ninja)'s status on Tuesday, 01-Aug-2023 02:15:36 JST pwm

     in reply to

     • 
     @jeff @mint The key to making the redirect not happen is to reset the accept header to the one pleroma expects to be coming to it from other AP servers or applications
     > proxy_set_header Accept application/activity+json;
     pleroma will always give you json if you tell it this, whether in your nginx conf or set on the command line with e.g. curl
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 01-Aug-2023 02:17:24 JST 

     in reply to

     • pwm
     @jeff @pwm /notice/ only returns either redirect to /objects/ (if requesting activity+json) or the same HTML page with linked scripts as everything else on frontend. Caching it is pointless and might even break things in case of frontend update.
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:17:25 JST jaf

     in reply to

     • 
     • pwm
     @mint @pwm go on.... why?
   •  (mint@ryona.agency)'s status on Tuesday, 01-Aug-2023 02:20:17 JST 

     in reply to

     • pwm
     @jeff @pwm Seems to be working now.
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:20:18 JST jaf

     in reply to

     • 
     • pwm
     @pwm @mint okay i circumcised the config snippet so it's kosher
   •  (mint@ryona.agency)'s status on Tuesday, 01-Aug-2023 02:24:12 JST 

     in reply to

     • pwm
     @jeff @pwm It should. Saves the trips to database and wasting queue slots for Pleroma's internal webserver replies.
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:24:13 JST jaf

     in reply to

     • 
     • pwm
     @pwm @mint it's not like it'll do anything perf wise tbh
   • pwm (pwm@crlf.ninja)'s status on Tuesday, 01-Aug-2023 02:24:14 JST pwm

     in reply to

     • 
     @jeff @mint oy vey!
   •  (mint@ryona.agency)'s status on Tuesday, 01-Aug-2023 02:28:03 JST 

     in reply to

     • pwm
     @jeff @pwm Inbound (fetching activites by remote instances).
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:28:04 JST jaf

     in reply to

     • 
     • pwm
     @mint @pwm for outbound or inbound federation?
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:31:06 JST jaf

     in reply to

     • 
     • pwm
     @mint @pwm inbound federation queues have been draining fast af before all this tbh
      likes this.
   • pwm (pwm@crlf.ninja)'s status on Tuesday, 01-Aug-2023 02:36:02 JST pwm

     in reply to

     • 
     @jeff @mint in my case I am doing it to avoid trips across the vpn back to my home server, as my connection has been experiencing up to 20% packet loss lately. Could be placebo, since I didn't measure before and after but it seems to have made things snappy, and I definitely see smoother traffic especially when large accounts like or reply to a post.
      likes this.
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:59:41 JST jaf

     in reply to

     • 
     • pwm
     @pwm @mint no noticable perf impact
     
      likes this.
   • jaf (jeff@misinformation.wikileaks2.org)'s status on Tuesday, 01-Aug-2023 02:59:42 JST jaf

     in reply to

     • 
     • pwm
     @pwm @mint so like, this nginx ran the largest open bittorrent tracker which used tls in the god damned world.