Ask me anything.

I also develop Tesseract UI for Lemmy/Sublinks

  • 1 Post
  • 6 Comments
Joined 1 year ago
cake
Cake day: March 17th, 2024

help-circle

  • That’s a good point. I’ll have to check the default values, but on my own instance, I have very conservative limits in place, and it hasn’t proven to be an issue (so far?).

    Unless it’s changed since I wrote the online docs for Tessreact, the modlog is part of the “Messages” rate limit bucket which is/was something of a catch-all for endpoints that didn’t fit elsewhere. Even in the default config, that bucket is the most permissive due to that.

    I’ve been daily-driving my dev version with this feature enabled for a few days, and it hasn’t been an issue so far (it only does a modlog lookup if a comment is removed, so not on every comment in the tree). It’s also per IP, so unless a lot of people are behind the same public IP, I don’t think it’s going to pose an issue. I’d have to double check, but I think the most comments it loads in a batch is close to 100, so unless every comment has been removed, that would be the worst-case number of modlog fetches.

    So it looks like I’ll definitely want to make this feature toggleable even if it does end up defaulting to ‘on’.





  • Pam from 'The Office' defiantly saying 'Yep!'

    Yep, sure do! But only on my own instance in accordance with our polices; communities I moderate elsewhere are modded according to those instances’ rules and TOS.

    If someone does nothing but give out downvotes (the upvotes-given to downvotes-given ratio threshold for the automated ban is quite generous), then they’re contributing nothing but negativity and shitting on things for everyone else. If everything here displeases them so much, they can and should go somewhere else.

    I stand by (and have reviewed) every automated “Mass downvoting” ban my automod has issued.