(1/2)

@jupiter_rowland
> Not after all the head-butting that has happened between Mike and Gargron

This is why Mike's tech remains marginal, even within the fediverse, even though it's brilliant. He just can't help being a dick to people, and blaming *them* for it. I've experienced this on and off for over a decade.

Plus he's usually been too busy building new stuff to document his work in a way other devs can grok it without asking him questions. So ... 🤷‍♂️

@tchambers @mikedev @rakoo

@Strypey Still, the headbutting was often justified for Mike. Unless, of course, you say that Mastodon is and has always been the one and only Fediverse gold standard and the one and only ActivityPub reference implementation.

I'll give you an example: In July, 2017, Mike's Hubzilla was the very first Fediverse server software to implement ActivityPub. Mike played strictly by the rules. As Hubzilla has a character limit of over 16.7 million and supports text formatting on the same level as the best long-form blogging platforms out there, he declared Hubzilla long-form and made Hubzilla send Article-type objects. Just as the spec demands.

In September, Mastodon became the second Fediverse server software to implement ActivityPub. But Gargron did not play by the rules. He only implemented a tiny subset of the protocol, namely what suited him. And he also broke it: Mastodon could display Article-type objects at their full length. But Gargron staunchly refused to implement any support for anything that goes beyond plain text. The ActivityPub spec explicitly says that Article-type objects are formatted. But Gargron wanted Mastodon to be a purist, minimalist, old-school, original-gangsta, Twitter-cloning microblogging platform. And stuff like bold type, italics, headlines, embedded in-line images or titles aren't purist, minimalist, old-school, original-gangsta, Twitter-cloning microblogging.

And so Mastodon took fully formatted, long-form-blog-style posts from Hubzilla and ripped everything out that wasn't plain text. It basically defaced Hubzilla posts. That is, it had been defacing Friendica and Hubzilla posts all the same ever since it was launched. But this time, there was a spec that actually defined what Mastodon was doing as wrong. And that spec had been finalised and pronounced a W3C standard meanwhile.

So Mike asked Gargron to please follow the official ActivityPub spec and make Mastodon support full HTML rendering for Article-type objects.

Gargron refused. Old-skool microblogging is plain text and only plain text, full stop.

This went back and forth. Eventually, Gargron presented a "solution": Mastodon now "renders" Article-type objects by showing the title and, right below, a link to the original. That is, basically not at all anymore. Of course, this meant that the vast majority of Mastodon users no longer read what came from Friendica and Hubzilla because they couldn't be bothered to open that link.

Mike saw this as a direct assault against Friendica and Hubzilla and an attempt at excluding both from "the Fediverse" which was almost entirely Mastodon at that point already. So he himself had to break the spec and make Hubzilla send Note-type objects instead so that Mastodon renders them at all. It still defaces them to this day.

(Friendica's solution was to send an Article-type object when a post has a title and a Note-type object when it doesn't have a title. Optionally, it can always send Note-type objects.)

By the way: This very same head-butting has returned. Not between Gargron and Mike, though, but between Gargron and much bigger players. Platforms like Flipboard and Ghost have introduced ActivityPub, and they send Article-type objects just as the ActivityPub spec demands. The same goes for WordPress. And, of course, they don't send plain-text "long tweets". They send fully formatted news articles and blog posts.

And now they demand Mastodon, as the biggest player in the Fediverse by user count, make their Article-type objects look just like they look at the source. They demand Mastodon not only render bold type, italics, headlines and the rest of the subset of text formatting that was introduced with Mastodon 4 in October, 2022. They also demand Mastodon show the titles and, most importantly, leave the images embedded within the articles in place, no matter how many they are.

This is no longer Gargron and his devs vs a guy in the Australian outback. This is Gargron and his devs who try hard to bend the Fediverse to their will and assume supreme control over it vs the Ghost Foundation, Flipboard, Inc. and Automattic, Inc. that play strictly by the ActivityPub rules. And I dare say that Automattic, Inc. alone has more money and more market power than Mastodon gGmbH and Mastodon, Inc. combined.

