Admin on the slrpnk.net Lemmy instance.

He/Him or what ever you feel like.

XMPP: [email protected]

Lemmy alt: @[email protected]

Avatar is an image of a baby octopus.

  • 60 Posts
  • 439 Comments
Joined 4 years ago
cake
Cake day: September 19th, 2022

help-circle



  • But that has nothing to do with the size of an instance of community. Rather the opposite is the case: an instance admin might decide to silence an community or instance because it is too big/busy and drowns out all the posts from smaller instances.

    Or a very practical example: those Reddit and RSS repost instances. We had to defederate them because they were drowning out all organic posts and discussions. I would have rather liked to silence them though as people might want to stay subscribed to them without bothering other people on the same instance by having them pollute the federated feed.

    On Mastodon it is also commonly used to temporarily silence an instance that is being abused for spam. This is much better than to defederate, as it still allows people to continue communicating with legitimate users on that instance.





  • I was referring to a different but similar case where someone intentionally spread mis-information about supposedly hardcoded things that turned out to be a complete nothingburger as all of it was behind an admin toggle. The same seems to be now true for this old issue you specifically pointed out here.

    It is true that there is some experimental stuff in Piefed, which is part of the relatively rapid iteration of features, but looking at the code and also the explanations given by the Piefed development team I can really not see any malice in those settings. It is perfectly normal that things get overlooked or implemented partially and when someone reports a bug (like a missing admin configuration setting) it usually gets fixed quite quickly, and at least in my experience without much discussions.



  • A while back, someone realized that piefed was hard coded to give negative reputation to certain people, regardless of what settings the admins had made.

    Please don’t spread old mis-info or at least back this up with actual links to the source-code (and if we are talking about the same thing, this was clearly debunked).

    As for the OP post, this is factually correct and I have seen the evidence. Although maybe Rimu should have been more clear in pointing out that this seems to be not an official instance tool, but rather something some moderators have cobbled together themselves.




  • Old DDR3 ECC is actually cheaper than regular DDR3 RAM, and it generally works with AMD CPUs (who unlike Intel don’t artificially restrict ECC support to their enterprise offerings).

    But tbh, ECC is generally not needed and I wouldn’t bother designing a system around it. Use a file system with checksums and regularly scrub the drives and you should not have any major issues with random bit flips that ECC protects against.





  • No, typically you use the DNS server of the domain provider.

    Hosting your own DNS server is possible, but if you don’t have a static IP address the other DNS servers will have no idea which server to ask when your IP changes, so in this specific scenario it wouldn’t work. And in general it isn’t really worth it as you get a DNS server with your domain included.