I think it's still going to be a while until it is relevant for our server(s) in particular, but if the new Meta project wanted to add us to their federation whitelist or just simply would open up its federation, would you as a user accept this to happen, assuming they moderate properly and the instance won't die due to load mid-term? #tchncs :tchncs:
@milan
As far as this topic is concerned, I'm torn. On the one hand, I want to be able to communicate with the people who will use the platform.
Especially the company accounts, for which I still have to open Twitter, are interesting to me. It'd be the last step to be able to delete my Twitter account for good, as I use it to get information about my favorite games directly from the developers.
On the other hand, we all know how well Meta handles user data.
[1/2]
@milan
I would prefer not to lock Meta out for now, until we have a very good reason to do so.
If we block the instance(s) I'd have to make another account on another instance and while that wouldn't be that big of a deal, it'd be annoying, nonetheless.
[2/2]
@milan No, I think they care much more about their business than for the people and do not value freedom as free/ libre software does. In the long run they would probably destroy or damage platforms like Mastodon - read for example https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
@milan tbh, I voted "yes“ but after reading some arguments and thinking about this for a few days I changed my mind. In my limited view the Fediverse seems to grow healthily on its own and allowing corporate hands on it seems not to be a smart move in the long run.
@milan I'm in for the chance.
Because we're open, and we should build bridges between social networks and not walls.
If it does not work, we can always close the gates
Besides, an option in my profile could help to exclude users of the networks.
An OptIn would perhaps be a possibility
@milan Defederating from them could be a smart choice as Meta has shown its true colors many times and we know its intentions are not noble at all. Plus, Meta would bring in a huge crowd of users different to most of the existing ones in the fediverse. This could cause problems.
On the other hand this is also an opportunity for progress and growth, and Meta might not be as awful as thought until now.
It is a complicated decision that could even have to be revised as time goes by.
@milan I'm a little disturbed as to why this is even a question. Of course, social.tchncs.de must give it a chance. We can't defederate an instance upfront for ideological reasons!
@milan imo there are two aspects in that case: 1.I always encouraged everyone to use open protocols and oss to communicate. Never have all of my contacts been on the "cool" protocol (IRC, xmpp, signal, matrix) nor were those who did agree to get something "not WhatsApp" happy to change to the new cool protocol. Since matrix it has been easier to reach my contacts and I love that. Meta sure has the potential to add some more people on an open protocol. I have never been on any of their services.
@milan
so #Meta mit Whitelist arbeiten sollte und diese Liste öffentlich gemacht wird kann man immer noch entscheiden. Sollten auf der Whitelist zu viele Instanzen auftauchen die man selber blockiert hat so beantwortet sich die Frage: "Meta blocken - ja oder nein" von selbst.
@milan I am happy not to be in your shoes in this discussion. I find the question difficult to answer because it feels to me, that you try to clear it from what seems most relevant to me: the messy circumstances a federation could have. In general, I think, we should not block instances from the outset, because we somehow vaguely assume that they have bad intentions. But of course the worry, how they will process other instances user's data is legit. A NDA from ‘my’ a deal breaker for me.
@milan the fact that they started their Fediverse journey by going on a divide and conquer campaign is more than enough proof they aren't acting in good faith. My bet is that they want Mastodon content so their Twitter competitor is not a ghost town at launch and will end up closing the doors to the walled garden again when they have enough users.
@milan
I am still wondering why it needed NDA as introductions.
Yes, them coming into Fediverse will be a huge thing. It will be huge for adjacent services too, like guppe et al. There will be disruptions if Mio of new Users influx and maybe federating one by one and seeing how the servers handle it would be sensible.
But why discuss this in NDA terms?
Why the secrecy and this way of saying "hello" while the problems of scale are well understood here, not only by key people.
Add comment