Mastodon has always gotten away with ignoring and breaking standards, re-inventing wheels and implying towards its religious followers that the whole Fediverse was built upon Mastodon and around Mastodon, and that everything that does things differently from Mastodon is inherently a broken add-on to Mastodon or an evil intruder. This time, they won't. And I guess they've actually taken it into consideration.

CC: @Tim Chambers @rakoo

# Long # LongPost # CWLong # CWLongPost # FediMeta # FediverseMeta # CWFediMeta # CWFediverseMeta # Fediverse # ActivityPub # Mastodon # Friendica # Hubzilla # WordPress # Ghost # Flipboard

⁂ Article

Rediscovering the Magic of the Blogosphere, with John O’Nolan and Matthias Pfefferle

Social networks were built on short posts designed for speed and scale. But what if the next era of the web was built for something deeper?

Two of the social web’s “longformers” are working on this. John O’Nolan, the founder and CEO of Ghost, and Matthias Pfefferle, the developer behind the ActivityPub plugin for WordPress, are at the forefront of integrating social features with blogs, newsletters, essays — anything that doesn’t fit in a box of 500 characters or less. 

In […]

Earlier today, @davew published a blog post titled WordPress and me. He talked about WordLand, his focused and fast editor for writers and bloggers. Through developing the editor, he’s discovered WordPress again.

WordPress as the OS of the open social web

I think WordPress has all that’s needed to be the OS of the open social web. We needed it and it’s always been there, and I saw something that I want to show everyone else, that the web can grow from here, we should build on everything that the WordPress community has created. It’s a lot stronger foundation that the other candidates for the basic needs of the open social web, imho.

@davew

I’ve been following Dave’s work with WordLand for the past few months, and it’s been really nice and encouraging to see him work on a product that aligns with my values. And now, Dave will get to present his tool and his ideas to others in the WordPress community! He will be talking at WordCamp Canada in October.

It should come as no surprise that someone so involved with some of the key concepts of the Open Web, like RSS, values ideals of openness and giving writers control over their content. WordLand’s approach to « what you see is what you get » is something that aligns so well with WordPress’ own ideals. It clashes with walled gardens like Twitter or Bluesky where you’re limited in length, format, content, and where you ultimately do not own your writing. It’s super motivating and empowering when someone newer to the WordPress ecosystem recognizes those shared values and the power of the platform.

Rediscovering WordPress

In his post, Dave talked about his journey of rediscovering WordPress through a new lens. The WordPress.com REST API, its endpoints and its authentication layer, gave him the tools to build the editor he needed, while still benefiting from everything the WordPress community has created in the past 22 years.

This is also what we had in mind when Automattic released Calypso 10 years ago:

Calypso is…

  • Incredibly fast. It’ll charm you.
  • Written purely in JavaScript, leveraging libraries like Node and React.
  • 100% API-powered. Those APIs are open, and now available to every developer in the world.

Matt — Dance to Calypso

Calypso and its underlying API paved the way for the first REST API endpoints that made it to WordPress itself a year later. That API then became a cornerstone of the Gutenberg project:

WordPress has always been about the user experience, and that needs to continue to evolve under newer demands. Gutenberg is an attempt at fundamentally addressing those needs, based on the idea of content blocks. It’s an attempt to improve how users interact with their content in a fundamentally visual way, while at the same time giving developers the tools to create more fulfilling experiences for the people they are helping.

Matías Ventura — Gutenberg, or the Ship of Theseus

WordPress.com REST API vs. WordPress REST API

On a more technical note, the folks more familiar with WordPress will wonder why WordLand uses the WordPress.com REST API, and not the core WordPress REST API.

Dave chose to use the WordPress.com API for WordLand — and that makes perfect sense for the goals of the project. It provides built-in authentication and opinionated endpoints that would otherwise need to be built on top of the core REST API, and would need to be shipped to every site that wants to use the WordLand editor. That’s simply not what WordLand was designed to do.

Perhaps more importantly, the WordPress.com REST API is just one of the many ways to interact with WordPress. That’s the beauty of WordPress: it’s open and flexible, allowing different tools and solutions to thrive. In this case, it’s nice to see how WordLand, WordPress, and WordPress.com came together to empower writers, each bringing their own strengths to the table. It’s a great example of how open tools and platforms can work hand-in-hand to create something truly special.

