In today's "WordPress/Jetpack/Automattic are the ones killing blogging, not Google": Jetpack Stats is now going to be a paid feature for "Commercial Sites"
I'll keep repeating myself: it's the like of #WordPress and #Automattic that are taking every chance to make it harder to keep your own blog. Not the lack of Google Reader which – and let's be honest there – had been a horrible solution for the last year of its existence.
MNT Reform CM4 modules will be available this fall (upgrade the modular laptop’s processor)
The MNT Reform is an unusual laptop with made open hardware and software principles in mind, and featuring a modular, customizable, and upgradeable design. When the MNT Reform began shipping a few years ago, it was only available with a single processor option. Since then the folks at MNT have been working on several additional system-on-a-chip solutions for the computer. And…
@voxpelli I know, but the #WordPress plugin responsible for posting this to Mastodon doesn't incorporate hashtags. I'd love it if #automattic would add an option to automatically use Wordpress post tags as hashtags... just saying.
He is currently doing a live stream for Tumblr users, and in response to an epileptic user asking if there could be a standard to prevent vibrant, strobing ads as they’re a seizure risk, he made some vague noises like “yeah I guess” then instantly uggested that the user buy the no-ad upgrade.
The #Fediverse’s worries over #Threads allowing abusive behaviour to spill over to networks here would also be a problem for Threads » Tumblr » Twitter if any of these federated.
On existing fediverse or #mastodon instances that would be overwhelming,
For large commercial to commercial instances what would it be? A reason to share resource or develop collaborative strategies against abuse?
Or simply imposition of external moderation costs? Incentive to defederate?
Other than that I guess it will be a game of cat and mouse as with the antispam measures adopted by the largest email providers who can't outright disconnect from each other (as they do with smaller players)?
I just had a look at #Meta's recent press release about #Threads, and something caught my attention right away.
For the very first time, they're acknowledging another #Fediverse platform alongside #Mastodon. Specifically, they're highlighting that #WordPress can now connect through #ActivityPub.
Now, you know Meta's PR department doesn't say things by accident. So here's why this is a big deal. Last time I checked, WordPress powers a whopping 43% of the Internet. Yeah, you heard that right! If you visit a website, there's a good chance it's using WordPress as its CMS.
Now, if even a fraction of those WordPress sites start federating, it could have a huge impact on the network effect of the Fediverse. Of course, Meta isn't oblivious to this. I've been talking about the potential of WordPress and ActivityPub for quite some time now.
But if you're particularly observant, you might also notice that they mention #Tumblr. We've known for a while that Tumblr is likely to integrate ActivityPub into their platform.
But here's an interesting tidbit: Did you know that one company, Automattic, not only owns Tumblr but is also the driving force behind WordPress?
I don't want to jump to conclusions, but once again, PR departments don't just drop hints randomly. I have a strong feeling that Meta has been having some high-level discussions with Automattic about the future of ActivityPub. It wouldn't surprise me if Meta has some insights into Automattic's upcoming plans for the Fediverse.
@tim@pfefferle Just to make it clear, I don't mean to suggest any sort of conspiracy here. I'm not implying that #Meta and #Automattic are secretly working together or anything like that. I'm simply suggesting that it's possible they've had conversations about #ActivityPub. It's a reasonable assumption, especially considering Meta has already been in discussions with admins who manage major Fediverse servers.
@WA5PSA I want to clarify that I'm not suggesting that #Meta and #Automattic might potentially take over the Fediverse. Instead, I'm talking about the current reality where #WordPress can already federate through #ActivityPub, and #Threads will be able to do the same in just a few months.
Now, you might be wondering if this will impact the independence of #Mastodon. Well, it's highly unlikely. Each Mastodon server operates independently from one another, and there's now over 10,000 servers out there. Even if Meta tried to acquire a few prominent servers, they couldn't possibly buy them all.
And as for the concern about Meta and Automattic overpowering Mastodon, there's no need to worry. Every Mastodon server has the power to decide what content gets displayed on their own server, and they can even choose not to federate if they prefer.
It's worth noting that Mastodon is just one type of server software that utilizes ActivityPub. There are other software options like #Kbin, #Friendica, and #Akkoma. By the way, I'm currently using #Calckey myself.
From a broader perspective, Threads is just one node among many, and we, as a collective, comprise numerous nodes.
I hope that explanation makes things clearer for you! Let me know if you have any more questions.
Have you seen the latest update from the #Instagram Help Center? It offers insight into how #Meta views the #Fediverse. Let's take a closer look at the highlighted text together:
"#Threads is planning to use a protocol called #ActivityPub to connect with other servers that support this protocol. Our aim is to enable communication between Threads and users on different fediverse platforms that we don't own or control."
Now, considering everything we know about Meta and their business practices, you might wonder why they're doing this. Well, here are a few reasons that could shed some light:
Regulatory pressure: While Meta is doing its best to compete with #Twitter, they also want to avoid appearing like a monopolistic force. By joining the Fediverse, they can show regulators that they are simply becoming part of an existing social network.
Zuckerberg's strategy: Mark Zuckerberg has been observing what's been happening with Twitter ever since Elon Musk acquired it, and he's learned some lessons. Twitter has faced criticism for various missteps like alienating journalists, restricting API access, and even requiring logins to view tweets. Zuckerberg wants to assure people that Threads is different from Twitter and avoid those same pitfalls.
Embracing social media decentralization: It's widely acknowledged in the social media industry that the future lies in decentralization. The era of closed-off platforms is gradually coming to an end. Just as Compuserve couldn't survive the open Internet, walled garden social media platforms won't be able to thrive in the open Fediverse. Meta doesn't want to become the next Compuserve.
Early entry into an emerging ecosystem: Meta is eager to establish itself in the emerging Fediverse ecosystem, much like they tried to do with the Metaverse. Being an early player allows them to take a leadership position before other major players like #Google, #Apple, and #Automattic jump on board.
However, it's worth noting that there might be a personal rivalry at play here. There have been rumors of a rivalry between Zuckerberg and Musk, and it seems they don't particularly like each other. So, one could speculate that Zuckerberg might want to undermine Musk by taking down Twitter, the platform Musk acquired for a hefty sum of $44 billion.
Hope that provides some context and clarity on why Meta is making these moves.
What do you think about Meta’s Fediverse explainer?
Big Journalism's abject capitulation to Musk, despite his loathing of their work and promotion of democracy's enemies, will not change unless he makes Twitter unusable.
Given the latest fail, perhaps practicality will prevail over honor.
But this would require work on the part of journalists and their employers. They may consider that to be an insurmountable barrier.
Which, by the way, is why #Automattic making strides into integrating #ActivityPub support for #Wordpress by default is such a massive win. It means that any blog or magazine that uses WP should be able to enter the #Fediverse with the click of a button. The big deal is to ensure that bloggers actually go and click that button!
Watching #Elon and now #Reddit CEO Huffman run the same play, it makes me think that Matt Muellenweg may be the only tech CEO left that I can think of has any credibility on the #OpenWeb. #WordPress#Automattic
Das war Inspiration genug um einen Monat später mit meinem eigenen kleinen b2 Blog an den Start zu gehen.
Mittlerweile begleitet mich das kleine stückchen PHP-Code fast mein halbes Leben und ich hätte nie daran gedacht, dass ich mit meinem Hobby-Projekt irgendwann mein Geld verdienen würde!
Während meinen 7++ Jahren bei IONOS hatte ich nebenher immer mal wieder mit WordPress zu tun. 2020 bekam ich aber die Möglichkeit, mit einem kleinen Team zusammen, das WordPress Hosting neu/mit zu gestalten. Aus diesem kleinen dreiköpfigen WordPress-Team wurde in den folgenden drei Jahren ein großartiges Haufen von 15+ Personen (inklusive Support, PO, PM, …).
Neben dem daily business haben wir IONOS in dieser Zeit ein kleines bisschen näher an die Community „geschubst“ (zumindest rede ich mir das ein 😉 ). Wir haben einen GitHub Account gestartet, den Entwicklern Zeit für die Five for the Future Initiative frei geräumt und IONOS wurde Teil der (Make) Hosting Community.
In diesem Zuge habe ich mich auch persönlich engagiert und dafür im Juni das Hosting Team Badge „verliehen“ bekommen.
2021
Mein aktivstes Jahr beim Pluginkollektiv. Ich mag die Idee und schätze die Plugins sehr! Ich hoffe ich finde in Zukunft wieder etwas mehr Zeit für das Kollektiv, immerhin arbeite ich ja jetzt hauptberuflich an ActivityPub & Co. und brauche deshalb wieder ein neues Hobbie/Freizeitprojekt 😉
2022
Im März fand der CloudFest Hackathon im Europa-Park statt und ich hatte die Chance, ein Thema zu betreuen. Drei Tage WordPress, IndieWeb und Webmentions <3
Ich bin gespannt was dieses Jahr noch mit sich bringt und wie die Zukunft von WordPress aussieht.
Wenn es nach mir ginge, dann würde daraus ein „open, portable, interoperable, small, social, synaptic, semantic, structured, distributed, (re-)decentralized, independent, microformatted and federated social“ WordPress 😉
It's not worth bemoaning that #ActivityPub is, in fact, an open protocol.
And this is because it's not worth bemoaning that #SMTP is an open protocol. Or Hypertextual Transfer Protocol (#HTTP) is an open protocol.
Or for that matter that anyone can use these protocols as they see fit.
Do I like every use of these protocols? Not at all. We can't always have good things because shady assholes insist on exploiting the open web for their own greed.
The trade off is that we get to have an open web.
Now occasionally, I get people popping by who tell me, "Screw you! I don't care about an open web! I just want to keep my community intact!"
But the only reason your community exists is because we have open protocols.
If you don't think so, find me all those thriving communities still using AppleTalk or IPX/SPX. Wait. There aren't any.
And that's because the only entities that have bothered with a closed, proprietary protocol happen to be for-profit corporations that have largely discontinued them due to -- again, wait for it -- the prevalence of open protocols.
Which brings us to a further problem.
You can't use an open protocol while simultaneously pushing for it to be closed. The #W3C already validated ActivityPub. The proverbial cat is out of the bag.
So yes, corporations will adopt ActivityPub. That's already happening. #Meta, #Automattic, #Medium, #Flipboard -- many more to come -- are developing for it.
But openness also means you can build upon it. You can create your own thriving communities. And some of these communities can be private if you so choose.
Just as it's possible for you to build your own newsletter or publish your own webpage, it's possible for you built your own #Fediverse server.
It's no secret that there's lots of work going into the #ActivityPub plugin for WordPress, which currently requires installation on self-hosted blogs.
But at some point, I imagine that this may find its way to WordPress.com.
Now I've said previously that email will be core to future Fediverse adoption. Email is what drives adoption even to this day. Hell, it's what grew Substack itself.
Once the stars align for ActivityPub integration and email subscriptions, I believe this is where a federated WordPress can really shine.
Ich bin ja skeptisch, ob es für das #Fediverse wirklich so gut ist, wenn die etablierten großen Player hier mitmischen. #Automattic und #Tumblr traue ich ja noch halbwegs, aber #Meta / #Instagram?