Perry
I guess it depends on how this “Data Protection Review Court” actually functions in practice. What is written on paper doesn’t seem to really matter much to US agencies so we’ll see how strong these safeguards actually are.
Nevertheless, it’s good to see that the new agreement is finally in place at least. We’ve had this legal vacuum for years now and it was completely unsustainable in the long run. Sans a complete legal overhaul of the nonexistent privacy laws in the US (hah good luck with that), this is probably the best we could hope for now.
I know that is a popular narrative in the Fediverse community right now, but I honestly find it unreasonable. Google and Meta didn’t kill XMPP, they abandoned it and without them it went right back to where it was originally: barely used whatsoever. The Fediverse already has a small, but relatively healthy user base. Meta can abandon ActivityPub or twist it into something unacceptable, but all that will do is bring us back to where we are right now.
All that is irrelevant, though, because the difference is that Meta is legally required to incorporate interoperability with other services and that’s why they are going with ActivityPub. Not from the good of their hearts, but because they need to and is in their own self interest to keep alive.
Right now, they are early adopters of ActivityPub and have a very early strong position there. When they federate they will be by several magnitudes the largest instance on the network. Whether we like it or not, they will inevitably be a major player in dictating the future of ActivityPub. Thus, they want to keep ActivityPub alive because they want to make sure that becomes the future EU mandated industry standard for SoMe. Otherwise, some other technology will be chosen, one that might not be lead by Meta, but by Google, Apple or ByteDance.
Note, that I’m not arguing whether this is good or bad, but only what I predict is happening.
Interestingly it seems like the main reason is not the enormous data gathering list that has been posted a few times, but rather the connection to Instagram and whether the two services are allowed to share user data.
Meta is also using Threads as a test bench for the Digital Markets Act, so they are probably holding off the launch until they can get federation going.
Meta has several billion active users across their platforms. 30M is nothing to them.
Also don’t forget that we’re talking about a microblog, so it will inherently generate a large amount of individual posts, much more so than e.g Instagram. The quality is however likely very low initially and a lot of users are probably just trying out the current talk of the day.
I do suspect that Threads will probably grow to a few hundred million users before the end of the year; anything less would probably be regarded as a colossal failure for Meta.
We migrated to Matomo, which has very similar functionality as GA, but can be self hosted and is GDPR compatible. It can even be configured to run without consent since it doesn’t build a third party ad profile, which should actually improve the data coverage a bit.
The tracking API is a little different than GA so we had to redo some things to get all the events to trigger properly (especially for e-commerce), but for basic usage statistics it’s relatively plug and play in the tag manager.
You use an Instagram account to register a Threads account, but they are two different services. After the Threads account is linked, there is however no way to remove that account without also removing the Instagram account.
Just for comparison, there are something like 2.3 BILLION Instagram accounts.
I don’t want a Meta account, but I want to communicate with the billions of people who do, including all of my family and friends.
But that is the power of the Fediverse. There is room for both small isolated instances as well as those that are part the larger “main” network, and everything in-between.
Just to put it in perspective, there are about 15 million users total in the entire Fediverse, of which ~9 million are on Mastodon.