It’s always exciting to see new tools emerge from old foundations — and even more so when they help bring us closer to the open web we want to build. Funny enough, the WordPress.com REST API still relies on XML-RPC — a technology built by Dave 27 years ago 🙂

Go write something!

If you haven’t tried WordLand yet, go give it a try! All you need is a WordPress site, either hosted on WordPress.com or running the Jetpack plugin.

#Automattic #EN #OpenWeb #WCEH #WordLand #WordPress

A few days ago, @florianziegler suggested that all of us running blogs with RSS feeds make a small change:

Please add your email address to your RSS feed.

Add Your Email Address to Your RSS Feed

This email address can be used by RSS feed readers to display an Email button next to each feed entry, so folks can reply to the post via email instead of visiting the post on your site to leave a comment.

That seems like a good idea. I found that there was no WordPress plugin that allowed that out of the box, so I built my own. If you’re a blogger and use WordPress, give it a try!

https://wordpress.org/plugins/rss-reply-via-email/

Next step will be for more feed readers to support that issue. I consequently opened an issue for my feed reader of choice, NetNewsWire, to support this, and another for the Android app I use, FocusReader. If you use a different feed reader, don’t hesitate to contact them about it!

#EN #plugin #RSS #WordPress

⁂ Article

What we shipped so far in 2025

Alongside our upcoming plans, we’ve already shipped several important features in recent releases. Here are some highlights of what’s now available in the ActivityPub plugin.

Onboarding

We’ve added an onboarding flow after plugin activation to help guide new users through key decisions — such as selecting the Actor Mode.

It’s also a great opportunity to explain Fediverse concepts for users who are new to them.

More details:

👉 5.9.0 — Easier onboarding for your Fediverse […]

The Work Continues: What’s Next

Details will follow soon — but the work on events in the #Fediverse is far from complete. Key upcoming milestones include:

  • Improvements and new features for the Event Bridge for ActivityPubplugin for WordPress
    Continued development to maintain, fix issues, enhance, and expand functionality.
  • Work on Fediverse Enhancement Proposals (FEPs)
    Ensuring a robust final status of FEP-8a8e and focus on recurring and irregularly scheduled events.
  • Support for event interoperability in other Fediverse applications
    Contribute to other Fediverse applications and help them to explore and improve support for Event objects. For example, @linos@graz.social has outlined a potential roadmap for Mastodon.
  • Contribution to GatherPress
    Active involvement in the GatherPress project — a modern and truly FLOSS community oriented WordPress event plugin — to ensure full ActivityPub compatibility, including RSVP support and advanced federation features.
  • Community engagement and outreach
    Participation in conferences, public talks, and direct conversations to foster knowledge exchange, gather feedback, and grow the ecosystem around federated events.

Additional updates and technical details will be shared soon. Input, testing, and collaboration from interested parties are always welcome. Or if you know any conferences we should attend, let us know.

#ActivityPub #Events #Fediverse #FEP #GatherPress #WordPress

⁂ Article

New Look, Faster Blocks in ActivityPub 6.0.0

In this version of ActivityPub for WordPress, most blocks received a pretty fundamental overhaul of their technical infrastructure, design, and functionality.

The biggest change is almost invisible—all blocks now use WordPress’ Interactivity API under the hood, shedding a substantial amount of load-heavy scripts. On well-optimized sites, this should lead to noticeably quicker load times and improved web vitals.

Let’s dive in and look at each block individually.

Follow Me Block

After […]

⁂ Article

Our 2025 Roadmap: Building the Future of WordPress Federation

We’re excited to share this roadmap — there’s a lot happening with the ActivityPub plugin, and we can’t wait to show you what’s coming next.

We often refer to this roadmap in GitHub issues and discussions, but until now, we haven’t published a full roadmap post — nor a formal changelog. This post is a first step toward keeping the community more informed about what’s planned and what’s coming up next.

Our goal for this year is to finalize the full ActivityPub experience […]