@benpate - can you post a link to that #FEP here? Is this it: https://codeberg.org/fediverse/fep/src/branch/main/fep/3b86/fep-3b86.md

I figured as much, but good to know for sure : )

> if there is one final or near final #FEP I should point to for each UX fix happy to go back and add them!

That's a bit above my paygrade, but @silverpill might have some suggestions?

> And part 2 is live now

All my Christmases come at once! : P Will devour this now.

I’ll go back and edit that a bit to show that I have nothing but love for the FEP process!

Also if there is one final or near final #FEP I should point to for each UX fix happy to go back and add them!

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 ActivityPubplugin 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

"I was also pointed to another interesting topic: the FEDERATION.md file and the Fediverse Enhancement Proposals initiative (one of which is precisely the FEDERATION.md file). After reading about this file and reviewing other proposals on the project’s site, I have to say it’s fantastic. It’s an open process for standardizing and documenting extensions and proposed changes to the ActivityPub protocol and other technologies used in the Fediverse"

@mczachurski, 2025

https://vernissage.photos/news/7504383493426645980

#FEP

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 @evan

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

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:

@lesion @heiglandreas @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