• 855 Posts
  • 2.17K Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle



  • gedaliyah@lemmy.worldOPMtoLemmy Apps@lemmy.worldA note about Tesseract
    link
    fedilink
    arrow-up
    2
    arrow-down
    10
    ·
    22 hours ago

    Some clarifications:

    1. Several people called the dev a Nazi, etc. Those comments were removed. I never said someone called me that. One of those users posted in this thread defending their original comments calling the dev a Nazi, and additionally attacked me. Yes, that’s against the rules.

    2. Nope. That comment was mistaken. The repo was not moved. A user had been blocked from the repo, then mistakenly linked to a fork from 2023 that was not associated with the dev.

    The claim of the thread was misinformed. It was adding gasoline to a flamewar by falsely claiming that the dev took down the repo. This community is not for witch hunts or shovelling more falsehoods into the rumor mill. The fact that so many people are repeating the false claim even after the removal shows that the post was causing real harm. In other words, the removal seems to have been the correct decision.

    The dev posted their reasoning here. The comment in that thread was the same information copied and pasted.


  • gedaliyah@lemmy.worldOPMtoLemmy Apps@lemmy.worldA note about Tesseract
    link
    fedilink
    arrow-up
    3
    arrow-down
    11
    ·
    1 day ago

    I’m sorry, but you are just plain wrong.

    The comments calling the dev a Nazi are in the modlog. The post falsely saying that the repo was deleted was misinformed. The repo is still here. Where it has always been. Please correct me if I am wrong and I’ll restore the post. Just share the original link and the “moved” location.

    I’m not covering for anyone. I’ve posted elsewhere exactly why what they did was wrong, and I didn’t have to resort to invoking the Holocaust.



  • gedaliyah@lemmy.worldOPMtoLemmy Apps@lemmy.worldA note about Tesseract
    link
    fedilink
    arrow-up
    3
    arrow-down
    16
    ·
    1 day ago

    In order to believe that one must posit:

    1. Calling someone a “reddit mod” is a compliment
    2. Saying a repo is deleted when it is clearly there is not misinformation
    3. Nazis are not murderers

    And an inability to read the actual mod log in which the offending comments are (as you suggest) individually removed. Then the post which is based on the misinformation was removed separately.

    FYI, I’m not the dev. I’m not defending their actions. You are seriously misplacing your anger.


  • gedaliyah@lemmy.worldOPMtoLemmy Apps@lemmy.worldA note about Tesseract
    link
    fedilink
    arrow-up
    2
    arrow-down
    13
    ·
    1 day ago

    I find it more odd that people can’t talk about a piece of software without calling the person who made it a literal murderer.

    Please take a look at the mod log and let me know if there’s any removed post that does not contain a personal attack.

    The rules of this community were established long before I was asked to step in as a moderator. I’ve repeatedly and emphatically asked for additional moderators. I’m enforcing the rules of the community according to the standards that the community had already established before I got here. If those need to change, then so be it.

    But this ain’t it.



  • In my experience anonymous people online don’t hide their bigotry behind an eloborate 10-point system. In this case, yes. I believe the motivation is exactly as it’s presented.

    The fact that the dev clearly thinks it is a fair justification shows exactly the mindset. The problem is bad enough on its own without making up additional poorly founded accusations.



  • You’re right, I should specify (although the condescension is not helping your case). They are views deemed problematic by the Tesseract dev.

    I’ve had run-ins with other devs or instance admins who find my views problematic, and banned me from their community/instance/whatever. That’s unfortunate, but it’s transparent. People know who the petty tyrants are and act accordingly.

    This is something different.

    Having a frontend preemptively blocking users and instances based on the sole judgment of the dev is unprecedented AFAIK. We don’t need to invent intimations of bigotry to see why this is wholly bad for the platform. It goes against basic principles of transparency, openness, and free choice that the Fediverse is based on.

    I believe that a front-end (client) should be a tool to access the service/network. It shouldn’t be making content decisions. If someone wants to make a block list and publish it for others to use, that’s great. If someone wants to trust an admin for content curation/blocking, well… that’s how this whole thing works. People choose or change instances based largely on that trust. But to have a tool for accessing the network also modifying the content? That’s bad, and a bad precedent.


  • See, THIS is the issue I wish people would focus on. The dev of a pretty important frontend has set up a block list. They have made it the default. They have not applied a clear and equitable criteria, set up a community feedback channel, or any sort of crowdsourced input.

    The modlog is open, meaning that anyone can see exactly what moderators and admins (generally) are up to. People can (and do) push back when things decisions are punitive, arbitrary, or unclear.

    This is not that. You have no way to see why your username was included, or correct it if it was in error. There is no community feedback to direct what standard makes sense.

    That’s the problem. It’s draconian. By manufacturing some shrill accusations of bigotry, yeah, it makes a lot more flashy posts, but doesn’t help in addressing the issue. If we can’t accurately name problems, we can’t solve them. We are just a mob on a witch-hunt.



  • That’s a big distortion. They are accounts that advocate violence or other problematic political views. Many of them are also LGBT, but that’s not why they are on the block list.

    I do think it’s problematic for a client/frontend to default-block any group of individuals or instances at all, but portrayimg it as motivated by bigotry when it’s not is pretty messed up too.