Search results

Is anyone running their blog on a static or semi-static stack like Hugo, VitePress, etc.?

If so, is there an easy way to add an ActivityPub-based comment system, maybe some share buttons, and also republish content to the Fediverse? I'm not looking for ActivityPub-native blogging platforms, more interested in adding ActivityPub support in a mostly client-side way.

0
0
0

Three new , Bonfire Social, Channel.org, and Bounce, were showcased at the virtual conference:

1️⃣ is a for creating digital .

2️⃣ content across the web.

3️⃣ allows users to their accounts to while retaining followers.

👉 theverge.com/news/680895/fediv

0

We've turned on ActivityPub for Shellie's website :)

That means you can follow Shellie at @shellieIron Chef Shellie and each time she updates the blog with a new recipe, you should see that pop into your feed.

I had hoped the plugin would make all her old recipes live, but that doesn't happen. Unless, you punch the URL into a search box for Mastodon. In which case it makes a new toot, but backdated, and I can retoot it :)

This is the new home for Shellie on the Fediverse.
0

Videospielgeschichten replied to the below article:

6.0.0 – New Kids on the Block

ActivityPub for WordPress @activitypub.blog@activitypub.blog

<p>Our latest release brings a lot of improvements — especially to our blocks! </p> <p>The Follow Me and Followers blocks now have a fresh design, better interactivity, and broader support for ActivityPub-enabled users.</p> <p>The Reactions block and “Reply on the Fediverse” feature also now take advantage of the latest Block Editor features and are built on the Interactivity API for a smoother experience.</p> <p>We’ll follow up soon with a deeper dive into the new block features — stay […]</p>

Read more →
0
3
0
0

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselves—making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

🔍 WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

🛠 Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

🎯 Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

2
0
2

Ω🪬Ω
, the customizable timeline algorithm / filtering system for your Mastodon feed, now has a "TOTAL CHAOS" preset for when you're really feeling like mixing up your timeline in addition to a way to weight toots based on the author's follower count, highlighting of hashtags based on how much you use or interact with them, and a bunch of other fund stuff.

* Try It: michelcrypt4d4mus.github.io/fe
* Code: github.com/michelcrypt4d4mus/f
* Video of FediAlgo in action: universeodon.com/@cryptadamist

screenshot of fedialgo with TOTAL CHAOS preset chosen
0
0

Did you know? provides optimized for LLMs through the llms.txt standard.

Available endpoints:

Useful for training assistants on / development, building documentation chatbots, or -powered dev tools.

0

6.0.0 – New Kids on the Block

ActivityPub for WordPress @activitypub.blog@activitypub.blog

<p>Our latest release brings a lot of improvements — especially to our blocks! </p> <p>The Follow Me and Followers blocks now have a fresh design, better interactivity, and broader support for ActivityPub-enabled users.</p> <p>The Reactions block and “Reply on the Fediverse” feature also now take advantage of the latest Block Editor features and are built on the Interactivity API for a smoother experience.</p> <p>We’ll follow up soon with a deeper dive into the new block features — stay […]</p>

Read more →
0
3
0
0
0

🔥 Bonfire Social 1.0 release candidate has landed!

Curious about what the fediverse could look like with real community control?

Try out features like custom feeds, nested discussions, shared profiles, circles, and boundary-based permissions — then let us know what breaks or needs improvement.

More details and video demos: bonfirenetworks.org/posts/bonf

0
0
0

Hi @mikedev,
as you implemented you may know - which servers in the wild use it?
Request

I built a parser for yesterday and am curious to look at other implementations/code as well. Mine so far: codeberg.org/mro/seppo/src/com
Would love to discuss it.

0
0

Join us at today — an unconference about the ActivityPub ecosystem. We’ll be doing a live demo and proposing a session:

Behind the Bonfire: building a fediverse app in public

Curious how a fediverse app actually gets made? We’ll share the journey to Bonfire 1.0, talk about deployment, governance, and what building in public really looks like — the good, the hard, and the weird.

1/2

This is a chance to poke at the process, challenge assumptions, and have an open conversation. Bring your curiosity, hard questions, and ideas about co-design, funding, burnout, moderation, and the messy realities of open-source work.

Let’s dig into how fediverse apps get built, maintained, and shaped by their communities.

See you there! 🔗 fediforum.org

0

Exciting news for the project! We're thrilled to announce that Emelia Smith (@thisismissemEmelia 👸🏻) has joined as a co-maintainer alongside Hong Minhee (@hongminhee洪 民憙 (Hong Minhee)).

Emelia brings extensive experience in the ecosystem, having been a long-time contributor to Mastodon and a leading expert in trust & safety tooling for decentralized social networks. She's dedicated years to improving moderation systems and security across platforms.

Her recent contributions to Hollo have been substantial—implementing the reporting/flagging system and making significant improvements to OAuth and security features. These valuable contributions naturally led to her joining as a co-maintainer.

This collaboration marks an important milestone for Hollo as we continue building better single-user microblogging software for the fediverse. Welcome aboard, Emelia! 🚀

8
3
0
0

