to get future videos right in your timeline, that allows you to follow and comment thanks to #activitypub follow their video account directly
to get future videos right in your timeline, that allows you to follow and comment thanks to #activitypub follow their video account directly
New NLNet Projects were recently announced, with a solid collection of ActivityPub related ones:
* Mastodon adding new features for institutional instances
* ActivityPub Polls for Wordpress
* Funkwhale Federation Improvements
* Making Events more interoperable between Fediverse Platforms
* Context Discovery in NodeBB
* Icosa 3-D Model Sharing with ActivityPub
Did I miss any?
https://nlnet.nl/news/2025/20250624-announcement-grants-CommonsFund.html
Government officials currently needing to be present on both #threads and #bluesky to reach the masses gives me hope that this eventually provides enough pressure for both services to fully support #ActivityPub by default, with governments then setting up their own fedi servers. #SocialWeb
We're pleased to share that Encyclia has joined our success stories.
@encyclia bridges academic research to the #fediverse by making #ORCID researcher profiles and publications discoverable through #ActivityPub—built with #Fedify for seamless interoperability across Mastodon and other fediverse platforms.
This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.
We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.
Learn more about Encyclia at https://encyclia.pub/.
We are pleased to announce the release of #Fedify 1.7.0. This release was expedited at the request of the Ghost team, who are actively using Fedify for their #ActivityPub implementation. As a result, several features originally planned for this version have been moved to Fedify 1.8.0 to ensure timely delivery of the most critical improvements.
This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.
Native retry mechanism support
This release introduces support for native retry mechanisms in message queue backends. The new MessageQueue.nativeRetrial
property allows queue implementations to indicate whether they provide built-in retry functionality, enabling Fedify to optimize its retry behavior accordingly.
When nativeRetrial
is set to true
, Fedify will delegate retry handling to the queue backend rather than implementing its own retry logic. This approach reduces overhead and leverages the proven retry mechanisms of established queue systems.
Current implementations with native retry support include:
DenoKvMessageQueue
— utilizes Deno KV's automatic retry with exponential backoffWorkersMessageQueue
— leverages Cloudflare Queues' automatic retry and dead-letter queue featuresAmqpMessageQueue
— can now be configured to use AMQP broker's native retry mechanismsThe InProcessMessageQueue
continues to use Fedify's internal retry mechanism, while ParallelMessageQueue
inherits the retry behavior from its wrapped queue.
AMQP message queue improvements
Alongside Fedify 1.7.0, we have also released @fedify/amqp 0.3.0. This release adds the nativeRetrial
option to AmqpMessageQueueOptions
, enabling you to leverage your AMQP broker's built-in retry mechanisms. When enabled, this option allows the AMQP broker to handle message retries according to its configured policies, rather than relying on Fedify's internal retry logic.
Configurable double-knocking
The new FederationOptions.firstKnock
option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.
Previously, the first knock for newly encountered servers always used RFC 9421 (HTTP Message Signatures), falling back to draft-cavage-http-signatures-12 if needed. With this release, you can now configure which specification to use for the first knock when communicating with unknown servers, with RFC 9421 remaining the default.
Summary
This release maintains Fedify's commitment to reliability and compatibility while laying the groundwork for more efficient message processing. The native retry mechanism support will particularly benefit applications using queue backends with sophisticated retry capabilities, while the double-knocking mechanism addresses real-world compatibility challenges in the ActivityPub ecosystem.
For detailed technical information about these changes, please refer to the changelog in the repository.
Nachdem #wanderer inzwischen auch #ActivityPub unterstützt, muss ich das jetzt doch mal eingehender testen.
https://trails.tchncs.de/trail/view/@folix/k5b68asz44c5k2l
Development for Mastodon compatible #ActivityPub polls in #WordPress is starting. This project is receiving funding from the latest round of the NGI Zero Commons Fund. #ngi0 #NLnet
I've built #Enigmatick to manage threading using conversation
IDs like Mastodon uses. But that's not aligned with #ActivityPub - or at least it wasn't the least time I looked. ActivityPub uses inReplyTo
to indicate direct parent relationships and doesn't have a concept for linking multiple objects under a single ID.
Other systems don't use the conversation
convention and that's caused some discord in my timeline. So now I'm learning about closure tables and concepts I probably would already know if I had studied computer science in college. But it's never too late to learn!
We're pleased to announce that #Node.js support has been merged and will be available in #BotKit 0.3.0.
Now you can build your #ActivityPub bots with both #Deno and Node.js, giving you more flexibility in choosing your preferred runtime environment.
Stay tuned for BotKit 0.3.0!
From: blenderdumbass . org
I decided since I don't understand how all of this works, I will just simply ask Jerry personally about all of this data and technical details, so that people will no longer be confused about all of this.
Includes an exclusive interview with Jerry.
Read or listen: https://blenderdumbass.org/articles/clarifying_costs_of_running_the_fediverse_with_jerry_from_infosec.exchange
Our Starter Sets, which have hundreds of recommended sources on everything from Elden Ring to Michigan, are the easiest way to discover custom feeds on Surf, and start building your own.
Got feedback? Email feedback@surf.social! And if you're not in the beta yet, join the waitlist here, using the referral code SURFSHARES.
Anybody with an #activitypub or #atproto or related open social web project planning to go to Web Summit in Lisbon, Portugal, in November? Is that something this community does?
Just dropped a new article on the VEX.blue BETA site: Connect your Bluesky account to the Fediverse
Want your Bsky posts to show up on Mastodon? Or your Mastodon account to be visible on Bsky?
This guide walks you through using bsky.brid.gy and ap.brid.gy so your posts & profile can talk to others across platforms.
Read + reply via your timeline
https://new.vex.blue/articles/2024/09/06/bsky-fedi
Just a thought, from a knuckle-dragging biology scientist. TL;DR: I believe there is scope to make the hosting of a peertube instance even more lightweight in the future.
I read some time ago of people using #webAssembly to transcode video in a user's web-browser. https://blog.scottlogic.com/2020/11/23/ffmpeg-webassembly.html
Since then, I believe #WebGPU has done/is doing some clever things to improve the browser's access to the device's GPU.
I have not seen any #peertube capability that offloads video transcoding to the user in this way.
I imagine, though, that this would align well with peertube's agenda of lowering the bar to entry into web-video hosting, so I cannot help but think that this will come in time.
My own interest is seeing a #Piefed (activitypub) instance whose web-pages could #autotranslate posts into the user's own language using the user's own processing power... One day, maybe!
Thank you again for all your hard work; it is an inspiration.
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 […]
https://activitypub.blog/2025/06/24/what-we-shipped-so-far-in-2025/
Just added my article “Decentralised Social Media” to the VEX.blue BETA site - Now with Fediverse comments!
It’s a full write-up on Mastodon, Threads, and why decentralisation matters.
Read + reply via your timeline
https://new.vex.blue/articles/2024/09/03/decentralised-social-media
I just updated the #fediverse experience curated list with the latest #ActivityPub server platforms. Great to see new types of applications finding their way to the interoperable #SocialWeb!
https://delightful.coding.social/delightful-fediverse-experience
Despite traveling, I've been working on some things for #GoActivityPub and one of them is the ability to generate web optimized images when uploading JPG/PNG files.
The end result is an Image object containing multiple URL entries to small/medium web-optimized copies, plus the original.
This still requires some work on the frontend web components to be able to select from multiple variants based on the reported width/height.
But it also allowed me to fix issues with the ability of the library to process activities that contain multiple Objects.
The Fediverse, a network of independently run servers using the ActivityPub protocol, is #segmented by #serverblocks.
These #blocks, often based on imported #blocklists, create #echochambers and hinder message threads.
While #decentralisation is a goal, the Fediverse’s current state, with heavy-handed #moderation and #serverblocking, undermines this principle.
https://battlepenguin.com/tech/the-broken-fediverse?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News