Highlighting the recent report of users and admins being unable to delete images, and how Trust & Safety tooling is currently lacking.

  • Sean Tilley@lemmy.mlOPM
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    35
    ·
    8 months ago

    If you can take a moment to move your massive, fragile ego out of the way, you’ll realize it’s not a hit piece. It’s criticism of your behavior in reaction to what is frankly a reasonable set of requests.

    Journalism is not just about serving as a propagandic mouthpiece to lionize you and your work. Sometimes, I have to report on subjects that are frankly horrible, people acting shitty, and how people in spaces react to that.

    Effectively you are blowing the complaints of a single user completely out of proportion. It is true that we didnt respond ideally in the mentioned issue, but neither is it okay for a user to act so demanding towards open source developers who provide software for free.

    This issue is basic fucking table stakes for user safety and data compliance, and the fact that it still does not exist after four years of being a project is wild to me. It creates liabilities for admins. The fact that it’s still a problem, right now, illustrates that these things are not direct concerns in how you design software.

    I find it very questionable that you publish this sort of hit piece against Lemmy without even bothering to ask for a comment from our side.

    Your comments were in the GitHub issues.

    • nutomic@lemmy.ml
      link
      fedilink
      arrow-up
      26
      arrow-down
      7
      ·
      8 months ago

      massive fragile ego, frankly horrible, acting shitty

      So this is how you see me, all based on two issues out of thousands and never having talked with me directly. Honestly this comment would be a good reason to ban you for harassment and violating the site’s code of conduct. But lucky for you I don’t care what random strangers on the internet think about me.

      • Sean Tilley@lemmy.mlOPM
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        26
        ·
        8 months ago

        No, it’s how I see you based on pretty much any time I observe you making a public comment. Which is unfair of me, admittedly, I can’t possibly see everything you write. Most of the time, though, you come across as hostile, and read as though you’re dunking on other people and projects.

        Anyway, the article was updated somewhat to give proper credit for your recent developments and point to your fundraising efforts.

        Have a nice day.

    • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
      link
      fedilink
      arrow-up
      15
      arrow-down
      5
      ·
      8 months ago

      The fact that the issue exists after 4 years clearly shows that you are in fact blowing it out of proportion. Actual issues that affect large numbers of people running servers end up being addressed by people contributing to the project. Lemmy is an open source project that anybody can contribute to, and fix the issues that are affecting them. The fact that this hasn’t happened shows that this issue is not as high priority as you want to make it out to be.

      This doesn’t mean this isn’t a real issue that should be fixed at some point, but it’s simply not the show stopper you paint to be.

      So yeah, you are absolutely doing a hack job here.

    • eveninghere@beehaw.org
      link
      fedilink
      arrow-up
      11
      arrow-down
      3
      ·
      edit-2
      8 months ago

      I think it’s a dead lock. The replies show that they can’t even understand the concern.

      That’s a typical death to a project. For, there will never be a moment for the team to address the concern. Whatever you try, the team won’t move an inch.

      I don’t know what instance admins are thinking, but there’s no point complaining at this point.