»#PostQuantumPrivacy for #PostPlatformInternet. — #Fediverse pilots: #ActivityPub with #Dilithiumsignatures. While #Mastodon and other ActivityPub servers still use #RSA-#HTTP-#Signatures by default, developers in the #SocialHub community are working on a #FEP (Fediverse Enhancement Proposal) to clarify signature processing and accommodate #quantumsafealgorithms.« https://hackernoon.com/post-quantum-privacy-for-post-platform-internet?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News

FEP-521a: Representing actor's public keys has been finalized!

https://codeberg.org/fediverse/fep/src/branch/main/fep/521a/fep-521a.md

#fep #fep_521a

FEP-844e: Capability discovery has been published to the FEP repository:

https://codeberg.org/fediverse/fep/src/branch/main/fep/844e/fep-844e.md

I already use it to signal RFC-9421 support. An anonymous Application object is added to actors:

{
  "generator": {
    "type": "Application",
    "implements": [
      {
        "name": "RFC-9421: HTTP Message Signatures",
        "href": "https://datatracker.ietf.org/doc/html/rfc9421"
      }
    ]
  }
}

All important information is embedded, so additional HTTP requests are not necessary.

#FEP

@mapacheMaho Pacheco 🦝🍻 @box464Jeff Sikes @activitypub.blogActivityPub for WordPress @badgefedThe BadgeFed Project

Ah! The LGPL / Language totally forgotten during the monster job of the full list overhaul I did.