Depending on where you live, Meta keeps track of your:

* Full name.
* Previous name if you change your name
* E-mail (past, current, future)
* Date of birth and age.
* Address (past, current, future)
* Living state (do you own, lease, or rent)
* Phone number (past, current, future)
* Cellular device model (past, current, future)
* Cellular device IMEI number (serial too, if provided)
* Friends
* Family relationship
* Relationship status
* Marital status
* Personal associations status
* Sexual preferences
* Gender identity
* Education (past, current, future)
* Employment status (past, current, future)
* Income
* Travel status (GPS)
* Shopping
* Political affliction
* Government affiliation.
* Browser history

If you had to verify your account and submitted documentation, we additionally keep track of:

* Residence status
* Driving status (if you have a license or not)

* Whether if you have passport or not. - But the system will assume you do, if they notice your travel status (GPS) moves internationally.

If at any time you shared a link back to any of your personal accounts, anywhere -- Meta knows you have an account.

That includes competing social media platforms, such as the Fediverse.

The value in this is both market resource and further marketing, for example, if you talked about watching Netflix, expect Meta to recommend, HBO Max. And if Meta notices you're using a known competing app or platform, Meta's app will increase the notification to draw you back to Meta.

0

If the posts, pages, podcasts, articles and videos etc on every website were all natively items, the whole web would be part of "social media". But it wouldn't be right to call that "social networking". That would still just be what you're doing messaging and managing online groups with your friends, family and other communities.

0

I might be overdoing this whole and thing, but… here's the first steps with , a RDF-to-HTML mapper and :

codeberg.org/Taganak/trinja/sr

The idea is: Use *any* resource described as RDF (e.g. from or an action), link a template to it or its rdf:type in your own set of statements, and there you got your visualisation!

Based on , the development kit by @codecraftBitSyndicate and me. We are collecting real-world examples at a good rate!

Screenshot of a Turtle document; see linked code in post for text version.A quite basic web page with heading "Ninja Turtles", followed by four cards with names and depictions of the four Ninja Turtles Leonardo, Raphael, Donatello and Michelangelo.
0
0

Fediverse Report - This week's news

A quiet week as the hype announcements are waiting for this week's @fediforum . You can catch me on Thursday on Fediforum with a session on whats new on the open social web!

In other news:
- A @peertube AMA on Lemmy, and the first milestone of their fundraising for their app reached
- The @swfSocial Web Foundation publishes Web Components

fediversereport.com/fediverse-

0
0
0
0
0
0

0.6.0 is coming soon!

We're putting the finishing touches on our biggest security and feature update yet. Here's what's coming:

Enhanced

  • RFC 8414 (OAuth metadata discovery)
  • RFC 7636 ( support)
  • Improved authorization flows following RFC 9700 best practices

New features

  • Extended character limit (4K → 10K)
  • Code syntax highlighting
  • Customizable profile themes
  • EXIF metadata stripping for privacy

Important notes for update

  • Node.js 24+ required
  • Updated environment variables for asset storage
  • Stronger SECRET_KEY requirements (44+ chars)

Special thanks to @thisismissemEmelia 👸🏻 for the extensive OAuth improvements that help keep the secure and compatible! 🙏

Full changelog and upgrade guide coming with the release.

2
1
0

Trying Ghost's AP implementation just emphasizes what I don't like about AP-in-practice. Between that and all the bridge profiles, there are 4 new profiles, each with their own copy of the data to maintain.

With AT, it's just the one account across all platforms with all the data stored on my PDS.

Worse, to get any notice to posts appearing on them, I have to boost from my existing accounts on each network. That's a lot of trouble! With AT, they would just pull it from the relay, which pulls from my PDS. Or go directly to the PDS in some circumstances.

AP could probably be better in practice, but everyone is required to make it work with Mastodon or essentially be incompatible since it has most of the network on a few servers with a standard ignoring implementation.

New problems emerge the more I try to use it. Direct AP<->AP works fine. Bridged stuff is inconsistent. Likes, boosts, etc don't go through. Follows don't show even if there's a bridged pair for the following account.

I don't fault the people working on Bridgy but I do know this would be easier to get right if follow relationships were simple data any authenticated app could read.

I haven't heard a positive account of developing anything moderately complex for AP. By comparison, all the AT dev accounts are positive, usually noting how easy it is to work with everything since everything is "on protocol" (the term of art for storing data in lexicons on your PDS) rather than dependent on negotiating implementation differences between the dominant platform and everything else.

0

1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! 🚀

2
0
0
0

Hi @mikelynch 👋

I am updating delightful.coding.social/delig and wanted to include your archive to pages utility.

Yet the curated list is only for open source resources and without license the script is technically not. Would you be open to add a FOSS license to it, perhaps?

git.tilde.town/bombinans/apub2

0
0
0
0

Bumped into this interesting yet unmaintained project while updating delightful.coding.social/delig

"Stonenet is a (social) publish-subscribe network, also known as a decentralized social media platform. It is designed to protect free speech, and resist censorship. Everyone moderates their own home feed, and content is only distributed by those peers that have consented to do so, by subscribing to someone and thereby explicitly supporting their content"

