Comment on X’s deepfake porn feature clearly violates app store guidelines. Why won’t Apple and Google pull it?

lmmarsano@lemmynsfw.com ⁨3⁩ ⁨weeks⁩ ago

• Sunflier@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  The difference between the two is that, while the browser can be used to access child porn, X actively generated the porn.

  source

  • lmmarsano@lemmynsfw.com ⁨3⁩ ⁨weeks⁩ ago

    The browser can access X. Isn’t material produced from actual child sexual abuse worse than depictions generated without it?

    source

    • Sunflier@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      The browser can access X & any website.

      A browser doesn’t activately generate it. X did.

      Isn’t material produced from actual child sexual abuse worse than fictions generated without it?

      They’re both equally as bad because they result in the same things: production and advancement of child porn.

      source

      • lmmarsano@lemmynsfw.com ⁨3⁩ ⁨weeks⁩ ago

        Actual child sexual abuse is equally as bad as fiction? Are you trying to distort truth or diminish the meaning of child sexual abuse until it’s meaningless?

        So, pull X-only client, but keep everything client that still accesses X, which results in no effective change: what does that accomplish?

        source

        • -> View More Comments