The exchange is about Meta’s upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!
The exchange is about Meta’s upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!
I mean worst case you’ll see @meta.com accounts in your Federated feed in Mastodon (which for pretty much every instance is already a complete mess), I don’t even really see how it’ll affect Lemmy or Kbin, as they’re community driven rather than user driven. I follow users with Mastodon, I follow communities with Kbin.
I dunno, maybe I’m being necessarily optimistic, but I do have friends and family who are posting on Insta/FB, and I basically maintain an account there to keep up with them. I’d love to be able to keep that connection without having to actually be locked into Meta’s platforms. And I do think at least a few of my tech savvy friends would be willing to give a client like Ivory a go if they’re able to do the same.
Their idea is likely to eventually present themselves as the “better part of the network” and make migrating to their servers very easy.
This must be prevented at all costs.
I was talking about this with someone here the other day, and this seems like the logical direction for them. They’ll create a cloud of instances that users are able to utilize and create their own communities with relative ease compared to compiling the code and doing the base level software management, and also develop Meta-specific featuresets on those servers to lock people onto their platform. Oh, you want to break away from us and manage your own instance? Have fun doing it the hard way, and without features XYZ that are only available from us!