github.com/bamidev/stonenet

0

Ω🪬Ω
The new version of is much, much faster at loading and reordering the timeline. Also has fancy gradients to show you which hashtags in your feed are the ones trending the most and which ones you post about the most. Also a bunch of other tweaks and improvements.

* Try the demo: michelcrypt4d4mus.github.io/fe
* Video of it in action: universeodon.com/@cryptadamist
* Release notes: github.com/michelcrypt4d4mus/f

Screenshot of Fedialgo demo
0

Trying Ghost's AP implementation just emphasizes what I don't like about AP-in-practice. Between that and all the bridge profiles, there are 4 new profiles, each with their own copy of the data to maintain.

With AT, it's just the one account across all platforms with all the data stored on my PDS.

Worse, to get any notice to posts appearing on them, I have to boost from my existing accounts on each network. That's a lot of trouble! With AT, they would just pull it from the relay, which pulls from my PDS. Or go directly to the PDS in some circumstances.

AP could probably be better in practice, but everyone is required to make it work with Mastodon or essentially be incompatible since it has most of the network on a few servers with a standard ignoring implementation.

0

Good news! We've officially added support to the roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

🎉 support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, can now run on Cloudflare Workers.

What's included:

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

1

I just discovered the superb powrss.com by @enoccEnoc - a site that aims to "make it easier to discover independent sites."

And thanks to it, I found this inspiring blog post by @sylvia: "Do Nothing" sylvia.studio/do-nothing/

Aw the magic of the internet (as it was originally intended) ✨

Wishing everyone a lovely Sunday! And fascinating, serendipitous discoveries on powrss.com 😊

@_elenaElena Rossini ⁂ @enoccEnoc @sylvia

Nice! Good opportunity to mention I just added some fedi-related resources, magic of the to:

codeberg.org/fediverse/delight

(In the Bridges section)

Had a huge backlog and I am making lotsa updates now to process it. Earlier did too to apps and clients fedi delightful lists, and the root list, now hosted at delightful.coding.social

0
0

As we consider ways to implement into our FOSS Community Calendar Ecosystem platform Koalagator, I've been looking over the differing specs for how to specify the event object schema.

Have any other folk wrestled with this?Asking before I get arms deep in this stuff.

For those playing at home...

---
Schema.org - Event

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet.

schema.org/Event

-----
W3C Activity Vocabulary - Event

This specification describes the Activity vocabulary. It is intended to be used in the context of the ActivityStreams 2.0 format and provides a foundational vocabulary for activity structures, and specific activity types.

w3.org/TR/activitystreams-voca

----

Fediverse Enhancement Proposal
FEP-8a8e: A common approach to using the Event object type

ActivityStreams defines the Object Type Event. In real-world applications, the event object immediately showed the need for extension. Applications featuring Event objects have often chosen to add additional attributes and clarifications (i.e., interpretations) in order to implement their particular use case. This proposal clarifies and extends the ActivityPub standard to address the needs that have arisen in real-world implementations.

codeberg.org/linos/fep/src/bra

---

[HTML] Microformats - h-event

People are using microformats to mark up profiles, posts, events and other data on their personal sites, enabling developers to build applications which use this data in useful and interesting ways.

microformats.org/wiki/h-event

---

iCalendar Standard (RFC 5545)

iCalendar was first defined as a standard as RFC 2445 in 1998 by the Internet Engineering Task Force (IETF). Today, iCalendar is used to import and synchronize events on various platforms, including smart phones, computer and web applications.

icalendar.org/the-icalendar-st


As we consider ways to implement into our FOSS Community Calendar Ecosystem platform Koalagator, I've been looking over the differing specs for how to specify the event object schema.

Have any other folk wrestled with this?Asking before I get arms deep in this stuff.

For those playing at home...

---
Schema.org - Event

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet.

schema.org/Event

-----
W3C Activity Vocabulary - Event

This specification describes the Activity vocabulary. It is intended to be used in the context of the ActivityStreams 2.0 format and provides a foundational vocabulary for activity structures, and specific activity types.

w3.org/TR/activitystreams-voca

----

Fediverse Enhancement Proposal
FEP-8a8e: A common approach to using the Event object type

ActivityStreams defines the Object Type Event. In real-world applications, the event object immediately showed the need for extension. Applications featuring Event objects have often chosen to add additional attributes and clarifications (i.e., interpretations) in order to implement their particular use case. This proposal clarifies and extends the ActivityPub standard to address the needs that have arisen in real-world implementations.

codeberg.org/linos/fep/src/bra

---

[HTML] Microformats - h-event

People are using microformats to mark up profiles, posts, events and other data on their personal sites, enabling developers to build applications which use this data in useful and interesting ways.

microformats.org/wiki/h-event

---

iCalendar Standard (RFC 5545)

iCalendar was first defined as a standard as RFC 2445 in 1998 by the Internet Engineering Task Force (IETF). Today, iCalendar is used to import and synchronize events on various platforms, including smart phones, computer and web applications.

icalendar.org/the-icalendar-st


0