Cross-posted from "FYI: StarTrek.website is no longer federating with Lemmy.dbzer0.com" by @Admin@startrek.website in !quarks@startrek.website

Crossposting here since y'all won't be able to see it now that they've defederated us.


If you're not familiar with how Lemmy/the Fediverse works, basically everything you read at StarTrek.website is hosted by us, even if the content originated elsewhere. That means we are responsible for everything here and we have to decide if we are comfortable boosting content from other instances.

If you're curious, the final straw here was learning that db0 explicitly allows hosting discussions about hurting people, which needless to say goes against our instance values and we simply don't have the manpower to moderate that volume of content incoming from their server to a degree that we feel meets our quality standards, which left defederating as the only viable option.

In keeping in line with past trends we're announcing this because is is a larger instance and don't want to leave any of the crew confused as to why something may be missing.


I don't consider this a massive loss tbh. We already have !Risa@lemmy.dbzer0.com and !tenforward@lemmy.world was already more active than their whole instance. And I'm sure @Stamets@lemmy.dbzer0.com can provide the noxious lore of their instance if you're interested. The only loss would be not having members such as @Kirk@startrek.website running around running interference for DDoSers like @ptz@dubvee.org. Also Admiral Patrick of the Tesseract fame, was also an admin on their instance iirc so this is a clear retaliation as far as I'm concerned, even though we didn't actually do anything to AP.

But also

db0 explicitly allows hosting discussions about hurting people

What the fuck does this even mean? Can someone ask for an example? Is this about Luigi? IDFK...

PS: Will this drama season never end? I want my free time back >_<

[–] 4 points 4 hours ago (1 child)

We were on a previous version, so that's why. I think that's actually what hypercharged this drama. If I had not fell back on my upgrade schedule for a while, I would have realized tesseract was doing blacklists early on, and the backlash was probably be orders of magnitude lower. But because he had time to build this up to this monster, when people discovered it, it was a huge deal.

  • source
  • parent
  • context
  • [–] 5 points 6 hours ago (1 child)

    Like I literally pointed out that they have a blacklist for instances. I didn't even break the news about the second secret blacklist with usernames! All I did after is post 3 memes. But apparently I'm the master manipulator egging the whole fediverse smh.

  • source
  • parent
  • context
  •  

    I discovered this after upgrading our instance yesterday, which also upgraded all frontends to their latest versions as well. After I did, our Tesseract frontend stopped working and I noticed immediately as it's been my primary for a while. Initially I thought it was an API version mismatch, but no, it was much worse.

    Someone pointed out that the developer of the frontend added an explicit hidden and unmodifiably blacklist which includes any and all instances to the left of Kissinger. There's a commit which also explains their specious reasoning about our instance specifically, as it seems we've been on their shit list for a bit longer than that.

    This instance and its admin staff encourages identity politics, groupthink, mob mentality, and extremist solutions to societal problems. Users who advocate violence are not moderated so long as the admins agree with the target. Caution and critical thinking are advised when interacting with this instance or its users.

    When you use tesseract to connect to one blacklisted such instance , you just get a message informing you that Tesseract is "incompatible with that instance" which leads one to think of a technical issue, like an API mismatch, rather than the dev being an opinionated coward.

    Isn't it funny how all the software developed by turbolibs, like Piefed and Tesseract, end up with hidden control mechanisms from developers who think they know better than everyone else? That they don't just think they deserve to tell you what you should think, but they should manipulate you to think it? Isn't it funny how libs go on about how bad it is to support lemmy due to the ideology of the devs behind it, and yet lemmy has 0 opinions as a software? It does make one think...

    Anyway, I forked - it as one does - and disabled the blacklist, but since this is a massively ideologically compromised software, I'll doubt I'll keep this frontend up after Lemmy 1.0. I think we'll bring up mlmym again now that someone's maintaining it again.

    submitted 6 days ago* (last edited 6 days ago) by [M] to c/div0@lemmy.dbzer0.com
     

    Cross-posted from "Lemmy Release v0.19.20 - Reduced Memory Usage" by @dessalines@lemmy.ml in !announcements@lemmy.ml


    I'm planning to upgrade to this version ASAP as we've been having some RAM issues in the DB recently which is causing the "daily hiccups". I can't promise this will fix it, but I can hope. Expect some short downtime in the near future.

    EDIT: Done

     

    As promised, here's my first Maleghast battle report.

    I made this using python, and kdenlive. Soon I will write another devlog on my workflow for anyone interested.

    It took me a lot of hours to figure kdenlive out and create the relevant scripts to generate the units. Obviously it's very amateurish compared to other editors, but I think it's ok for the first attempt. Do let me know of your suggestions for improvement.

    view more: next ›