I hope it is a way to solve this…

  • thesmokingman@programming.dev
    link
    fedilink
    arrow-up
    10
    arrow-down
    2
    ·
    11 months ago

    You’re getting into very sketchy territory by saying a dev who is using a public GitHub repo to solve their problems needs to take it down because of how others are abusing it. Should the original dev be punished by their email provider because they shouldn’t be allowed to use this? Should anything that has potential harm be required to be a private repo? Who gets to decide all of that?

    In the interest of specifics, can you point to where this specific list has done harm? I spent a fair amount of time looking around to make sure I wasn’t going out on a limb for someone with neutral views.

    • ono@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      4
      ·
      edit-2
      11 months ago

      You’re getting into very sketchy territory by saying a dev who is using a public GitHub repo to solve their problems needs to take it down

      No, I don’t believe I said any such thing. Since you mention it, though, I think taking this list down and removing the false positives before bringing it back up would be the responsible thing to do.

      In the interest of specifics, can you point to where this specific list has done harm?

      I know from personal experience and investigation (both as a user and on the admin side) that there are now many cases of privacy-focused email addresses being rejected, or even worse, accepted and then silently black-holed, due to the domains being inappropriately added to lists like this one. I don’t know of a place where people report such cases so they can be documented in aggregate, but if I find one, I’ll be sure to bookmark it in case your question comes up again in the future.

      • thesmokingman@programming.dev
        link
        fedilink
        arrow-up
        6
        arrow-down
        3
        ·
        11 months ago

        So you’re lumping this resource into a bucket with other resources that were malicious but you have no direct connection from this resource to harm you claim it causes? You’re saying a dev using this list to allow people to download free content but prune emails to save his bounce rate is doing bad things and needs to convert their FOSS use-case to yours?

        Who gets to decide? You didn’t answer that and in the interest of good faith I’ll pull that one down as the important one since it follows from the argument I feel you’re making.

        • ono@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          5
          ·
          edit-2
          11 months ago

          but you have no direct connection from this resource to harm you claim it causes?

          The connection is very clear, because you can see what domains are on the list.

          So you’re lumping this resource into a bucket with other resources that were malicious

          You’re saying a dev using this list […] needs to convert their FOSS use-case to yours?

          […] the argument I feel you’re making.

          Please stop putting words in my mouth. As you seem to be arguing in bad faith, I’m done with this conversation.

          • thesmokingman@programming.dev
            link
            fedilink
            arrow-up
            4
            arrow-down
            3
            ·
            11 months ago

            You’ve ignored my questions attempting to flesh out your point and refuse to link this specific list to anything bad. I don’t think you understand good or bad faith. Good luck with that!