In other news, Discourse, the free forum platform, is now joining the Fediverse.
Yep, Discourse forums will become compatible with Mastodon!
https://meta.discourse.org/t/activitypub-plugin/266794/116
So the big fear that existing Fediverse communities will be overrun with Threads content is moot? That seems to be the main concern people have.
I don’t see what the problem with them reading ActivityPub data is. That’s what it’s for. These communities are not private and there was never any need for Threads to integrate ActivityPub for them to “ingest” the content from them.
The problem is not them reading data, but that Threads will take Fediverse content, and display it on Threads. In the opposite direction, Fediverse will only see the select few user content that do actually opt-in, and let’s be honest here, most users won’t know what the Fediverse is, except for again the few people that are on both platforms.
This is absolutely not “playing nice” as you’ve put it before, and purely parasitic and, again, purely a greed decision by Meta.
I don’t really know why you are shilling so hard trying to excuse absolutely unexcusable behavior.
I’m not shilling. As I’ve said repeatedly, I don’t like Meta. But I just don’t see what problem this is. Sitting here on kbin.social, how does it affect me if someone over on Meta is seeing my posts and comments?
Before you talked about the Fediverse as a whole, now from a single user perspective.
IMO it affects the Fediverse as a whole by abusing it. The whole idea is an open network, where instances can federate with each other to bilaterally share information and create a seemingly single platform. This is not the case with the planned Threads integration, because they explicitly plan to feed on the content, but hiding sharing their own content behind an (for most of their userbase) obscure opt-in.
From a single user perspective it doesn’t affect you directly. But it affects the platform you are part of with malicious intent.
I am not against Threads joining the Fediverse, and I do actually think it would be great for the growth of the Fediverse if actual big players join, and if it brings content that I personally do not like to see, I can use the tools available (e.g. blocking user/communities/instances) to hide it. But only if they plan on joining as a “regular instance” like any other - but Meta does not intent doing so, since they have chosen the opt-in with obvious intent of simply gaining additional content on their walled platform for their own gain.
The Fediverse is made up of individual users. If Threads isn’t broadcasting its content out to other instances, how does it affect anyone out there on those other instances? They’ll never see a thing. I used a single example user (myself) simply to illustrate that.
So the big fear that existing Fediverse communities will be overrun with Threads content is moot? That seems to be the main concern people have.
I don’t see what the problem with them reading ActivityPub data is. That’s what it’s for. These communities are not private and there was never any need for Threads to integrate ActivityPub for them to “ingest” the content from them.
The problem is not them reading data, but that Threads will take Fediverse content, and display it on Threads. In the opposite direction, Fediverse will only see the select few user content that do actually opt-in, and let’s be honest here, most users won’t know what the Fediverse is, except for again the few people that are on both platforms. This is absolutely not “playing nice” as you’ve put it before, and purely parasitic and, again, purely a greed decision by Meta. I don’t really know why you are shilling so hard trying to excuse absolutely unexcusable behavior.
I’m not shilling. As I’ve said repeatedly, I don’t like Meta. But I just don’t see what problem this is. Sitting here on kbin.social, how does it affect me if someone over on Meta is seeing my posts and comments?
Before you talked about the Fediverse as a whole, now from a single user perspective.
IMO it affects the Fediverse as a whole by abusing it. The whole idea is an open network, where instances can federate with each other to bilaterally share information and create a seemingly single platform. This is not the case with the planned Threads integration, because they explicitly plan to feed on the content, but hiding sharing their own content behind an (for most of their userbase) obscure opt-in.
From a single user perspective it doesn’t affect you directly. But it affects the platform you are part of with malicious intent.
I am not against Threads joining the Fediverse, and I do actually think it would be great for the growth of the Fediverse if actual big players join, and if it brings content that I personally do not like to see, I can use the tools available (e.g. blocking user/communities/instances) to hide it. But only if they plan on joining as a “regular instance” like any other - but Meta does not intent doing so, since they have chosen the opt-in with obvious intent of simply gaining additional content on their walled platform for their own gain.
The Fediverse is made up of individual users. If Threads isn’t broadcasting its content out to other instances, how does it affect anyone out there on those other instances? They’ll never see a thing. I used a single example user (myself) simply to illustrate that.