Artists have finally had enough with Meta’s predatory AI policies, but Meta’s loss is Cara’s gain. An artist-run, anti-AI social platform, Cara has grown from 40,000 to 650,000 users within the last week, catapulting it to the top of the App Store charts.

Instagram is a necessity for many artists, who use the platform to promote their work and solicit paying clients. But Meta is using public posts to train its generative AI systems, and only European users can opt out, since they’re protected by GDPR laws. Generative AI has become so front-and-center on Meta’s apps that artists reached their breaking point

  • Zak@lemmy.world
    link
    fedilink
    English
    arrow-up
    40
    ·
    6 months ago

    I think it would be great for new social things like this to just speak ActivityPub. They can build up their own user experience and culture while joining a larger network. I don’t have a problem with the software itself being non-free if the protocols are and they commit to supporting account migration.

    • Frank Ring@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      6 months ago

      Pixelfed already does support the image import from Instagram.

      Mastodon doesn’t seem to support any import from Twitter/X.

      I’m assuming account migration from the main social media platforms to be an important feature.

      But I don’t think supporting ALL social media is realistic unless they all follow the same norms. Which I really doubt.

      • Zak@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        6 months ago

        ActivityPub supports alsoKnownAs and movedTo so that users can migrate their social graphs to a different server or software. Of course that doesn’t work for migrating from networks that don’t support ActivityPub.

        Content import is a separate issue, but I can imagine it being helpful as well.

        • danA
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          6 months ago

          ActivityPub supports alsoKnownAs and movedTo so that users can migrate their social graphs to a different server or software.

          The annoying thing with ActivityPub is that your username/handle is tightly coupled to a particular server, and moving server requires you to change your handle. Everywhere you’ve mentioned/documented your old handle is now out of date.

          Bluesky handles this a lot better. If you own a domain, you can use it with any Bluesky server by creating a TXT record for validation. Your username is the domain name - if you own example.com, you can be @example.com on Bluesky, without having to self-host it. If you move server, you don’t have to change your username. Currently there’s just one main Bluesky server but they plan to introduce federation at some point, and their protocol is already mostly designed for it.

          • Zak@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 months ago

            And the losing server has to cooperate, which is why I mentioned the commitment to support migrating away.

            ATProto/Bluesky has some interesting ideas, and I’m interested to see how that develops as third parties start supporting the protocol. For a new service launching now, I think ActivityPub is the more important protocol to support, but it’s presumably possible to support both.

    • mryessir@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      6 months ago

      This would be a good approach to improve growth of the community.

      Does the ActivityPub protocol support copyright for user content? E.g. an artist releases some picture and they explicitly prompt a license. Each client should accept that they are obligated to prompt this license when using the content… Something like this

      • far_university1990@feddit.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        Not found anything on send license or agree before receive for protocol.

        But could maybe do with federation: federate only with instance that agree on license for all user content, make all user read and sign license. Turn off access without account.

        People can always break license, so can never be perfect.

        • mryessir@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 months ago

          Would this again segregate the users? Some attribute on a submission which refers to a license would be nice though