Would it be possible for you to PR or file an issue? (Codeberg account always comes in handy for submitting that #ActivityPub #FEP 😜)

I will take a note on my backlog, but will be some time before I get to that.

The Work Continues: What’s Next

Details will follow soon — but the work on events in the #Fediverse is far from complete. Key upcoming milestones include:

• Improvements and new features for the Event Bridge for ActivityPub plugin for WordPress
  Continued development to maintain, fix issues, enhance, and expand functionality.
• Work on Fediverse Enhancement Proposals (FEPs)
  Ensuring a robust final status of FEP-8a8e and focus on recurring and irregularly scheduled events.
• Support for event interoperability in other Fediverse applications
  Contribute to other Fediverse applications and help them to explore and improve support for Event objects. For example, @linos@graz.social has outlined a potential roadmap for Mastodon.
• Contribution to GatherPress
  Active involvement in the GatherPress project — a modern and truly FLOSS community oriented WordPress event plugin — to ensure full ActivityPub compatibility, including RSVP support and advanced federation features.
• Community engagement and outreach
  Participation in conferences, public talks, and direct conversations to foster knowledge exchange, gather feedback, and grow the ecosystem around federated events.

Additional updates and technical details will be shared soon. Input, testing, and collaboration from interested parties are always welcome. Or if you know any conferences we should attend, let us know.

#ActivityPub #Events #Fediverse #FEP #GatherPress #WordPress

Just replied to #SocialHub discussion to @evanprodromou #FEP on #fediverse support for long-form text.

There's a broader discussion that the #ActivityPub dev community isn't really addressing.

Nowhere in the #W3C specs is defined that #Microblogging is the foundation of #SocialNetworking. And certainly not #Mastodon's app-specific interpretation of this domain.

The entire AS extension mechanism is overlooked, and that leads to a massive ⚒️ Golden Hammer anti-pattern.

https://socialhub.activitypub.rocks/t/fep-b2b8-long-form-text/5300/18?u=aschrijver

As we consider ways to implement #ActivityPub 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.

https://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.

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-event

----

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.

https://codeberg.org/linos/fep/src/branch/fep-8a8e/fep/8a8e/fep-8a8e.md

---

[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.

https://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.

https://icalendar.org/the-icalendar-standard-2.html

#EventObjectSchema
#Calendar #Standards #WebStandards #W3C #Microformats #FEP #FediverseEnhancementProposals #iCal #iCalendar #FOSS #WebDevelopment #WebDesign #RubyOnRails #Rails #Mastodon #Dev #Developer #OpenStandards

@abeorch @nextcloudNextcloud 📱☁️💻 @warmaster @buyeuropean

Good idea. And it might also federate with #SocialHub the #ActivityPub developer community that is custodian of the #FEP process, among others.

https://socialhub.activitypub.rocks

I wrote a #FEP about actor statuses. Yeah, those things near the name that Facebook had in 2007.

https://codeberg.org/fediverse/fep/src/branch/main/fep/82f6/fep-82f6.md

#activitypub

Started writing a new FEP:

FEP-0151: NodeInfo in Fediverse Software (2025 edition)

Mentioned some best practices. What else should be added there?

#FEP #NodeInfo

@write_as

That is excellent and exemplary to other fediverse app developers to help the #ActivityPub ecosystem improve and become increase overall #interoperability.

PS. I noticed that no discussion thread for the #FEP was created on #SocialHub, so I took that upon me:

https://socialhub.activitypub.rocks/t/fep-b2b8-long-form-text/5300/2?u=aschrijver

I mentioned #WriteFreely / #WriteAs in follow-up as candidate for the Implementations sections of this FEP.

cc FEP author @evanEvan Prodromou

@write_as I like the improvements and above all the focus to adhere to Fediverse Enhancements Proposals. Thank you! In this case:

FEP-b2b8 Long-form Text

https://codeberg.org/fediverse/fep/src/branch/main/fep/b2b8/fep-b2b8.md

#fep #fep_b2b8 #activitypub #socialhub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

1. The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
2. Separating approval objects from interactions appears more secure against forgery
3. The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
4. The extensible framework allows for handling diverse interaction types, not just replies

I wonder if creating an #FEP that extracts GoToSocial's interaction policy design into a standalone standard might be worthwhile. It could potentially serve as a more comprehensive foundation for access control in #ActivityPub.

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

Coda: The growth of BlueSky, and the novel features it launches with, point to a need for a 2.0 version of ActivityPub. One that fleshes out and updates the protocol based on dev experiences in the first decade of active use, and intentions going forward.

Ideally an AP 2.0 would include a formal mechanism for protocol extensions. One that learns from the experiences of the FEP process.

#ActivityPub #AP #AP2 #FEP #BlueSky

On the #W3C #SocialCG a related issue. For a good bottom-up standardization process that guarantees an open and inclusive #ActivityPub related ecosystem, there should be good alignment with the #FEP Process.

https://github.com/swicg/general/issues/43

What should #FEP Process be about? #ActivityPub et al? Or everything that vaguely represents #SocialWeb?

I took FEP codeberg chat to a #SocialHub thread that discusses how we can ensure and foster an open and grassroots ecosystem.

Imho the FEP Process should define its particular scope of protocols and technologies that are relevant, and that involves AS/AP and closely affiliated technologies.

FEP Process should NOT define what #Fediverse is. Leave that to Fedizens.

https://socialhub.activitypub.rocks/t/3-stage-standards-process-guaranteeing-an-open-and-decentralized-ecosystem/3602/42

#ActivityPub "The Good, the Bad and the Ugly" is a good article by @dominikDominik Chrástecký - Blog

https://chrastecky.dev/technology/activity-pub-the-good-the-bad-and-the-ugly

The two mentioned examples in "The Bad" are long-time issues that were also discussed at #SocialHub. I just responded to one of them on the forum..

The #Mastodon Update(Note) quirk. https://socialhub.activitypub.rocks/t/update-note-quirk/4545/14

The other one is around Direct Messages which are a hack (a Note with special sauce). #LitePub specifies ChatMessage object type here, which is the intended way to extend the protocol. #FEP

Progress on the FEP for Event objects

The FEP-8a8e (Fediverse Enhancement Proposal) had at lot of progress in the last months. In the meantime, the document has become somewhat more extensive than originally planned, but contains not only instructions for new features that have to be tediously implemented, but also a lot of advice and points that should provide orientation for developers of Fediverse applications that support events.

It now covers:

• Required attributes
• Events with Open End
• Timezone
• Physical and Virtual Locations
• Event status
• RSVP (Attendee Management)
• Event Banner and Poster Images
• Event Categories
• Discoverability
• Event Organizers
• Upcoming Events Collection for ActivityPub actors
• Term Definitions

Many thanks again to all reviewers and co-editors:

@lesionles @heiglandreasAlerta! Alerta! @naturzukunft @laurin

We warmly welcome further feedback from the communities of #Friendica, #Mobilizon, #Hubzilla, and other Fediverse platforms supporting events.
If you’re working on such an application or are part of these communities, your insights would be very valuable! @developers @mobilizon

#ActivityPub #Fediverse #FEP

How to subscribe to a thread?

Several days ago FEP-efda: Followable objects was published. I don't like this solution because ActivityPub spec only talks about "following" in the context of actors, and the proposed "proxy-following" mechanism forces us to change some well-established practices.

So here is an alternative: FEP-f06f: Object observers.

Object observer is an actor that can be followed to receive object updates. If conversation thread is a collection, its observer will broadcast Add and Remove activities that have thread collection as their target. Observer's followers will have an up-to-date view of the thread.

#ActivityPub #FEP

I've made some changes to FEP-521a: https://codeberg.org/fediverse/fep/pulls/482

- Many changes due to a rename of Controller Documents specification to Controlled Identifiers.
- Using https://www.w3.org/ns/cid/v1 context in example. I haven't tried it myself yet, but it works in JSON-LD playground.
- Key ID and actor ID are now recommended to have same origin.

#fep_521a #fep