# orderedItems[].object.content
Flohmarkt is a free open platform for small ads and selling things ("Flohmarkt" is the German for flea market). It's part of the Fediverse so the small ads can federate to other servers, and people can interact with Flohmarkt from Mastodon etc accounts.

If you want to post or browse adverts there is a server list:

🌱 https://codeberg.org/flohmarkt/flohmar kt/wiki/flohmarkt-instances

There is techy info on their Codeberg page:

🌱 https://codeberg.org/flohmarkt/flohmar kt

You can follow their lead dev's account at:

🌱 @grindhold

#Fediverse #ActivityPub

# orderedItems[].object.ephemeral.metadata[].description
flohmarkt - federated decentral classified ad software using activitypub

# orderedItems[].object.ephemeral.metadata[].ogDescription
federated decentral classified ad software using activitypub

# orderedItems[].object.ephemeral.metadata[].description
flohmarkt - federated decentral classified ad software using activitypub

# orderedItems[].object.ephemeral.metadata[].ogDescription
federated decentral classified ad software using activitypub

# orderedItems[].object.content
I absolutely love @itchio@mastodon.social . It's the best way to find new and interesting games.

I see that #Itch has links to different socials.

I wonder how difficult it would be, should they be interested, in actually implementing #ActivityPub inside of Itch?

This would allow software developers to just use Itch as their platform to post their games and communicate with others.

Itch already supports a comments section. Configuring AP anyone anywhere in the world could the comment on a game as well.

We could follow a developer from our open socials and when a developers posts a comment or posts a game, we'd get it everywhere.

Just thinking this would be really interesting idea. I don't know how much work or how feasible it would be, but it'd support developers, it'd support Itch ( by allowing folks on the Fediverse anywhere to follow and know that it's only Itch that you can do this on) and it'd support the wider Fediverse as we whole.

Love to hear thoughts, comments, suggestions, and even if it's just a silly idea that isn't really practical.

