The dubvee guy made something the way he wanted it and shared it with others. If someone doesn’t like the way he did it they can fork it or use another front end. Not everyone likes the same things and that’s okay.

  • WhiteOakBayou@lemmy.worldOPEnglish
    215·
    2 months ago

    I think alphabet is a weird example to use for your opt in vs opt out analogy but the point is taken. That doesn’t change the fact that the list was available in published, clear (not obfuscated) code. Does the maintainer of a project have a duty to warn about their political leanings or weird social peccadillos? Was there any point that a user or admin performing their due diligence via code review would be unable to see that information?

    • Oni_eyes@sh.itjust.worksEnglish
      22·
      2 months ago

      The maintainer has a duty to publicly note any changes they make so that their users are aware and can consent to continue using the platform with said changes.

      Edit: Also putting the burden on a user to be tech savvy enough to discover changes made should also be something made aware to the users. In addition, a user did audit the code and found out what the changes were and got railroaded as a result (db0)…