objects (@objects@social.rjp.is)
The Mastodon API could do with an expires_at option for posting non-poll statuses which are useless after a specific date (such as gig notifications, etc.)
(Akkoma/Pleroma support it as a custom extension but Mastodon/GotoSocial don’t seem to.)
(Obviously I can rig something up to remember what’s been posted in SQLite and delete/mark them expired when their time is up but it’d be easier if it was part of the general API.)
Show Original Post
lps (@lps@mograph.social)
I was just reminded of the awesomeness of #castopod the self-hosted #podcasting platform that is connect to the #fediverse by #activitypub
This allows us to follow, comment etc etc from #mastodon or similar apps:)
And discovery is easy:).
https://index.castopod.org/#&language=en
And to get you started, for the techies out there, may I suggest
the latest episode is amazing!
"Guerrilla Infrastructure in the Age of the Electrostate"
Show Original Post
lps (@lps@mograph.social)
@overlappodcast What a fantastic podcast subject! I love that you're on #castopod :). I really can't wait for #antennapod to incorporate #activitypub into the app .. it sounds like it's in the works 🤟
Show Original Post
naturzukunft2026 (@naturzukunft2026@mastodon.social)
@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev
Show Original Post
objects (@objects@mitra.social)
It might be not possible to create a generic #ActivityPub server, but nevertheless this is an interesting thought experiment that helps simplify the protocol and figure out the best way to extend it.
I've been thinking about generic servers for quite some time (because this complements my work on nomadic clients), here are my notes:
https://codeberg.org/silverpill/feps/src/branch/main/fc48/fep-fc48.md
RE: https://mastodon.social/users/eyeinthesky/statuses/116095929503245071
Show Original Post
users (@users@holos.dns7.top)
Looks like a new bridge is being developed, supporting newsreader groups and Lemmy (plus presumably any Activity Pub Groups supported software):
https://github.com/rjolina/leNNyTP
#activitypub #lemmy #bridges
Show Original Post
betreibe-ich-clickbaiting (@betreibe-ich-clickbaiting@www.blogissimo.de)
Betreibe ich Clickbaiting?
Bei Mastodon gibt es ein kleines Scharmützel wegen meines letzten Artikels. Mir wird vorgeworfen, ich würde Clickbaiting betreiben. Eigentlich ist die Sache der Rede nicht wert, aber ich will an dem Beispiel erklären, wie ich meine Artikel in Mastodon teile.
[…]
https://www.blogissimo.de/betreibe-ich-clickbaiting/?mtm_campaign=mastodonblog #ActivityPub #Fediverse #Mastodon
Show Original Post
20260219 (@20260219@pilas.guru)
pilas.guru blog en el Fediverso !
Tu blog WordPress puede ser un miembro del Fediverso. Con el plugin ActivePub de Matthias Pfefferle & Automattic el blog puede ser un miembro más del fediverso y lo pueden seguir como cuenta general @pilas.guru donde se postean las principales incidencias (nuevos post, nuevos comentarios, etc.) o por autor de los artículos. En mi configuración del plugin lo ajusté para que el blog completo sea una cuenta y que solo publique artículos, pero podría haber elegido páginas […]https://pilas.guru/20260219/pilas-guru-blog-en-el-fediverso/
Show Original Post
fedizen (@fedizen@mastodon.social)
»Mastodon is for the people« https://blog.joinmastodon.org/2026/02/mastodon-is-for-the-people/?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News
Show Original Post
ktistec (@ktistec@epiktistes.com)
Release v3.3.0 of Ktistec adds support for consent-respecting quote posts (FEP-044f). Quote posts represent the most lines of code I've written for any single changelog entry in my life.
Added
- Support for consent-respecting quote posts (FEP-044f).
Changed
next_attempt_atin tasks now means not scheduled whennil.- Permit type changes for ActivityPub objects.
Important: Quote posts come with a few big caveats. I've been using iterations of this in production for weeks, but if you don't like what you read below you might want to wait for the patch release.
- FEP-044f quote posts require delicate choreography between quoted and quoting servers. Server support across the fediverse is incomplete and evolving. If a quote post doesn't display it might be my bug, it might be their bug. Expect bugs.
- Quote authorization is currently all or nothing—you either blanket reject quote post requests (the default) or blanket accept them. I intend to support more granular controls and manual approval but that comes later.
- Quote authorization revocation isn't supported.
- Automatic re-verification of quote authorization isn't supported.
- Compatibility with other quote implementations is incomplete.
- There will be bugs 🐞 and more bugs 🐜.
#ktistec #crystallang #activitypub #fediverse
Show Original Post
smallcircles (@smallcircles@social.coop)
Saying "outdated version of the #ActivityPub spec" is inaccurate. Mastodon isn't a version of the spec, but a app domain-specific implementation on top of a not-well-defined spec and then subsequently many adopting Mastodon-specific stuff out of convenience. After all they tackled these problems already, so very pragmatic to copy that. But that pragmatism comes at high cost, and here we are today still complaining about it.
The AS/AP ecosystem should be able to stand on its own feet.
What we have achieved with the #FEP is great, but it is still a bandaid. The best we can do in an ecosystem of fiercely independent people intent to go their own way and who shun the design-by-consensus parts (which can be very frustrating indeed) that interoperability requires. It is a way to deal with protocol decay and tech debt after-the-fact, when it has already been created and adopted, part of installed bases and hard to turn towards commonly adopted best-practices.
Show Original Post
smallcircles (@smallcircles@social.coop)
> The main hindrance in Fediverse development is Mastodon. It's a painfully incomplete implementation of a hopelessly outdated version of the ActivityPub spec.
I have a different take on this. As long as we have an app-centric development model that drives fediverse evolution we'll have these problems. I agree that all the Mastodon quirks that have crept on-the-wire is severely holding back the fedi, but I'd rather lay blame by the ecoystem as a whole who continues to follow a post-facto interoperability leader.
Mastodon is an app. If you take on their #ActivityPub namespace extensions you take on a dependency, put them in charge. But they are an app, a product, a single #FOSS project. And they do product development for their user base first and foremost. There's nothing to criticize on that, and also adopting an open standard doesn't come with obligation to maintain/evolve it. Though it would be smart to do so.
The ecosystem should set its own course.
Show Original Post