meta (threads) will not support fediverse already. They said they will do in some later version. So for the completely practical part, you don't need to do anything right now.
i'm not here for the ton of content that meta will produce. If I wanted this content I would had been there in the first place. It looks like somebody else is in the wrong place and is dreaming of a fediverse full of brands trying to promote their products and the influencers pretending they are real life advertisements.
its funny that you measure value by that metric.
the defederation has nothing to do with "reducing meta's number". The reason to defederate is so you're not playing their game with their own rules. Fediverse will gain absolutely nothing by playing meta's game.
Am I just misunderstanding this?
yes
i'm sorry but you're naive.
If I want to post something and I want people to see it and react to it, I will post it to the side with more people.
do you know how FB or instagram work? Do you think that when you post, your post reaches your whole audience? I believe you know how they work but for some reason you chose to ignore now.
My argument is that the fedipact, if executed as desired by the people running it, will defederate from Meta and anywhere that federates with Meta.
So now you have 2 fediverses, completely separated from one another.
So, you've read the history of XMPP. Did you understand what google practically did? Simply put, meta will create new features on top of activity pub. Open source activity pub developers will be in a constant race to adapt their own projects in a way that will be compatible with meta's project. They will have no voice but to follow whatever meta decides. Users will start getting fed up that their open source instance is not behaving as well as their friend's meta instance. People will jump project and/or when users are polarised, meta will decide that they had enough with activity pub. It doesn't cover their needs and they move to another completely closed project. Users again are forces to choose side and the open source community is just left with the project which they adapted in favour of meta, but now meta is gone because they were never in the same boat actually.
Staying away from meta is a decision in the basis of protecting the whole project. It is not because people don't want to be close to the users of meta. It is because meta is not here to promote the federated networks. It is here to make profit of it and they may even destroy it if they believe that this is the way to make profit. Siding with them is naive and will never bring value in the network itself.
what you (and other likeminded people) haven't understood is that these 2 are 2 different topics. Defederating with meta is not because people don't want to be near the users of meta. It is because meta is a huge corp and it is not here to promote the idea of a federated network. It is here to make profit and to exploit the network. Allowing them to be part of the same network will just cause harm to the network itself in the end.
I suggest you reading this article https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html which is the story of how google killed XMPP, written by one of the XMPP core developers. I believe you will see the similarities.
this argument makes sense only if you're talking about defederating instances. It doesn't make sense here. The problem is not whether we want the users of meta's instances. The problem is whether we want a huge corp be part of the fediverse. And why are we talking about it? Because people are trying not being naive and believing that meta is here because they liked the ideas of a federated network and want to participate. Meta will cause more harm than good as it has already happened in the past in different technologies/projects.
meta is not here to promote open networks. They will do more harm than good. If you want to learn more about how google achieved it with the XMPP you can read the story here https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html written by one of the core developers.
i don't agree. I think it is important to maintain a blacklist instead of a whitelist where people would then submit what they need to add which will then will need to be approved etc. It will decrease the federated experience.
using your credit/debit card to verify your account is something that I also wouldn't like to do. Same as using my ID
but you're still "visiting" it. It is just your reader that makes the https request instead of your browser. In their logs and stats you are still visible. The only difference is that you will have a user-agent that shows that it is an RSS reader instead of a browser. Like:
"GET /atom.xml" 304 0 "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 16 subscribers; like FeedFetcher-Google)"
And while you've the RSS reader open it while make requests periodically so we're talking for multiple visits as well.
view more: next ›
duringoverflow
joined 3 years ago
large companies and influential people are in the commercial platforms because of the ads. There is literally no reason for them to move in a place without ads.