Since Threads isn’t federating yet, there’s no particular rush to announce a stance. Especially while the developer is still playing catch up following the user growth.
Yep, and if Threads is enforcing the same TOS as Instagram, there’s no way that Meta is going to open the doors to the fediverse in general. I expect that when Meta does enable federation, it will be with a small number of vetted servers that agree to follow their TOS as well.
I understand people’s concerns with Threads, and don’t want to touch it with a ten foot pole myself, but a lot of the reaction posts are sensationalized.
No, I don´t think that you really understand the concern. Specially if, as you say, Threads will slowly federate this and that server, poisoning the fediverse.
If Threads begins federating, the “ten foot pole” is going to touch you, like it or not.
Independently from what Meta wants, do you want to federate with them?
Seems like you didn’t really understand my point. Meta is very averse to, for example, any NSFW content, or using words that aren’t G-rated to talk about other people. I do not think there will be a slow creep of Meta federating with server by server, because I do not think 99% of servers are willing to abide by those restrictions. If you want me to make up numbers, I think Meta will federate with 10 servers, at most, and that’s it.
The other part of the equation, from what I understand, is authorized fetch. If servers implement that, that prevents Threads from accessing their content from a middle-man server if defederated.
So no, I don’t want to federate with them. But I also think that writing off kbin because Ernest hasn’t already defederated is a premature, knee-jerk reaction.
I do understand your point. You are case 1: Meta federates with remote instance with no contractual relationship.
Case 1 will never happen because Meta will never allow uncontrolled content over their platform, they will always, always demand that yous sign an agreement before you write anything on their servers. Their lawyers will never allow strangers to publish just like that.
I’m taking about case 2: where Meta federates servers who agree to sign a chart with Meta. A legal framework, which also involves content moderation control, data flow control, etc. And this will cause a big risk of Meta slowly pushing their changes into the protocol. The more servers follow the bigger the danger becomes for everyone.
It’s not a knee-jerk reaction, it’s a safety precaution against a corporation of which we know the methods. Do you know of a bigger predator to us?
They don’t want your friendship, they don’t care at all about this open source fediverse thing. We are a risk to their business, nothing else. Other fell before, other will fall after. There is nothing to gain here for us and everything to lose, so block it.
Since Threads isn’t federating yet, there’s no particular rush to announce a stance. Especially while the developer is still playing catch up following the user growth.
Yep, and if Threads is enforcing the same TOS as Instagram, there’s no way that Meta is going to open the doors to the fediverse in general. I expect that when Meta does enable federation, it will be with a small number of vetted servers that agree to follow their TOS as well.
I understand people’s concerns with Threads, and don’t want to touch it with a ten foot pole myself, but a lot of the reaction posts are sensationalized.
No, I don´t think that you really understand the concern. Specially if, as you say, Threads will slowly federate this and that server, poisoning the fediverse.
If Threads begins federating, the “ten foot pole” is going to touch you, like it or not.
Independently from what Meta wants, do you want to federate with them?
Seems like you didn’t really understand my point. Meta is very averse to, for example, any NSFW content, or using words that aren’t G-rated to talk about other people. I do not think there will be a slow creep of Meta federating with server by server, because I do not think 99% of servers are willing to abide by those restrictions. If you want me to make up numbers, I think Meta will federate with 10 servers, at most, and that’s it.
The other part of the equation, from what I understand, is authorized fetch. If servers implement that, that prevents Threads from accessing their content from a middle-man server if defederated.
So no, I don’t want to federate with them. But I also think that writing off kbin because Ernest hasn’t already defederated is a premature, knee-jerk reaction.
I do understand your point. You are case 1: Meta federates with remote instance with no contractual relationship.
Case 1 will never happen because Meta will never allow uncontrolled content over their platform, they will always, always demand that yous sign an agreement before you write anything on their servers. Their lawyers will never allow strangers to publish just like that.
I’m taking about case 2: where Meta federates servers who agree to sign a chart with Meta. A legal framework, which also involves content moderation control, data flow control, etc. And this will cause a big risk of Meta slowly pushing their changes into the protocol. The more servers follow the bigger the danger becomes for everyone.
It’s not a knee-jerk reaction, it’s a safety precaution against a corporation of which we know the methods. Do you know of a bigger predator to us?
They don’t want your friendship, they don’t care at all about this open source fediverse thing. We are a risk to their business, nothing else. Other fell before, other will fall after. There is nothing to gain here for us and everything to lose, so block it.