Conversation

Notices

1. Embed this notice
   nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 08-Apr-2025 06:09:10 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
   I don't know how people use Verita's half baked block bot shell script rather than HighRollerPolicy. High Roller is just better.
   • ✙ dcc :pedomustdie: :phear_slackware: and Phantasm like this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Tuesday, 08-Apr-2025 06:11:38 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to
     @nyanide Yea lol
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 08-Apr-2025 06:14:38 JST Phantasm

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @dcc @nyanide
     >my blockbot cannot be spammed easily
     >gives an example of how to quickly and easily spam it
     >*crickets*
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 08-Apr-2025 06:17:11 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @phnt @dcc Cooldown spam prevention method when Cachex appears in an MRF:
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 08-Apr-2025 06:19:58 JST Phantasm

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @nyanide @dcc It has one flaw (I think) when I last looked at it. The global per actor ratelimit has no lifetime specified, so an actor that hits the ratelimit during the lifetime of the Pleroma process (weeks/months) will stop generating notifs. Depending on how large your instance is, you might hit that unintentionally.
     
     Or at least I think that's what will happen, because I've never actually tried testing that hypothesis.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 08-Apr-2025 06:21:11 JST Phantasm

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @nyanide @dcc So in a way, it's way to ratelimit-y than probably intended.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 08-Apr-2025 06:22:14 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @phnt @dcc I assume that's easily fixable, right? Otherwise an occasional restart which happens anyway for lab sometimes works around this minor oversight
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 08-Apr-2025 06:30:03 JST Phantasm

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @nyanide @dcc You can probably put an expire() on the object after the incr() function and it will fix it, but then the question is: Does it remove that expire when you incr() the same object again. It requires some quick testing.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Tuesday, 08-Apr-2025 06:35:39 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @phnt @dcc @nyanide It's per actor so it won't get hit unless someone's autistically blocking every user on the instance. Could be solved by adding `expire` to it, but at that point it's worth adding global per-domain ratelimits as well as fully global ones. Also I should get rid of tag_[N]ing_author since one could just add put an @ before {actor}.
     ✙ dcc :pedomustdie: :phear_slackware:, Phantasm and nyanide :nyancat_rainbow::nyancat_body::nyancat_face: like this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Tuesday, 08-Apr-2025 06:48:51 JST Phantasm

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     @mint @dcc @nyanide You'll loose the ability to change behavior based on the action (I have (un)blocks set to tag the actor and rest does not tag). But I don't think many fedi admins use that option anyway. A global one should be more than enough, if you want to still keep it configurable from AdminFE.
      likes this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Tuesday, 08-Apr-2025 06:50:53 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • Phantasm
     @phnt @nyanide ERM NO ITS CAN'T VE SPAMED
     Phantasm likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Tuesday, 08-Apr-2025 06:57:13 JST 

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @phnt @dcc @nyanide Tested it in iex, appears that Cachex.incr kilts the expire.
     Phantasm likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Tuesday, 08-Apr-2025 07:03:03 JST 

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @phnt @dcc @nyanide Actually no it doesn't, I just forgot to run Cachex.purge.
   • Embed this notice
      (mint@ryona.agency)'s status on Tuesday, 08-Apr-2025 07:18:11 JST 

     in reply to

     • 
     • ✙ dcc :pedomustdie: :phear_slackware:
     • Phantasm
     @dcc @nyanide @phnt A-and the purge does nothing. Anyway, will deal with this later, for now I got rid of tag_[N]ing_author (just put the @ in the message options) and instead made report message more configurable.
     https://gitgud.io/ryonagency/pleroma/-/commit/3863bf1af0eee539bd2b4ee6238e7a1336066a17