That only works if we care about the bells and whistles they add. Nobody here does or else we’d still be on those platforms. That strategy just doesn’t work with a federated network that doesn’t connect to your instance.
They’ll have their own instance with bells and whistles that nobody connects to and we’ll have our federated network. It’ll be exactly like the current structure but they’ll have an instance instead of a dedicated platform.
Meta has a monetary interest in divering from the activity hub standard. They will use it to stand out from all other federated instances with cool features you can only use on meta instances.
New people will join metas instances because they are “clearly better” and it will be difficult to deny. Sure there will be ads, privacy concerns etc. but most people don’t care about that.
The rest of the federated network will over time lose users to meta because people want to stay connected and that’s difficult to do when two instances don’t share the same features.
The end result is meta oficially forking activity hub and disconnecting from the rest of the federated network.
It’s the death of activity hub and what we are trying to build here.
The only way to prevent it is by preventing meta instances from taking off. The main way to do that is to not allow their instances to benefit from the rest of the federated network and to inform meta users of better alternatives. It’s impossible for a disorganized opensource project to keep up with the features that 1000’s of meta developers are paid to do.
That only works if we care about the bells and whistles they add.
Like accessibility features? Moderation tools? Profile migration? It may be different in beehaw.org, but here on kbin.social those are features we’re lacking. To my knowledge, moderation is explicitly undefined by the entire ActivityPub spec.
Just in case it wasn’t clear, I hate Meta. I hate them with a burning passion. I don’t want to see them burn down the fediverse like they’ve done to online privacy and democracy as a whole. But they’re not something we can afford to scoff at and ignore.
They won’t be offering bells and whistles we want, they’ll be offering features we need. They’ll run their own troll farms, brigading their way across the fediverse, and say “look at all these trolls! We’re gonna create moderation tools to stop these ne’erdowells! And we’ll integrate them into the spec, and give them to you! For free!”
We’re all proud to say we wouldn’t fall for such a Trojan horse, but we need to be ready to recognize whatever that Trojan horse looks like.
Like accessibility features? Moderation tools? Profile migration? It may be different in beehaw.org, but here on kbin.social those are features we’re lacking. To my knowledge, moderation is explicitly undefined by the entire ActivityPub spec.
Which are already being developed as the r/blind community has migrated to Lemmy and is getting those taken care of or at least getting the ball rolling. I’m sorry Kbin doesn’t have that traction yet, but it too will get there. Again, we’re still in alpha/beta stages of these platforms. These things take time.
Just in case it wasn’t clear, I hate Meta. I hate them with a burning passion. I don’t want to see them burn down the fediverse like they’ve done to online privacy and democracy as a whole. But they’re not something we can afford to scoff at and ignore.
It is something we can ignore because it literally can’t happen unless nobody defederates them when they get it going. Which, looking at all the community discussion isn’t going to happen. You can relax.
They won’t be offering bells and whistles we want, they’ll be offering features we need. They’ll run their own troll farms, brigading their way across the fediverse, and say “look at all these trolls! We’re gonna create moderation tools to stop these ne’erdowells! And we’ll integrate them into the spec, and give them to you! For free!”
They’re all attached to Meta still, it’s a moot point. Nobody who deliberately moved to decentralized platforms is going to go back to a centralized instance to use tools they haven’t been using all this time, it doesn’t make sense.
Let them make instances and hundreds of bots on them, we’ll defederate those too. Which is the beauty of the fediverse design, we get to keep control of our communities and keep them safe. Just like beehaw defederated from lemmy.world (temporarily) until moderation tools get more powerful.
That only works if we care about the bells and whistles they add. Nobody here does or else we’d still be on those platforms. That strategy just doesn’t work with a federated network that doesn’t connect to your instance.
They’ll have their own instance with bells and whistles that nobody connects to and we’ll have our federated network. It’ll be exactly like the current structure but they’ll have an instance instead of a dedicated platform.
Meta has a monetary interest in divering from the activity hub standard. They will use it to stand out from all other federated instances with cool features you can only use on meta instances.
New people will join metas instances because they are “clearly better” and it will be difficult to deny. Sure there will be ads, privacy concerns etc. but most people don’t care about that.
The rest of the federated network will over time lose users to meta because people want to stay connected and that’s difficult to do when two instances don’t share the same features.
The end result is meta oficially forking activity hub and disconnecting from the rest of the federated network.
It’s the death of activity hub and what we are trying to build here.
The only way to prevent it is by preventing meta instances from taking off. The main way to do that is to not allow their instances to benefit from the rest of the federated network and to inform meta users of better alternatives. It’s impossible for a disorganized opensource project to keep up with the features that 1000’s of meta developers are paid to do.
Like accessibility features? Moderation tools? Profile migration? It may be different in beehaw.org, but here on kbin.social those are features we’re lacking. To my knowledge, moderation is explicitly undefined by the entire ActivityPub spec.
Just in case it wasn’t clear, I hate Meta. I hate them with a burning passion. I don’t want to see them burn down the fediverse like they’ve done to online privacy and democracy as a whole. But they’re not something we can afford to scoff at and ignore.
They won’t be offering bells and whistles we want, they’ll be offering features we need. They’ll run their own troll farms, brigading their way across the fediverse, and say “look at all these trolls! We’re gonna create moderation tools to stop these ne’erdowells! And we’ll integrate them into the spec, and give them to you! For free!”
We’re all proud to say we wouldn’t fall for such a Trojan horse, but we need to be ready to recognize whatever that Trojan horse looks like.
Which are already being developed as the r/blind community has migrated to Lemmy and is getting those taken care of or at least getting the ball rolling. I’m sorry Kbin doesn’t have that traction yet, but it too will get there. Again, we’re still in alpha/beta stages of these platforms. These things take time.
It is something we can ignore because it literally can’t happen unless nobody defederates them when they get it going. Which, looking at all the community discussion isn’t going to happen. You can relax.
They’re all attached to Meta still, it’s a moot point. Nobody who deliberately moved to decentralized platforms is going to go back to a centralized instance to use tools they haven’t been using all this time, it doesn’t make sense.
Let them make instances and hundreds of bots on them, we’ll defederate those too. Which is the beauty of the fediverse design, we get to keep control of our communities and keep them safe. Just like beehaw defederated from lemmy.world (temporarily) until moderation tools get more powerful.