# orderedItems[].object.source.content
I absolutely love [@itchio@mastodon.social](https://mastodon.social/users/itchio) . It's the best way to find new and interesting games.

I see that [#Itch](https://btfree.social/hashtag/Itch) has links to different socials.

I wonder how difficult it would be, should they be interested, in actually implementing [#ActivityPub](https://btfree.social/hashtag/ActivityPub) inside of Itch?

This would allow software developers to just use Itch as their platform to post their games and communicate with others.

Itch already supports a comments section. Configuring AP anyone anywhere in the world could the comment on a game as well.

We could follow a developer from our open socials and when a developers posts a comment or posts a game, we'd get it everywhere.

Just thinking this would be really interesting idea. I don't know how much work or how feasible it would be, but it'd support developers, it'd support Itch ( by allowing folks on the Fediverse anywhere to follow and know that it's only Itch that you can do this on) and it'd support the wider Fediverse as we whole.

Love to hear thoughts, comments, suggestions, and even if it's just a silly idea that isn't really practical.

# orderedItems[].object.ephemeral.metadata[].description
24 Posts, 6 Following, 169 Followers · Open indie game marketplace and DIY game jam host Account support? Email support@itch.io

# orderedItems[].object.ephemeral.metadata[].ogDescription
24 Posts, 6 Following, 169 Followers · Open indie game marketplace and DIY game jam host Account support? Email support@itch.io

# orderedItems[].object.content
Seeing how EU uses Absent==Yes as trick to pass #Chatcontrol 1.0 shows we need 100% tranparent and scanned communication of politicans working in the EU.

Furthermore as I mentioned earlier there is massive need for #Tor based #SocialMedia and #Messenger based on #Activitypub and #Matrix .

Based on #Tor #Hidden #Services #Onion addressess, everybody is able to run the instance on his own device(s).

And for the view ones having lots of contacts a pc at home will mostly work to let it run

# orderedItems[].object.content
It took a while, but Shoot now has a role editor (among other guild settings)!

Roles and permissions have been implemented server-side nearly since the beginning but they haven't been available in the client until now.

The UI/UX here is very similar to how Discord's permissions used to work. Roles can be assigned to users and they are evaluated from bottom to top in the role list. Roles can deny or allow permissions, with lower roles in the list being overridden by higher roles. In the screenshots guild, the 'everyone' role allows 'Send Messages' permission, but the 'muted' role denies it. If someone has the 'muted' role, it will override the send messages permission from the 'everyone'/default role and prevent them from speaking.

It's still a bit rough of course, but I'm still having a good time working on the project.

You can try it out yourself/learn more at https://shoot.pub using the registration token `0K2A3` which expires in a week. That's just for anti-spam reasons, let me know if you want to register if it doesn't work :)

#shootpub #activitypub #fedidev

# orderedItems[].object.attachment[].name
The role editor in Shoot. There are 3 roles shown, "moderator", "muted", and finally "everyone" which is selected. The editor shows the default permissions given to everyone which include: send messages, view channel, call channel, create invite, and upload permissions.

# orderedItems[].object.content
#HolosDiscover is a search engine dedicated to the #Fediverse. It does not scrape content, because it speaks #ActivityPub and respects each user's choice to opt in or out.
The most respectful alternative, open to all and full of content to explore.

https://discover.holos.social

# orderedItems[].object.attachment[].name
HolosDiscover Overview stats:
13.9M posts indexed
3.2M posts deleted
492K posts updated
70K users followed
2.8K opted out
7.1K instances known

# orderedItems[].object.ephemeral.metadata[].description
A privacy-respecting search engine for Mastodon, Pleroma, Misskey and the Fediverse.

# orderedItems[].object.ephemeral.metadata[].ogDescription
A privacy-respecting search engine for Mastodon, Pleroma, Misskey and the Fediverse.

# orderedItems[].object.ephemeral.metadata[].twitterDescription
A privacy-respecting search engine for Mastodon, Pleroma, Misskey and the Fediverse.

# orderedItems[].object.name
NodeBB v4.14.0 — Federation regression fixes, security fixes, and more!

# orderedItems[].object.summary
With temperatures reaching well into the 30s (in celsius of course :sunglasses:) in the Toronto area, we're all firmly in summer mode :swimmer: :beach_with_umbrella: , but that won't stop us from forging on ahead with new features and fixes for NodeBB!

There are improvements across ActivityPub federation, administrative tooling, and security hardening. Our ActivityPub integration receives bug fixes including duplicate handling, configurable rate limiting, and better error reporting, alongside new hooks for remote user lifecycle events. The registration queue and invitations are reorganized into a dedicated UI with a new "Reject All" bulk action and improved notification handling. Security reports have been coming in consistently throughout the month with valid security reports (though almost all AI discovered and generated). This led to stricter privilege checks on post diffs, crossposts, and GDPR exports, plus protection against username enumeration. The NodeBB team strongly encourages upgrading to v4.14.0 for the latest security fixes and federation improvements. The release also includes a new tx() translation helper, Benchpress escaping improvements, and a first-run categories onboarding modal for fresh installations.

Here are the high level changes you can expect to see when you upgrade from v4.13.0 to v4.14.0... [...]

# orderedItems[].object.content
With temperatures reaching well into the 30s (in celsius of course :sunglasses:) in the Toronto area, we're all firmly in summer mode :swimmer: :beach_with_umbrella: , but that won't stop us from forging on ahead with new features and fixes for NodeBB!

There are improvements across ActivityPub federation, administrative tooling, and security hardening. Our ActivityPub integration receives bug fixes including duplicate handling, configurable rate limiting, and better error reporting, alongside new hooks for remote user lifecycle events. The registration queue and invitations are reorganized into a dedicated UI with a new "Reject All" bulk action and improved notification handling. Security reports have been coming in consistently throughout the month with valid security reports (though almost all AI discovered and generated). This led to stricter privilege checks on post diffs, crossposts, and GDPR exports, plus protection against username enumeration. The NodeBB team strongly encourages upgrading to v4.14.0 for the latest security fixes and federation improvements. The release also includes a new tx() translation helper, Benchpress escaping improvements, and a first-run categories onboarding modal for fresh installations.

Here are the high level changes you can expect to see when you upgrade from v4.13.0 to v4.14.0... [...]

:globe_with_meridians: Federation Regression Fixes!

Around v4.12.0 or so, a number of regressions were unintentionally introduced as part of security fixes that severely hampered federation — especially with Lemmy-based instances and relays. We've resolved those regressions and Relay/Lemmy federation should resume within 24 hours after upgrading.

The public key fetch rate limiter logic was simplified and updated (due to it being faulty and not really working in the first place), streamlined some duplicate logic with Like/Dislike activities, improved the AP Errors reporting page in the ACP, added a parent traversal depth guard, fixed an issue where updates to scheduled topics were accidentally being federated out, and about a hundred other smaller bugs :slightly_smiling_face:

:ballot_box_with_check: Registration Queue updates

The registration queue was moved out of the ACP, and invitations are also managed in this page now. A "reject all" button was added to allow admins to quickly reject every queued registrant in one fell swoop.

🔒 Privilege & Security Fixes

Post diff access — Check topics:read privilege when loading post diffs

Crossposts — Added source category privilege check to crossposts

GDPR export — Prevented global moderators from performing GDPR data exports

Nids ownership — Don't mark nids as read/unread that you don't own

Upload privileges — Prevent uploading thumbnails without upload:image privilege; replaced extension-based MIME validation with content
sniffing

Username enumeration — Use dummy lockout key for non-existent users to prevent enumeration

Category disabled flag — Check category disabled flag on getRaw

:interrobang: Benchpress Improvements

We use Benchpress as our templating engine. We updated our integration for security and performance. @baris put together a thorough write-up for that one here.

Miscellaneous

First-run modal — New categories onboarding modal for fresh installations

Dashboard warnings — Added localhost and URL mismatch warnings to admin dashboard notices

Push notifications should work on Safari/iOS devices now (via the web-push plugin)

# orderedItems[].object.source.content
With temperatures reaching well into the 30s (in celsius of course :sunglasses:) in the Toronto area, we're all firmly in summer mode :swimmer: :beach_with_umbrella: , but that won't stop us from forging on ahead with new features and fixes for NodeBB!

There are improvements across ActivityPub federation, administrative tooling, and security hardening. Our ActivityPub integration receives bug fixes including duplicate handling, configurable rate limiting, and better error reporting, alongside new hooks for remote user lifecycle events. The registration queue and invitations are reorganized into a dedicated UI with a new "Reject All" bulk action and improved notification handling. Security reports have been coming in consistently throughout the month with valid security reports (though almost all AI discovered and generated). This led to stricter privilege checks on post diffs, crossposts, and GDPR exports, plus protection against username enumeration. **The NodeBB team strongly encourages upgrading to v4.14.0 for the latest security fixes and federation improvements**. The release also includes a new `tx()` translation helper, Benchpress escaping improvements, and a first-run categories onboarding modal for fresh installations.

Here are the high level changes you can expect to see when you upgrade from v4.13.0 to v4.14.0... 

## :globe_with_meridians: Federation Regression Fixes!

Around v4.12.0 or so, a number of regressions were unintentionally introduced as part of security fixes that severely hampered federation — especially with Lemmy-based instances and relays. We've resolved those regressions and Relay/Lemmy federation should resume within 24 hours after upgrading.

The public key fetch rate limiter logic was simplified and updated (due to it being faulty and not really working in the first place), streamlined some duplicate logic with Like/Dislike activities, improved the AP Errors reporting page in the ACP, added a parent traversal depth guard, fixed an issue where updates to scheduled topics were accidentally being federated out, and about a hundred other smaller bugs :)

## :ballot_box_with_check: Registration Queue updates

The registration queue was moved out of the ACP, and invitations are also managed in this page now. A "reject all" button was added to allow admins to quickly reject every queued registrant in one fell swoop. 

 ## 🔒 Privilege & Security Fixes                                                                                                          
                                                                                                                                            
 - Post diff access — Check topics:read privilege when loading post diffs                                                                   
 - Crossposts — Added source category privilege check to crossposts                                                                         
 - GDPR export — Prevented global moderators from performing GDPR data exports                                                              
 - Nids ownership — Don't mark nids as read/unread that you don't own                                                                       
 - Upload privileges — Prevent uploading thumbnails without upload:image privilege; replaced extension-based MIME validation with content   
 sniffing                                                                                                                                   
 - Username enumeration — Use dummy lockout key for non-existent users to prevent enumeration                                               
 - Category disabled flag — Check category disabled flag on getRaw 

## :interrobang: Benchpress Improvements

We use Benchpress as our templating engine. We updated our integration for security and performance. [[@baris](https://community.nodebb.org/user/baris) put together a thorough write-up for that one here](https://community.nodebb.org/topic/19364/upcoming-breaking-changes-for-4.14.0).

## Miscellaneous

 - First-run modal — New categories onboarding modal for fresh installations                                                                
 - Dashboard warnings — Added localhost and URL mismatch warnings to admin dashboard notices                                                
 - Push notifications should work on Safari/iOS devices now (via the web-push plugin)

# orderedItems[].object.preview.content
With temperatures reaching well into the 30s (in celsius of course :sunglasses:) in the Toronto area, we're all firmly in summer mode :swimmer: :beach_with_umbrella: , but that won't stop us from forging on ahead with new features and fixes for NodeBB!

There are improvements across ActivityPub federation, administrative tooling, and security hardening. Our ActivityPub integration receives bug fixes including duplicate handling, configurable rate limiting, and better error reporting, alongside new hooks for remote user lifecycle events. The registration queue and invitations are reorganized into a dedicated UI with a new "Reject All" bulk action and improved notification handling. Security reports have been coming in consistently throughout the month with valid security reports (though almost all AI discovered and generated). This led to stricter privilege checks on post diffs, crossposts, and GDPR exports, plus protection against username enumeration. The NodeBB team strongly encourages upgrading to v4.14.0 for the latest security fixes and federation improvements. The release also includes a new tx() translation helper, Benchpress escaping improvements, and a first-run categories onboarding modal for fresh installations.

Here are the high level changes you can expect to see when you upgrade from v4.13.0 to v4.14.0... [...]

:globe_with_meridians: Federation Regression Fixes!

Around v4.12.0 or so, a number of regressions were unintentionally introduced as part of security fixes that severely hampered federation — especially with Lemmy-based instances and relays. We've resolved those regressions and Relay/Lemmy federation should resume within 24 hours after upgrading.

The public key fetch rate limiter logic was simplified and updated (due to it being faulty and not really working in the first place), streamlined some duplicate logic with Like/Dislike activities, improved the AP Errors reporting page in the ACP, added a parent traversal depth guard, fixed an issue where updates to scheduled topics were accidentally being federated out, and about a hundred other smaller bugs :)

:ballot_box_with_check: Registration Queue updates

The registration queue was moved out of the ACP, and invitations are also managed in this page now. A "reject all" button was added to allow admins to quickly reject every queued registrant in one fell swoop.

🔒 Privilege & Security Fixes

Post diff access — Check topics:read privilege when loading post diffs

Crossposts — Added source category privilege check to crossposts

GDPR export — Prevented global moderators from performing GDPR data exports

Nids ownership — Don't mark nids as read/unread that you don't own

Upload privileges — Prevent uploading thumbnails without upload:image privilege; replaced extension-based MIME validation with content
sniffing

Username enumeration — Use dummy lockout key for non-existent users to prevent enumeration

Category disabled flag — Check category disabled flag on getRaw

:interrobang: Benchpress Improvements

We use Benchpress as our templating engine. We updated our integration for security and performance. @baris put together a thorough write-up for that one here.

Miscellaneous

First-run modal — New categories onboarding modal for fresh installations

Dashboard warnings — Added localhost and URL mismatch warnings to admin dashboard notices

Push notifications should work on Safari/iOS devices now (via the web-push plugin)

# orderedItems[].object.content
RE: https://mediaformat.org/2026/07/nuages-says-hello/

Announcing it here publicly for the first time!

I've been building a general purpose activitypub pwa.

Follow @nuages for official updates!

#activityPubAPI #ActivityPub

# orderedItems[].object.content
An article can be made directly boostable with #ActivityPub. I call it #APnative and WordPress and Ghost already allow us to publish that way. I desperately want this to happen with podcasts too. Perhaps such that we use AP in addition or instead of RSS as the base of the format.

Can content that works with #ATproto live outside of a PDS? (I'm not sure I'm even asking the question correctly)

cc @mackuba

# orderedItems[].object.content
Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse
#activitypub #ActivityPubAPI #c2s #fediverse

# orderedItems[].object.ephemeral.metadata[].description
Do you yearn for a user powered social network? A social space free from constant Ads, Sponsored and AI generated slop? The Fediverse 1 is a network where you c

# orderedItems[].object.ephemeral.metadata[].ogDescription
Do you yearn for a user powered social network? A social space free from constant Ads, Sponsored and AI generated slop? The Fediverse 1 is a network where you c

# orderedItems[].object.content
The ActivityPub API doesn't define a way to get all server known posts with a specific tag.

There are a few ways this could be done in an ActivityPub client

What behaviour would you prefer when clicking on a post Tag link?

(Any other ideas, comment)
#ActivityPub #c2s #activityPubAPI

# orderedItems[].object.content
#ActivityPub over #ATProto 👀

https://berjon.com/ap-at

# orderedItems[].object.ephemeral.metadata[].ogDescription
Thought experiment: how hard would it be to implement ActivityPub over ATProto? The answer might surprise you!

# orderedItems[].object.ephemeral.metadata[].twitterDescription
Thought experiment: how hard would it be to implement ActivityPub over ATProto? The answer might surprise you!

# orderedItems[].object.content
Week in Fediverse 2026-07-10

Servers

- Betula v1.8.1
- Stegodon v1.8.6
- Ktistec v3.8.0
- Mitra v5.7.0
- Ibis v0.3.3
- Gathio v1.6.3
- NodeBB v4.14.0
- Wanderer v0.20.0
- Wafrn v2026.07.01
- Gush! v0.0.40
- PieFed v1.7.5
- Harmony v1.4.0

Clients

- Mastodon for iOS v2026.05
- tooi v0.27.0
- Voyager v2.47.4
- Aria v1.5.7
- Holos v1.14.0
- Rocinante v1.1.0
- chan-fe: Imageboard-style frontend for Mitra and Mastodon-compatible fediverse APIs

Tools and Plugins

- tag-federation.online: How Widely Do Hashtags Federate?
- Fedigraph: A dashboard for exploring the fediverse

For developers

- BotKit v0.5.0

Protocol

- FEP-4772: Representing bookmarks
- FEP-521b: Switch the default in FEP-521a to be 76171% cooler

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019f29a4-78da-7a53-805d-72c8e43916c2

# orderedItems[].object.ephemeral.metadata[].description
Blog directly from ssh! Contribute to deemkeen/stegodon development by creating an account on GitHub.

# orderedItems[].object.ephemeral.metadata[].ogDescription
stegodon v1.8.6
SSH-first federated blogging platform with ActivityPub support.
Installation
Download the appropriate binary for your system:

Linux AMD64: stegodon_1.8.6_Linux_x86_64.tar.gz
Linux ...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
stegodon v1.8.6
SSH-first federated blogging platform with ActivityPub support.
Installation
Download the appropriate binary for your system:

Linux AMD64: stegodon_1.8.6_Linux_x86_64.tar.gz
Linux ...

# orderedItems[].object.ephemeral.metadata[].ogDescription
There are two significant new additions in release v3.8.0 of ktistec.
First, the actor cards on the followed/following pages show relevant actor status. O…

# orderedItems[].object.ephemeral.metadata[].twitterDescription
There are two significant new additions in release v3.8.0 of ktistec.
First, the actor cards on the followed/following pages show relevant actor status. O…

# orderedItems[].object.ephemeral.metadata[].description
Ibis is a federated encyclopedia with numerous features
[https://github.com/Nutomic/ibis?tab=readme-ov-file#features]. If you want to
start a wiki for a TV series, a videogame, or an open source project then Ibis
is for you! You can register on an existing instance [https://ibis.wiki/explore]
or install it on your own server [https://ibis.wiki/article/Setup_Instructions].
Then you can start editing on the topic of your choice, and connect to other
Ibis instances for different topics. Federation ensures that articles get
mirrored across many servers, and can be read even if the original instance goes
down. Ibis is written in Rust and Webassembly, fully open source to make
enshittification impossible. — This version includes some minor bug fixes and
improvements, plus updated translations. Changelog: - Use jemalloc on x86 to
reduce RAM usage - Properly render international domain names - Remove markdown
max_width and fixed_indent - Allow parenthesis in article title - Update
Dockerfile Debian version - Show emoji indicator for dead instances — If you are
interested what a federated wiki can do, join and give it a try. You can
register on ibis.wiki [https://ibis.wiki/], open.ibis.wiki
[https://open.ibis.wiki/] or other instances [https://ibis.wiki/explore]. You
can also install Ibis on your own server. It is very lightweight and can easily
run on an existing server alongside other software. This release includes an
additional installation method using Docker
[https://ibis.wiki/article/Setup_Instructions#docker-installation]. To discuss
the project, report problems or get support use the following links: Lemmy
[https://lemmyverse.link/c/ibis@lemmy.ml] | Matrix
[https://matrix.to/#/#ibis:matrix.org] | Github
[https://github.com/Nutomic/ibis]

# orderedItems[].object.ephemeral.metadata[].ogDescription
Ibis is a federated encyclopedia with numerous features
[https://github.com/Nutomic/ibis?tab=readme-ov-file#features]. If you want to
start a wiki for a TV series, a videogame, or an open source project then Ibis
is for you! You can register on an existing instance [https://ibis.wiki/explore]
or install it on your own server [https://ibis.wiki/article/Setup_Instructions].
Then you can start editing on the topic of your choice, and connect to other
Ibis instances for different topics. Federation ensures that articles get
mirrored across many servers, and can be read even if the original instance goes
down. Ibis is written in Rust and Webassembly, fully open source to make
enshittification impossible. — This version includes some minor bug fixes and
improvements, plus updated translations. Changelog: - Use jemalloc on x86 to
reduce RAM usage - Properly render international domain names - Remove markdown
max_width and fixed_indent - Allow parenthesis in article title - Update
Dockerfile Debian version - Show emoji indicator for dead instances — If you are
interested what a federated wiki can do, join and give it a try. You can
register on ibis.wiki [https://ibis.wiki/], open.ibis.wiki
[https://open.ibis.wiki/] or other instances [https://ibis.wiki/explore]. You
can also install Ibis on your own server. It is very lightweight and can easily
run on an existing server alongside other software. This release includes an
additional installation method using Docker
[https://ibis.wiki/article/Setup_Instructions#docker-installation]. To discuss
the project, report problems or get support use the following links: Lemmy
[https://lemmyverse.link/c/ibis@lemmy.ml] | Matrix
[https://matrix.to/#/#ibis:matrix.org] | Github
[https://github.com/Nutomic/ibis]

# orderedItems[].object.ephemeral.metadata[].twitterDescription
Ibis is a federated encyclopedia with numerous features
[https://github.com/Nutomic/ibis?tab=readme-ov-file#features]. If you want to
start a wiki for a TV series, a videogame, or an open source project then Ibis
is for you! You can register on an existing instance [https://ibis.wiki/explore]
or install it on your own server [https://ibis.wiki/article/Setup_Instructions].
Then you can start editing on the topic of your choice, and connect to other
Ibis instances for different topics. Federation ensures that articles get
mirrored across many servers, and can be read even if the original instance goes
down. Ibis is written in Rust and Webassembly, fully open source to make
enshittification impossible. — This version includes some minor bug fixes and
improvements, plus updated translations. Changelog: - Use jemalloc on x86 to
reduce RAM usage - Properly render international domain names - Remove markdown
max_width and fixed_indent - Allow parenthesis in article title - Update
Dockerfile Debian version - Show emoji indicator for dead instances — If you are
interested what a federated wiki can do, join and give it a try. You can
register on ibis.wiki [https://ibis.wiki/], open.ibis.wiki
[https://open.ibis.wiki/] or other instances [https://ibis.wiki/explore]. You
can also install Ibis on your own server. It is very lightweight and can easily
run on an existing server alongside other software. This release includes an
additional installation method using Docker
[https://ibis.wiki/article/Setup_Instructions#docker-installation]. To discuss
the project, report problems or get support use the following links: Lemmy
[https://lemmyverse.link/c/ibis@lemmy.ml] | Matrix
[https://matrix.to/#/#ibis:matrix.org] | Github
[https://github.com/Nutomic/ibis]

# orderedItems[].object.ephemeral.metadata[].description
Self-destructing, shareable, no-registration event pages - Release v1.6.3 · lowercasename/gathio

# orderedItems[].object.ephemeral.metadata[].ogDescription
What's Changed

fix: Stable UID in iCal export by @ellieayla in #246
Code mod (written by copilot) to convert all then/catch to await/async by @halkeye in #244
fix(#247): add configurable max comme...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
What's Changed

fix: Stable UID in iCal export by @ellieayla in #246
Code mod (written by copilot) to convert all then/catch to await/async by @halkeye in #244
fix(#247): add configurable max c...

# orderedItems[].object.ephemeral.metadata[].description
Node.js based forum software built for the modern web - Release v4.14.0 · NodeBB/NodeBB

# orderedItems[].object.ephemeral.metadata[].ogDescription
Release build (minor) of NodeBB @ 2026-07-09T12:41:51.241Z
v4.14.0 (2026-07-09)
New Features

categories:  add first-run modal for new installations (19e25f2)
admin:  add localhost and URL mismatch...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
Release build (minor) of NodeBB @ 2026-07-09T12:41:51.241Z
v4.14.0 (2026-07-09)
New Features

categories:  add first-run modal for new installations (19e25f2)
admin:  add localhost and URL mismatch...

# orderedItems[].object.ephemeral.metadata[].description
wanderer is a self-hosted trail database. Save your adventures! - Release v0.20.0 · open-wanderer/wanderer

# orderedItems[].object.ephemeral.metadata[].ogDescription
v0.20.0
Breaking Changes
CautionWith this update we introduce a new plugin system: integrations (Strava, Komoot, Hammerhead) now run as sandboxed WASM plugins, providing the foundation for third-pa...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
v0.20.0
Breaking Changes
CautionWith this update we introduce a new plugin system: integrations (Strava, Komoot, Hammerhead) now run as sandboxed WASM plugins, providing the foundation for third-pa...

# orderedItems[].object.ephemeral.metadata[].description
Federated social app: Discord-style servers and chat with ActivityPub. Vue 3 + Supabase + Tauri. - Release v1.4.0 · y4my4my4m/harmony

# orderedItems[].object.ephemeral.metadata[].ogDescription
What's Changed

Chore/professionalize by @y4my4my4m in #63
Videochat rework by @y4my4my4m in #64
Tauri implementation by @y4my4my4m in #65

Full Changelog: v1.3.1...v1.4.0

# orderedItems[].object.ephemeral.metadata[].twitterDescription
What's Changed

Chore/professionalize by @y4my4my4m in #63
Videochat rework by @y4my4my4m in #64
Tauri implementation by @y4my4my4m in #65

Full Changelog: v1.3.1...v1.4.0

# orderedItems[].object.ephemeral.metadata[].description
Official iOS app for Mastodon. Contribute to mastodon/mastodon-ios development by creating an account on GitHub.

# orderedItems[].object.ephemeral.metadata[].ogDescription
Some small but important bug fixes:

Restores the ability to change your avatar and banner images.
Shows a collection attached to a post only once, rather than as a collection and as a link preview...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
Some small but important bug fixes:

Restores the ability to change your avatar and banner images.
Shows a collection attached to a post only once, rather than as a collection and as a link preview...

# orderedItems[].object.ephemeral.metadata[].description
Voyager — a beautiful app for Lemmy and Piefed. Contribute to aeharding/voyager development by creating an account on GitHub.

# orderedItems[].object.ephemeral.metadata[].ogDescription
🐛 Fixes

fix: sort communities list by handle instead of API order

PR: #2303


fix: focus rich text editor on account switch

PR: #2305


fix: restore rich text editor cursor position on focus

PR...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
🐛 Fixes

fix: sort communities list by handle instead of API order

PR: #2303


fix: focus rich text editor on account switch

PR: #2305


fix: restore rich text editor cursor position on focus

PR...

# orderedItems[].object.ephemeral.metadata[].description
A cross-platform Misskey client built with Flutter - Release v1.5.7 · poppingmoon/aria

# orderedItems[].object.ephemeral.metadata[].ogDescription
What's Changed

fix: set tag for Android notification by @poppingmoon in #948
perf: reduce BlurHash resolution for user avatar by @poppingmoon in #949
fix: count AiScript UI component update by @po...

# orderedItems[].object.ephemeral.metadata[].twitterDescription
What's Changed

fix: set tag for Android notification by @poppingmoon in #948
perf: reduce BlurHash resolution for user avatar by @poppingmoon in #949
fix: count AiScript UI component update by...

# orderedItems[].object.ephemeral.metadata[].description
chan-fe - Image board style fedi front end with a emphasis on gallery view

# orderedItems[].object.ephemeral.metadata[].ogDescription
Image board style fedi front end with a emphasis on gallery view

# orderedItems[].object.ephemeral.metadata[].description
See how far a Mastodon hashtag spreads: compare how many tagged posts different servers can actually see.

# orderedItems[].object.ephemeral.metadata[].ogDescription
See how far a Mastodon hashtag spreads: compare how many tagged posts different servers can actually see.

# orderedItems[].object.ephemeral.metadata[].description
fedigraph - Data visualization and information for the fediverse.

# orderedItems[].object.ephemeral.metadata[].ogDescription
Data visualization and information for the fediverse.

# orderedItems[].object.ephemeral.metadata[].ogDescription
BotKit 0.5.0 introduces significant updates to the framework, headlined by the ability to host multiple bots from a single process through a new multi-bot instance architecture. This release brings a visual overhaul to both the documentation site and the automatically generated bot pages, replacing external dependencies with a self-contained, customizable design system that improves visitor privacy. A major technical addition is the support for FEP-044f, which implements a consent-based handshake for quoting messages to ensure better compatibility with Mastodon’s quoting mechanisms. Developers can now utilize a new Redis-backed repository for shared production environments, complementing existing storage options with robust concurrency handling through short-lived locks. The update includes breaking changes for custom repository implementations and shifts bot sessions to a read-only model to support lazy resolution of bot identities. These enhancements provide developers with greater flexibility in deploying complex bot fleets while maintaining high standards for privacy and Fediverse interoperability.

# orderedItems[].object.ephemeral.metadata[].ogTitle
BotKit 0.5.0: A new design language, multi-bot instances, and consent-respecting quotes

# orderedItems[].object.ephemeral.metadata[].description
In social bookmarking networks, users publish bookmarks, which are annotated links, to the public. This FEP describes the model for such bookmarks and the practices for federating them.

# orderedItems[].object.ephemeral.metadata[].description
This proposal updates FEP-521a to require base-64-url, not base-58-btc, as the default codec for Multibase encoding of public keys.

# orderedItems[].object.ephemeral.metadata[].description
Week in Fediverse 2026-07-03 - Post by @weekinfediverse

# orderedItems[].object.ephemeral.metadata[].ogTitle
Week in Fediverse 2026-07-03 - Post by @weekinfediverse

# orderedItems[].object.content
RE: https://vincentbreton.fr/qui-utilise-a ctivitypub-sur-son-site-wordpress/

Pour l'instant, je ne trouve pas vraiment de personnes en #France ou de la #francophonie qui ont un site #wordpress avec le protocole #activitypub , je cherche, je cherche notamment pour des échanges de pratiques ;-)

# orderedItems[].object.ephemeral.metadata[].description
je recherche des personnes utilisant le plugin ActivityPub sur leur site WordPress pour un partage d'expériences

# orderedItems[].object.ephemeral.metadata[].ogDescription
je recherche des personnes utilisant le plugin ActivityPub sur leur site WordPress pour un partage d'expériences

# orderedItems[].object.ephemeral.metadata[].ogTitle
Qui utilise ActivityPub sur son site WordPress ? - {{ sep }

# orderedItems[].object.content
The open web is growing.

Communities around Mastodon, the Fediverse and ActivityPub are showing that we don’t have to depend entirely on closed platforms.

What if we take one more step?

Publish important messages on your own website first. Then share them everywhere else.

That’s the idea behind Method M.

https://method-m.eu/M/

#MethodM #Fediverse #Mastodon #ActivityPub #OpenWeb

# orderedItems[].object.ephemeral.metadata[].description
Method M is a public call for source-first communication. Publish important messages first on your own verifiable source, then share them everywhere else.

# orderedItems[].object.ephemeral.metadata[].ogDescription
Method M is a public call for source-first communication. Publish important messages first on your own verifiable source, then share them everywhere else.

# orderedItems[].object.content
#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

# orderedItems[].object.source.content
#Mastodon's #ActivityPub inbox treats object types in tiers. `Note` and `Question` are supported directly. A second tier, `Article`, `Page`, `Image`, `Audio`, `Video`, and `Event`, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as `Note` regardless of what the object actually is.

[mastodon/mastodon#24079][1] asks for content to show up whenever it's present and the `mediaType` is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

[1]: https://github.com/mastodon/mastodon/issues/24079

# orderedItems[].object.ephemeral.metadata[].twitterTitle
Always show object `content`, regardless of object `type`, if `mediaType` is supported · Issue #24079 · mastodon/mastodon

# orderedItems[].object.ephemeral.metadata[].description
Pitch Currently, Mastodon separates ActivityPub objects between “supported” and “converted”, based on object type. Converted objects will only display a title, spoiler text and URL. This is the case even if the object has a content that ...

# orderedItems[].object.ephemeral.metadata[].ogDescription
Pitch Currently, Mastodon separates ActivityPub objects between “supported” and “converted”, based on object type. Converted objects will only display a title, spoiler text and URL. This is the cas...

# orderedItems[].object.ephemeral.metadata[].ogTitle
Always show object `content`, regardless of object `type`, if `mediaType` is supported · Issue #24079 · mastodon/mastodon

# orderedItems[].object.ephemeral.metadata[].twitterDescription
Pitch Currently, Mastodon separates ActivityPub objects between “supported” and “converted”, based on object type. Converted objects will only display a title, spoiler text and URL. This is the cas...

# orderedItems[].object.content
@thefed @hrefna

I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!

https://social.coop/@smallcircles/1163 94824802521441

There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.

I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".

# orderedItems[].object.ephemeral.metadata[].description
Attached: 1 image

#AntiPatterned™

Do NOT create out-of-bound custom and app-centric mechanisms that define new and expected behavior on protocol level.

https://codeberg.org/fediverse/fediverse-ideas/issues/33

#SX #SocialCoding #SocialWeb #ActivityPub #ProtocolDecay #Botiquette

# orderedItems[].object.ephemeral.metadata[].ogDescription
Attached: 1 image

#AntiPatterned™

Do NOT create out-of-bound custom and app-centric mechanisms that define new and expected behavior on protocol level.

https://codeberg.org/fediverse/fediverse-ideas/issues/33

#SX #SocialCoding #SocialWeb #ActivityPub #ProtocolDecay #Botiquette

# orderedItems[].object.content
@thefed @hrefna

ActivityPub at heart is a social graph of addressible actors that exchange activities with an object payload.

There are no "servers", "instances", "users". Neither is there "client", "app", "actor profile", and even not "identity" in #ActivityPub. That these words appear in the specification text, does not make them part of the protocol. Yes, all software runs on a computer system, yet "system" is not part of ActivityPub.

But you'd be forgiven the confusion, as over time app developers have liberally introduced abstractions that were subsequently seen by others as "the way to do it" and became de-facto standards. The name for that is Post-facto interoperability, "follow-the-leader", and it is the predominant way in which the fediverse has evolved unfortunately, without the specs catching up and incorporating the protocol decay this introduces. There were no good rules for protocol extension, and subsequent delineation of what is core protocol and what's an extension.

# orderedItems[].object.content
Let's talk for a moment about what an actual actor model could look like in a protocol _like_ #ActivityPub. I've done variations on this thought experiment before, but I find it useful to revisit.

alice@servera wants to send a message to bob@serverb. So Alice (A) accesses her profile and pulls a reference to an outbox actor (Ref{O}). She send the message (M) to this outbox:

A -M-> O

With me so far?

The Outbox actor does Something™, it doesn't matter what, but the server that hosts the outbox actor now may do one of two things, depending on whether servera (Sa) already has a reference to an inbox actor (Ref{I}) for bob on serverb (Sb).

The first scenario is a derivation of the second, so let's go through the second.

For this scenario Sa reaches out to webfinger (or some other lookup mechanism, but let's use webfinger) and says to it "gimme the user profile for bob@serverb." Sb returns the user profile Profile{bob@serverb}.

Within Profile{bob@serverb} is a list of actor references with names. One of which is named inbox. So now Sa has Ref{I} and can execute:

Sa -M-> I

In a way, we could end here and be content.

We're not done.

This is basically identical to the current ActivityPub flow with a few notable exceptions:

1. Note that I am not talking about the _user_ as an _actor_. The user is a user. The actor is an actor. Profile{bob@serverb} is not an actor, it's a Profile of a User.
2. I formalized the addition of webfinger. I don't need to do this, and there are alternatives.
3. It could _very_ well be that the inbox reference you are handed is identical between multiple actors.
4. I am treating "The Inbox" as a singular thing, but it _doesn't have to be_. I could have a different reference for where to send Events or calendar entries, I could have a different reference for where to send direct messages versus general posts, etc. All of this could be laid out pretty easily in a single map.
5. Most critically: The "inbox" is not a dereferencable collection. It's an _actor reference_. What gets exposed to the user might be completely different than what gets sent there.

The details don't matter as much as this: the foundational unit by which we reason about the system is different.

# orderedItems[].object.content
In a few days, the last brick of the relay server will be published for an official release and a tag.
A lot of stress when you are alone, but after a few weeks the work has paid off, it is really stable.
Running your own #ActivityPub server on your phone will be as simple as using any other app. You will not be limited to a lookalike: micro-blogging, media, videos, all you want in a simple tap.

#HolosSocial

# orderedItems[].object.content
I am psyched about #kazarma, the bridge between #matrix and #ActivityPub

https://kazar.ma/