Search results

0
0
0
0
0
0
0
0
0
0
0
0

7.9.0 — Spring Cleaning 🪣🧹

ActivityPub for WordPress @activitypub.blog@activitypub.blog

Version 7.9.0 is a spring-cleaning release for ActivityPub for WordPress. Custom Fediverse emoji now render properly, profile and following blocks make it easier to build richer identity pages, and new health checks improve reliability. Alongside performance tweaks and many fixes, this update focuses on polish, stability, and smoother everyday federation.

Read more →
0
0
1
洪 民憙 (Hong Minhee) :nonbinary: @hongminhee@hollo.social
Public

I have deeply mixed feelings about 's adoption of JSON-LD, as someone who's spent way too long dealing with it while building .

Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.

But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.

Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.

To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.

Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.

Doug Webb @douginamug@mastodon.xyz
Public

@hongminhee洪 民憙 (Hong Minhee) :nonbinary: I'm reading this thread as a relative noob, but what I see again and again: almost no one "properly" implents largely because is hard but also because the spec itself is unclear. Most people who get stuff done have to go off-spec to actually ship.

This seems a fundamental weakness of the - and that disregarding the limitations coming from base architecture. Seems to pose a mid/long-term existential threat.

What can we do to help improve things?

0
0
0

Funding Proposal: Open Media Network (#OMN) – Building Portable, Human-Centred Digital Commons

Hamish Campbell @info@hamishcampbell.com

https://nlnet.nl/fediversity Project Title Open Media Network (OMN): Portable Digital Commons for a Federated Europe Summary The Open Media Network (#OMN) is a real grassroots initiative to build sustainable, human-centred digital infrastructure aligned with the principles of the #openweb and the #4opens. To providing easy-to-use, hosted cloud services with service portability and freedom at their core - OMN focuses on creating living social ecosystems alongside technical […]

Read more →
0
0
1
Marcus "MajorLinux" Summers @majorlinux@toot.majorshouse.com
Public

I know this is going to be a hard lesson for people on the to learn, but here we go:

NOT EVERYONE ON THE FUCKING PLANET KNOWS HOW TO DO THE THINGS WE DO!

While I’ll take over , , and , some of y’all make it so difficult to just exist in a space without having to “well, actually” every fucking thing!

Understand that not everyone has all the answers (you sure as shit don’t) and treat people with some fucking grace and respect!

For fuck’s sake!

0
0
0
洪 民憙 (Hong Minhee) :nonbinary: @hongminhee@hollo.social
Public

I have deeply mixed feelings about 's adoption of JSON-LD, as someone who's spent way too long dealing with it while building .

Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.

But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.

Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.

To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.

Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.

2
25
1
marius @mariusor@metalhead.club
Public

I started adding support for services and it looks like it's easier than I imagined it initially.

On the server side, implementing the proxyURL handler doesn't need any new additions as it shares 90% code with other handlers that return objects.

On the client side, I'm creating a new http.RoundTripper that can use the proxyURL transparently for the caller.

As a developer in your client code you only do a regular request for a remote URL, and the round-tripper handles the proxying part transparently if it has all the available bits: a server that supports proxyURL and a valid OAuth2 session towards that server.

0
0
0
everton137 @everton137@vivaldi.net
Public

If decentralization is the future of social media, where millions or even billions of people share knowledge, then we can learn a lot from how the Open Knowledge Foundation (@okfnOpen Knowledge Foundation) and the Wikimedia Foundation (@wikimediafoundation) built cross-border, international movements with clear missions.

These two organizations are just two examples, but they demonstrate an important point: decentralization worked because communities were intentionally nurtured, not just because the technology was open.

The Fediverse, powered by the ActivityPub protocol, already has the technical capacity to thrive (UI tweaks aside).

What we still lack is the decentralization of communities, including shared ownership, coordination, and a mission that extends beyond individual instances.

Cc @eloquenceErik Moeller @bjoernstaBjörn Staschen @_elenaElena Rossini 📍 FOSDEM

0
0
0
0
0
0
everton137 @everton137@vivaldi.net
Public

Will Mastodon, the platform that keeps the alive, miss a strategic opportunity to bring official institutions on board at scale?

By watching how is being marketed compared to , it certainly seems that way.

I wish the folks at Mastodon would invest in more professional marketing, similar to what we're seeing from its rival, Bluesky.

There was a major meeting in the EU Parliament focused on this topic, yet there was no announcement or microblog post from Mastodon. Zero engagement.

Compare these two approaches:

fed.brid.gy/r/https://bsky.app

Sebastian (@seabass.bsky.social)

This author has chosen to make their posts visible only to people who are signed in.

bsky.app · Bluesky Social

0
0
0
0
0
0
Week in Fediverse :fediverse_light: @weekinfediverse@mitra.social
Public

Week in Fediverse 2026-02-06

Servers

- Gush v0.0.29
- PieFed v1.6.0
- Bookwyrm v0.8.4
- Mastodon v4.5.6
- Mitra v4.17.0
- Stegodon v1.7.0
- Hollo v0.7.1
- Wafrn v2026.02.01
- ActivityPub for WordPress v7.9.0
- Castopod v1.14.1
- Ktistec v3.2.9
- Wanderer v0.18.4
- Forgejo monthly report - January 2026
- Fedisky: ActivityPub extension for Bluesky PDS

Clients

- Tusky v32.0
- Fedilab v3.36.0
- Mangane 1.19.3
- Aria v1.4.2
- Phanpy changelog
- Coho: A fast, offline-first Mastodon client

Tools and Plugins

- Fedimap: An independent map for the Fediverse

Articles

- The best Mastodon client now has an iOS version!
- PkgFed: ActivityPub for Package Releases
- Statistics for Lemmy Instances and Communities

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019c10b9-e3f7-b6da-ef96-350864d2f791

Tak! (@Tak@gush.taks.garden)

[gush!](https://gush.social) [v0.0.29](https://codeberg.org/gush/gush/releases/tag/v0.0.29) is here! ### For users - Move poster header closer to content in replies and quotes (thanks @picklish !) - Fix federation of boosts of unlisted posts (thanks @picklish !) - Stream notifications to the notifications view (requires javascript) - Tune timeline queries for faster page loads - Don't show stale notification count in the notifications view - Update unread notification badge on other views when viewing the notifications view (requires javascript) - Fix rendering of polls with no deadline https://codeberg.org/gush/gush/issues/90 - Fix marking up hashtags in local notes when some hashtags are substrings of others https://codeberg.org/gush/gush/issues/88 - Don't fail actor import when the avatar url is malformed - Fix tooltip on report button in note footer - Fix reply badges sometimes being absent in timelines - The Ultimate Feature\* ### For admins - Move expired remote note cleanup to intermittent small batches when federated import service is idle, to reduce load spikes - Don't strip exif data from remote attachments - Update kotlin to 2.3.0 - Update ktor to 3.4.0 - Update logback to 1.5.25 - Update bouncycastle to 1.83 #gush

gush.taks.garden · gush.taks.garden

Link author: Tak!@Tak@gush.taks.garden

0
0
0
0
0
0
Jeff Sikes @box464@mastodon.social
Public

FediMTL, on the fedi at @info is a new 1-day fediverse related conference in Montreal in just a few weeks on February 24 (is it Fedi-conference season or something?)

There's a streaming option, too! And the sessions look good. Check it out, and spread the word.

fedimtl.ca/#about

FediMTL - A conference on digital sovereignty and the social web - February 24, 2026

FediMTL - Digital Sovereignty Conference

A Canadian conference on digital sovereignty and the social web - February 24, 2026 in Montreal

fedimtl.ca · FediMTL

0
0
0
0
0
0
Strypey @strypey@mastodon.nzoss.nz
Quiet public

(1/3)

@laurenshof
> W3C membership structure concentrates formal power ... while the implementers who could counterbalance that power have largely opted out of the process

My impression is that like a lot of things, this is caused by a combo of;

* lack of time and energy among projects devs, most of whom still work as volunteers

* the tense atmosphere that persists in many dev collaboration spaces, like SocialHub (not pointing the bone, I'm no saint, and I recognise I've contributed to this)

Strypey @strypey@mastodon.nzoss.nz
Public

(2/3)

My hope is that the chartering of a formal W3C Working Group to update ActivityPub will motivate devs to participate more in standards work. The promise of making concrete changes to the protocol specs might make it feel like less of a Boulder of Sisyphus. Plus, the prospect of working in a formally facilitated process, with fewer rubberneckers (like me), might mitigate any anxiety about discussions getting unpleasant.

0
0
0
0
0
0
Ricardo Ferrer Rivero🇪🇺 @ricferrer@mastodon.social
Public

It’s really surprising to me that the hasn’t agreed on a standardized way to open cross-instance objects and instead relies on links that open in the browser.

I found this proposal and what’s thinking… codeberg.org/fediverse/fep/src Which one would be your favorite?

(If anyone has updates on the progress, feel free to point me in the right direction)

Summary card of repository fediverse/fep, described as: Fediverse Enhancement Proposals

fep/fep/07d7/fep-07d7.md at main

fep - Fediverse Enhancement Proposals

codeberg.org · Codeberg.org

0
0
0
0
0
1
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social
Public

1/

RE: mastodon.social/@reiver/115945

Right now, Fediverse IDs resolve to HTTPS URLs.
For example, the Fediverse ID:

＠reiver＠mastodon.social

Resolves to HTTPS URL:

https;//mastodon·social/users/reiver

...

If we wanted cryptographic public-keys to serve as a basis of Identity on the Fediverse, then —

We would (similarly) also need a Fediverse ID to resolve to one or more cryptographic public-keys

...

@reiver ⊼ (Charles) :batman: (@reiver@mastodon.social)

Cryptographic public-keys are one way that one can have an identity (on the Fediverse, and elsewhere) while also having privacy — through a pseudonymous identity. Yes, we have Fediverse IDs such as: ＠joeblow＠example.com But a (non-delegated) public-key can function as a PORTABLE form of identity on the Fediverse. #ActivityPub #Cryptography #Fedidev #Fedidevs #Fediverse #JSONLD

mastodon.social · Mastodon

@reiver ⊼ (Charles) :batman: @reiver@mastodon.social
Public

2/

RE: mastodon.social/@reiver/115945

The resolving of a Fediverse ID to one or more cryptographic public-keys could happen via the activity-file for the user.

A JSON-LD namespace (separate from ActivityPub) could put the cryptographic public-keys into the activity-file.

But, I think we would need more information than what the 2 current methods for including cryptographic public-keys currently support.

@reiver ⊼ (Charles) :batman: (@reiver@mastodon.social)

Cryptographic public-keys are one way that one can have an identity (on the Fediverse, and elsewhere) while also having privacy — through a pseudonymous identity. Yes, we have Fediverse IDs such as: ＠joeblow＠example.com But a (non-delegated) public-key can function as a PORTABLE form of identity on the Fediverse. #ActivityPub #Cryptography #Fedidev #Fedidevs #Fediverse #JSONLD

mastodon.social · Mastodon

0
0
0
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social
Public

1/

RE: mastodon.social/@reiver/115945

Right now, Fediverse IDs resolve to HTTPS URLs.
For example, the Fediverse ID:

＠reiver＠mastodon.social

Resolves to HTTPS URL:

https;//mastodon·social/users/reiver

...

If we wanted cryptographic public-keys to serve as a basis of Identity on the Fediverse, then —

We would (similarly) also need a Fediverse ID to resolve to one or more cryptographic public-keys

...

@reiver ⊼ (Charles) :batman: (@reiver@mastodon.social)

Cryptographic public-keys are one way that one can have an identity (on the Fediverse, and elsewhere) while also having privacy — through a pseudonymous identity. Yes, we have Fediverse IDs such as: ＠joeblow＠example.com But a (non-delegated) public-key can function as a PORTABLE form of identity on the Fediverse. #ActivityPub #Cryptography #Fedidev #Fedidevs #Fediverse #JSONLD

mastodon.social · Mastodon

0
0
0
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social
Public

I dream of being able to store my online social presence, identity, and history just as — an (organized) set of static files.

A set that I control.

And, I can (if I want to) host myself. (I.e., I am the "source of truth" / "origin" for my files.)

RE: mastodon.social/@reiver/116018

@reiver ⊼ (Charles) :batman: (@reiver@mastodon.social)

3/ If you cannot get (most) regular people to write JSON-LD, JSON, or even HTML — But, you might be able to get them (regular people) to write something similar to Markdown and INI — Then, are there ways you could (explicitly or implicitly) encode JSON-LD type information, such as ActivityPub, into a Markdown-like to INI-like file — in a way where they (regular people) would likely include it? I suspect — probably yes. #ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX

mastodon.social · Mastodon

0
0
0
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social
Public

2/

I spend time thinking about how this (the importance of files and file data-formats) intersects with user-experience (UX).

For example, what types of files could you get regular people to create?

I don't think you can get regular people en masse to write JSON (including JSON-LD).

I think even getting them (regular people) to write HTML is difficult.

Something similar to Markdown probably has the best chance or success. Maybe something similar to INI, too.

@reiver ⊼ (Charles) :batman: @reiver@mastodon.social
Public

3/

If you cannot get (most) regular people to write JSON-LD, JSON, or even HTML —

But, you might be able to get them (regular people) to write something similar to Markdown and INI —

Then, are there ways you could (explicitly or implicitly) encode JSON-LD type information, such as ActivityPub, into a Markdown-like or INI-like file — in a way where they (regular people) would likely include it?

I suspect — probably yes.

0
0
0
GENKI @nibushibu@vivaldi.net
Public

勝手にプレビュー版のアプリみたいなのをインストールしないといけないんだと勘違いしてたけど Web から見られるようになってて嬉しい。
:mastodon: で言うところの Boost みたいなことはまだできないのかな？

0
0
0
0
0
0
0
0
0
0
0
0
kopper :colon_three: @kopper@not-brain.d.on-t.work
Public
this is shaping up well enough that i think i can can Post about it now:

working on an activitypub-aware reverse proxy to handle http signatures/authorized fetch (and, in the future, caching, though that's not there yet) on your behalf. primarily intended to absorb the load of large federation bursts for the underlying software, but also frees you from having to reimplement http signature validation yourself

supports both rsa-sha256 and ed25519 over the cavage draft. handles multiple keys per actor. will handle blind key rotations whenever i get around to it. may add support for the the new http signature rfc if there's a Reasonable library available

i have a few more things in mind but i need to finish the basics first
0
1
0
0
0
0
inventaire.io @inventaire@mamot.fr
Public

users and entities activities can now be followed from the !

Some examples of followable actors:
- a user: @Georges
- an author: @wd-Q46248Terry Pratchett
- a serie: @inv-083c773e8b26776230e40657fdfadeb9Temps Critiques
- a publisher: @wd-Q3213929La Volte
- a publisher collection: @inv-582c0644d0a9c06d4758deb86d49ff1e

This is the result of our first experiments with : let us know if you find it useful!

Learn more: wiki.inventaire.io/wiki/What_i

Fediverse - InventaireWiki

wiki.inventaire.io

0
0
0
marius @mariusor@metalhead.club
Public

Speaking of , I can't wait for the Sanitizer DOM API to start making an appearance in mainstream browsers later this month.

Currently the biggest chunk of the 140K that make the JavaScript application that comprises ONI is composed of the dompurify library I'm using now to do sanitization of NaturalLanguageValues in objects.

0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
2
0