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
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.
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.comon 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.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.