Ask me anything.

I also develop Tesseract UI for Lemmy/Sublinks

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

help-circle

  • Giving a garbo source the benefit of the doubt on an article-by-article basis just muddies the waters and gives an air of undeserved legitimacy to other things they publish.

    Credibility and trust are built over time; throwing out a “look, THIS article is okay” every so often does not make them a credible source.

    If the facts are solid, then there should be at least one other reputable source reporting on them. If only a sensationalist rag is covering it, maybe ask why that is.

    I notice you aren’t disputing the facts here, just the source.

    This is the same argument I’ve seen used by people trying to legitimize Fox News and RT, BTW.






  • 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’.