Conversation

Notices

1. karolat (karolat@stereophonic.space)'s status on Saturday, 10-Jun-2023 00:05:49 JST karolat

   • pistolero :thispersondoesnotexist:
   • Mike Hellstrom
   @endlessmike @p shut the fuck up doomer :blobcatumm:
   • Machismo repeated this.
   • karolat (karolat@stereophonic.space)'s status on Saturday, 10-Jun-2023 00:05:56 JST karolat

     in reply to

     • pistolero :thispersondoesnotexist:
     • Mike Hellstrom
     @endlessmike @p i'm sorry i didn't mean it
     
     i've never had this issue with fse before though--it reminds me of spc back on gnu social. i feel like i often have trouble fetching threads properly from your instance though, not sure.
     Machismo repeated this.
   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Saturday, 10-Jun-2023 00:06:27 JST pistolero :thispersondoesnotexist:

     in reply to

     • Mike Hellstrom
     @karolat @endlessmike Server load is low (like, unusually low) at the moment, and (this part's unusual) I don't even see the rate limit getting hit. (We rate-limit federation endpoints more aggressively than local stuff, the idea being that if you've got to slow down traffic for something, it's better to slow S2S stuff down than interactive clients. If Pleroma cached objects better, I think we could probably avoid rate-limiting that stuff anyway, as what we actually get is a few hundred requests for the same object as soon as it gets posted, so if there's an extremely active thread, other servers in the thread will sometimes bump up against that limit.)
     
     This post arrived in the thread nine seconds after the timestamp, but that'd be FSE fetching posts from SS, not subject to rate-limiting on our end.