In the few short hours since I started using #Threads, #DuckDuckGo has already blocked over 200 data tracking attempts. These include things like "headphone status" and "screen density."
What fuck up? If we were doing our own manufacturing, we'd be using the coal instead. We just wouldn't be able to blame other countries for our consumption.
This happened to me this morning. And because the link was from a work email but I was logged in on my personal account, Edge wanted me to sign in to view it, requiring time-wasted on a 2FA process for no good reason whatsoever (obv I just closed Edge and copied the link over to Firefox).
The loss of productivity is large regardless of which method you choose to view the link. May this be the beginning of the end for Microsoft. I am fuming.
It's difficult to get China and India off coal because they're doing most of the world's manufacturing and some processes are currently impossible without it. But 'we' exported manufacturing to Asia and 'we' buy the products the coal is used for. 'We' don't get to wriggle out of responsibility by pretending that a couple of low and middle income countries are somehow responsible for 'our' excessive consumption.
EEE is the risk, and surely their intent. But pre-emptive defederation from an instance that already has 1.6bn sign-ons is doing to ourselves exactly what google did to XMPP. If there are no independent instances allowing access to the mega-network, people who want the mega-network have nowhere else to go.
In 2013, Google realised that most XMPP interactions were between Google Talk users anyway. They didn’t care about respecting a protocol they were not 100% in control. So they pulled the plug and announced they would not be federated anymore...
As expected, no Google user bated an eye. In fact, none of them realised. At worst, some of their contacts became offline. That was all. But for the XMPP federation, it was like the majority of users suddenly disappeared. Even XMPP die hard fanatics, like your servitor, had to create Google accounts to keep contact with friends. Remember: for them, we were simply offline. It was our fault.
Mass defederation is just giving up before the fight starts. The fight may not be winnable, of course. But making the fediverse invisible to Meta users is exactly how google killed XMPP.
I get the impulse, for sure. It's upsetting, you want revenge. But would you stop to consider whether the injury to your feelings is really worth throwing someone out of work? I mean, if it's some tax-avoiding, worker-exploiting, obscenely highly paid executive, go for it. Bury them if you get the chance. But punishing a very low wage gig worker to make yourself feel better, and tightening the iron grip of the afore-mentioned executives by snitching on them? Be the better person and feel good about it.
Whatever you think of the driver's behaviour, getting someone sacked for having a bad day is a scummy thing to do. You leave them a five star review or you do nothing.
That happens whether they are defederated or not. They have 1.6bn users, the rest of the fediverse is a rounding error.
This is what happened with XMPP:
In 2013, Google realised that most XMPP interactions were between Google Talk users anyway. They didn’t care about respecting a protocol they were not 100% in control. So they pulled the plug and announced they would not be federated anymore. ...
As expected, no Google user bated an eye. In fact, none of them realised. At worst, some of their contacts became offline. That was all. But for the XMPP federation, it was like the majority of users suddenly disappeared. Even XMPP die hard fanatics, like your servitor, had to create Google accounts to keep contact with friends. Remember: for them, we were simply offline. It was our fault.
Even if the entire fediverse defederates from the Meta instance, they have a huge network which already exists. And people who want the things that a huge network brings will want to be part of it. Mass defederation will just push some people onto the Meta instance because it's the only place a huge network is operating (and many already have an Insta account so they're already on it anyway).
That's not to say that federating with them is necessarily better. Some users will prefer a smaller network. Some instances will want better moderation than Meta are likely to provide. Moderation issues might make it nigh on impossible for most instances to federate anyway.
But you can't stop them dominating the fediverse by universally defederating. That is not an option. Gmail got big enough to not need XMPP federation; Meta and other potential mega-corp instances are already huge, they don't need us at all.
The best hope might be for several mega-corp instances to hold each other hostage. Google could kill XMPP because none of its users understood that they were part of a federation and barely noticed when the tiny proportion of non-google users disappeared. But if there's a Meta instance and a Google instance and a Mozilla instance ... it's hard for one of them to unilaterally withdraw without handing their users over to a competitor.
The dose makes the poison. It is carcinogenic but current estimates are that you'd need to drink several litres a day to meaningfully increase your risk.
There are other good reasons to find a healthier drink but this isn't one of them. Most artificial sweeteners have some kind of risk attached so there is no point switching to a different diet soda.
Google killed XMPP by being the vast majority of the network and then defederating from the rest. Most of the gmail users didn't even notice anything had happened.
I see a couple of differences here. One is that it should be obvious to even the most casual of users that other instances exist. And the second is that other mega-corps have said they'll build instances too. With multiple very large instances, they may end up holding each other hostage, for fear of losing users to each other when so many people have multiple logins just because they have an account with one of the mega-corps.
One thing is for sure. Insta has 1.6bn users and it doesn't need to federate with anyone at all; the fediverse is a rounding error to them. Some people will want the massiveness of the network, others will want better moderation than the mega-corps are likely to offer, and some will prefer smaller networks anyway. There will be as many reactions as there are instances to react. And that will have to be fine.
It's a bit more than that. Cancer is caused by copying errors. Just the right errors, in just the right order. The longer you live, the more chances these copying errors get to happen in just the right order. If nothing else kills you, cancer will.
So, wealthy countries have a lot of cancer because they have a lot of people living longer. And the media loves to run stories on how terrifying this is.
The main risk factor for cancer is old age. Wealthy countries have a lot of cancer because a lot of people live long enough to get cancer.
But in this particular case, it's how the fediverse kills itself. By demanding a monolithic approach, ironically.