So - counter-example. I’m working with a UK organisation that currently still uses Twitter. I’m trying to persuade them to start their own Mastodon instance instead. Being able to reach Threads users, in addition to Masto uses would clearly be substantial selling point of setting up a Mastodon server - given the size of the Threads userbase - and much preferable to them starting a Threads account.
It would be right now, but the first step of Embrace Extend Extinguish is that: Embrace. Opening up to threads now might be extremely detrimental to the fediverse in the future, in the same way as happened with XMPP.
By this argument nothing should ever interoperate with anything else because clearly that’s the first step toward destruction.
I’m writing this on Firefox, which interoperates with Chrome and Edge. Oh no! We need to get these browsers operating on incompatible protocols stat, before they all extend and extinguish each other.
In reality, “embrace extend extinguish” is not a law of nature. XMPP is not ActivityPub. They are separate things with separate circumstances. Did you know that XMPP is actually still functional and open and you can download clients and servers that use it to this day? The stories about how Google “destroyed” it have become wildly distorted folklore at this point.
Maybe on your instance - it’s your loss. But admins have a choice - defed from them and lose access to all those users and having actual content worth looking at, or federate with them and actually grow your network into something that has enough going on to make people interested. As it is, I use Threads right now. I strongly prefer it to Mastodon. Kbin comes close, but has less content to idly scroll through. If no Fediverse site I use supports Threads, I’ll keep on using it.
I’ll take a smaller volume of stuff from people who want to engage over the quality of mass produced lowesr common denominator content that will come from Meta products.
The great thing about the Fediverse is that you can choose that even if Threads federates. You pick what you engage with, which communities and instances you subscribe to and which you block.
A bunch of people are pretty disgusting on the established fediverse as well. It’s just that nobody has a way of imposing themselves in your feed.
And I don’t use Lemmy, nor will I use Threads. I use services that broadcas information with both - that’s different. I made a web site once, that doesn’t make me a Google Chrome user. I send emails with Gmail users, but I still don’t use Gmail. I just co-exist with people who do.
Why can’t you do that? Use one of the many non-Threads servers to do it. Like Kbin, the one you’re already using. Nothing about it changes if Threads federates.
I want to stay as far away from Facebook as possible, my actual private data is safe because the login stuff doesn’t get federated and there isn’t much of it.
Not at all. They get defederated. Fuck em.
I think one of the points - and strengths - of the Fediverse is that a single person or instance can’t make that choice for others.
Most lemmy instances defederated that Facebook BS factory right after it was announced.
True, a single person cant, but everyone agrees that Facebook can go fuck itself and that it ain’t getting the stuff from us.
So - counter-example. I’m working with a UK organisation that currently still uses Twitter. I’m trying to persuade them to start their own Mastodon instance instead. Being able to reach Threads users, in addition to Masto uses would clearly be substantial selling point of setting up a Mastodon server - given the size of the Threads userbase - and much preferable to them starting a Threads account.
Thats a different story.
How so? It’s a direct benefit of federation
It would be right now, but the first step of Embrace Extend Extinguish is that: Embrace. Opening up to threads now might be extremely detrimental to the fediverse in the future, in the same way as happened with XMPP.
By this argument nothing should ever interoperate with anything else because clearly that’s the first step toward destruction.
I’m writing this on Firefox, which interoperates with Chrome and Edge. Oh no! We need to get these browsers operating on incompatible protocols stat, before they all extend and extinguish each other.
In reality, “embrace extend extinguish” is not a law of nature. XMPP is not ActivityPub. They are separate things with separate circumstances. Did you know that XMPP is actually still functional and open and you can download clients and servers that use it to this day? The stories about how Google “destroyed” it have become wildly distorted folklore at this point.
God forbid if Microsoft decided to use open document formats by default and to phase out docx - it would clearly be the first step of EEE!
God forbid companies use the world wide web - they’ll run it down the gutter!
The standards must be protected at all costs - may they never see mass adoption.
It might, yes. But I think the risk can be managed, with defederation if need be. I don’t think existing Fediverse users are suddenly going to defect.
Maybe on your instance - it’s your loss. But admins have a choice - defed from them and lose access to all those users and having actual content worth looking at, or federate with them and actually grow your network into something that has enough going on to make people interested. As it is, I use Threads right now. I strongly prefer it to Mastodon. Kbin comes close, but has less content to idly scroll through. If no Fediverse site I use supports Threads, I’ll keep on using it.
I’ll take a smaller volume of stuff from people who want to engage over the quality of mass produced lowesr common denominator content that will come from Meta products.
The great thing about the Fediverse is that you can choose that even if Threads federates. You pick what you engage with, which communities and instances you subscribe to and which you block.
Ok, bad for you, you get Facebook in your life.
Yes, indeed - which is why it would be good for them if Threads federated, and they could reach their network without using a Meta service.
For some users the network is a really important part of social networks.
By federating you do use their stuff. Also the people there are reportedly pretty ew.
A bunch of people are pretty disgusting on the established fediverse as well. It’s just that nobody has a way of imposing themselves in your feed.
And I don’t use Lemmy, nor will I use Threads. I use services that broadcas information with both - that’s different. I made a web site once, that doesn’t make me a Google Chrome user. I send emails with Gmail users, but I still don’t use Gmail. I just co-exist with people who do.
That would be a shame. Why shouldn’t I be able to directly tell Mark to go fuck himself without going anywhere near his software?
Why can’t you do that? Use one of the many non-Threads servers to do it. Like Kbin, the one you’re already using. Nothing about it changes if Threads federates.
Because i don’t want him to even know i exist…
And you are getting into his software, your stuff gets federated and they are likely to try and federate ads into the cloud.
If you want to stay private, probably avoid a networking protocol like ActivityPub that inherently relies on essentially everything being public
I want to stay as far away from Facebook as possible, my actual private data is safe because the login stuff doesn’t get federated and there isn’t much of it.
I don’t mean to alarm you, but Meta can see this post even if Threads doesn’t federate.
I mean obviously, but why gift it to them on a silver plate?
Why not? It’s no different as far as Meta is concerned, it only inconveniences us.