#fep — Public Fediverse posts

@gabboman @jcm

In theory you can do anything you want, and in practice people do that too. As long as you don't break anything that #ActivityPub specs prescribe, the #ActivityStreams vocabulary is just a 'toolbox' of #SocialWeb primitives you can use as building blocks in your solution. The only issue arises if you want your mechanism to have #interoperability with other #fediverse solutions. They should either ignore, or understand it, and not break. Writing a #FEP is the best-practice way to walking the path of adoption of your approach.

@gabboman @jcm

In theory you can do anything you want, and in practice people do that too. As long as you don't break anything that #ActivityPub specs prescribe, the #ActivityStreams vocabulary is just a 'toolbox' of #SocialWeb primitives you can use as building blocks in your solution. The only issue arises if you want your mechanism to have #interoperability with other #fediverse solutions. They should either ignore, or understand it, and not break. Writing a #FEP is the best-practice way to walking the path of adoption of your approach.

@aproposnix

This is a great and important article by @soatok

It also mentions how anyone, not just #security experts, can help make E2EE on the ActivityPub #fediverse a reality.

For instance by #fedi devs by supporting #FEP 521a: Representing actor's public keys in their #ActivityPub implementation:

https://fediverse.codeberg.page/fep/fep/521a/

Or help improve the #UX of E2EE enabled fedi apps. Or even just spread the word around by :boosts_appreciated: boosting the article around, and give impetus to #E2EE adoption.

See also:

https://swicg.github.io/activitypub-e2ee/

https://publickey.directory/

@aproposnix

This is a great and important article by @soatok

It also mentions how anyone, not just #security experts, can help make E2EE on the ActivityPub #fediverse a reality.

For instance by #fedi devs by supporting #FEP 521a: Representing actor's public keys in their #ActivityPub implementation:

https://fediverse.codeberg.page/fep/fep/521a/

Or help improve the #UX of E2EE enabled fedi apps. Or even just spread the word around by :boosts_appreciated: boosting the article around, and give impetus to #E2EE adoption.

See also:

https://swicg.github.io/activitypub-e2ee/

https://publickey.directory/

@ozoned @itchio

Yea, things are dispersed. The #fediverse org at #Codeberg is a place where a host of people (co)maintain various fedi-related projects, most notably the #ActivityPub #FEP process. I maintain the 3 fedi curated lists there for https://delightful.coding.social initiative.

@ozoned @itchio

Yea, things are dispersed. The #fediverse org at #Codeberg is a place where a host of people (co)maintain various fedi-related projects, most notably the #ActivityPub #FEP process. I maintain the 3 fedi curated lists there for https://delightful.coding.social initiative.

Vorschläge zur Verbesserung des Fediverse

Ein sogenanntes "#Fediverse Enhancement Proposal" (#FEP) ist ein #Dokument, welches der fediversalen Gemeinschaft Informationen bereitstellt. Das Ziel eines FEP ist es, die Interoperabilität zwischen verschiedenen fediversalen Diensten zu verbessern.

Auf #Codeberg wird ein passendes "#Git #repository" verwaltet.

https://codeberg.org/fediverse/fep/src/branch/main/

Wer des Englischen mächtig ist, findet hier Dokumente mit verschiedenem Status und kann theoretisch auch selbst ein neues FEP erstellen.

@thefed @hrefna

I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!

https://social.coop/@smallcircles/116394824802521441

There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.

I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".

@thefed @hrefna

I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!

https://social.coop/@smallcircles/116394824802521441

There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.

I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".

@djm62 @shlee

Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:

https://coding.social/blog/grassroots-evolution

@djm62 @shlee

Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:

https://coding.social/blog/grassroots-evolution

I'm requesting final comments on FEP-7628: Move actor

#fep_7628 #fep #activitypub

I'm requesting final comments on FEP-7628: Move actor

#fep_7628 #fep #activitypub

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Since ​@[email protected] seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call.

The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level.

The current implementation appears to have unintended, and unconsidered consequences associated with it.

Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually.

Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof.

The Solution: all platforms in the Fediverse should implement instance level relays in the following manner:

1. Instance level relays are disabled for all users on that instance.
2. User settings provide a list of the relays provided at the instance level.
   1. Users can opt to leave the relay(s) disabled, or
   2. They can choose to enable the relays they trust their content being sent to.

Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse.

I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP.

#fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev
@alice @admin @gotosocial @Gargron

Trying to see where things are with FEP-ef61: Portable Objects. Anyone working on this?

https://fediverse.codeberg.page/fep/fep/ef61/

https://socialhub.activitypub.rocks/t/fep-ef61-portable-objects/3738

#fediverse #FEP #PortableObjects #FEPEF61

Trying to see where things are with FEP-ef61: Portable Objects. Anyone working on this?

https://fediverse.codeberg.page/fep/fep/ef61/

https://socialhub.activitypub.rocks/t/fep-ef61-portable-objects/3738

#fediverse #FEP #PortableObjects #FEPEF61

Process on FEPs

https://event-federation.eu/2026/06/19/process-on-feps/

Process on FEPs

https://event-federation.eu/2026/06/19/process-on-feps/

Following a thread is now available in the latest version of #HolosSocial. #ActivityPub already lets you follow an object, not only an account, so a Follow can target a post. You then receive new replies, even from accounts you do not follow. A thread is short-lived, so the Follow uses the standard endTime property to expire on its own. It works best when other servers support it, that's why I want to turn it into a #FEP.

For people curious about the idea: https://tom79.dev/posts/follow-a-note/

Following a thread is now available in the latest version of #HolosSocial. #ActivityPub already lets you follow an object, not only an account, so a Follow can target a post. You then receive new replies, even from accounts you do not follow. A thread is short-lived, so the Follow uses the standard endTime property to expire on its own. It works best when other servers support it, that's why I want to turn it into a #FEP.

For people curious about the idea: https://tom79.dev/posts/follow-a-note/

FEP-5219: Groups and permissions has been added to the FEP repository.

#fep #fep_5219

RE: https://mitra.social/objects/019e87e9-62a6-71d1-8edc-3a8a63e96c9f

FEP-5219: Groups and permissions has been added to the FEP repository.

#fep #fep_5219

RE: https://mitra.social/objects/019e87e9-62a6-71d1-8edc-3a8a63e96c9f

FEP-f228: Backfilling conversations has been updated:
https://codeberg.org/fediverse/fep/pulls/853

I added tootik and Lemmy to the implementation list and did a little cleanup. This FEP feels complete, so I am requesting final comments.

Full text:

https://fediverse.codeberg.page/fep/fep/f228/

#fep_f228 #fep #fedidev

FEP-f228: Backfilling conversations has been updated:
https://codeberg.org/fediverse/fep/pulls/853

I added tootik and Lemmy to the implementation list and did a little cleanup. This FEP feels complete, so I am requesting final comments.

Full text:

https://fediverse.codeberg.page/fep/fep/f228/

#fep_f228 #fep #fedidev

Recurring Events in Federation

https://event-federation.eu/2026/05/15/recurring-events-in-federation/

Recurring Events in Federation

https://event-federation.eu/2026/05/15/recurring-events-in-federation/

Addendum: Another possible outcome of this prototype could be opening an FEP to include additional details inside nodeinfo, such as links to annual reports, membership price, etc.

Does this already exist? Would anyone be interested in helping write it?

Let me know!

#fediverse #FEP #FediAdmins #MastoAdmins

Addendum: Another possible outcome of this prototype could be opening an FEP to include additional details inside nodeinfo, such as links to annual reports, membership price, etc.

Does this already exist? Would anyone be interested in helping write it?

Let me know!

#fediverse #FEP #FediAdmins #MastoAdmins

Hey @[email protected],

we are looking into your #Go #Activitypub library to implement federation in #LAUTI

One thing we need to do is implement the #FEP 8a8e by @[email protected]

Do you have time for a quick call to get an overview?

Hey @[email protected],

we are looking into your #Go #Activitypub library to implement federation in #LAUTI

One thing we need to do is implement the #FEP 8a8e by @[email protected]

Do you have time for a quick call to get an overview?

FEP-8b32 (Object Integrity Proofs) is getting updated: https://codeberg.org/fediverse/fep/pulls/839

I added two new requirements:

- Objects identified using fragment IDs SHOULD NOT have integrity proofs. It is enough to secure the top-level document.
- Verifiers SHOULD ignore proofs that use unsupported algorithms and verification methods. This requirement provides forward compatibility, which is important because sooner or later we will need to use different algorithms.

#fep_8b32 #fep #fedidev

FEP-8b32 (Object Integrity Proofs) is getting updated: https://codeberg.org/fediverse/fep/pulls/839

I added two new requirements:

- Objects identified using fragment IDs SHOULD NOT have integrity proofs. It is enough to secure the top-level document.
- Verifiers SHOULD ignore proofs that use unsupported algorithms and verification methods. This requirement provides forward compatibility, which is important because sooner or later we will need to use different algorithms.

#fep_8b32 #fep #fedidev

@reiver

The only thing that I would bring in regarding emoji use in display names is #a11y issues if there are a lot of them. I'd say recommended practice should be to have 1 and max. 2 emoji in the name, so #screenreaders don't have read a long shebang you sometimes see on 'funny' display names.

But perhaps someone better versed in #accessibility issues for the visually impaired can chime in on this #ActivityPub #FEP (and perhaps other FEP's too), if this is a real issue. A "fediverse accessibility best-practices" may exist as well (somewhere).

#SX #SocialCoding #AskFedi

@reiver

The only thing that I would bring in regarding emoji use in display names is #a11y issues if there are a lot of them. I'd say recommended practice should be to have 1 and max. 2 emoji in the name, so #screenreaders don't have read a long shebang you sometimes see on 'funny' display names.

But perhaps someone better versed in #accessibility issues for the visually impaired can chime in on this #ActivityPub #FEP (and perhaps other FEP's too), if this is a real issue. A "fediverse accessibility best-practices" may exist as well (somewhere).

#SX #SocialCoding #AskFedi

@nicol

> if the challenge of knowing what Fediverse Apps implement which bit of the spec is a blocker, is there a standard way to declare which bits of the spec an app is conformant in?

The #ActivityPub #FEP process keeps a list of implementations, in each of its documents. The FEDERATION.md was once introduced as "something to start with before going more complex wrt introspection", a temporary bandaid to bring improvement. Its adoption and use, and later its description as a recommended practice are going very slow though. Still, a very useful practice, compared to lacking such doc and perusing foreign codebases for the info.

> does the Fediverse need a democratic membership org that funds core maintenance of FEP and pays for some of the core community maintainers to keep looking after the ecosystem.

That might be a good solution. For part of a much bigger problem. No #funding bakes bread yet.

I addressed this with @nlnet in the past, and intend to bring it up again next week.

@nicol

> if the challenge of knowing what Fediverse Apps implement which bit of the spec is a blocker, is there a standard way to declare which bits of the spec an app is conformant in?

The #ActivityPub #FEP process keeps a list of implementations, in each of its documents. The FEDERATION.md was once introduced as "something to start with before going more complex wrt introspection", a temporary bandaid to bring improvement. Its adoption and use, and later its description as a recommended practice are going very slow though. Still, a very useful practice, compared to lacking such doc and perusing foreign codebases for the info.

> does the Fediverse need a democratic membership org that funds core maintenance of FEP and pays for some of the core community maintainers to keep looking after the ecosystem.

That might be a good solution. For part of a much bigger problem. No #funding bakes bread yet.

I addressed this with @nlnet in the past, and intend to bring it up again next week.

@abeorch @gary

There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..

The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.

https://social.coop/@smallcircles/116379158584600016

PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..

https://social.coop/@smallcircles/116402592862958767

Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.

#SX #SocialCoding #SocialWeb

@abeorch @gary

There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..

The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.

https://social.coop/@smallcircles/116379158584600016

PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..

https://social.coop/@smallcircles/116402592862958767

Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.

#SX #SocialCoding #SocialWeb

#BoostFediForwards :boosts_appreciated:

In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?

Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?

Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!

The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.

Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.

https://delightful.coding.social/delightful-fediverse-experience/

#UrgentPlatitude: Our #future is created today, not #tomorrow.

https://socialhub.activitypub.rocks/t/vacancy-commons-custodians-help-increase-fep-sustainability-and-progress/8640

See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.

https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836

https://social.coop/@smallcircles/116379158584600016

#FediJobs #Vacancy #Job #Jobs #Volunteer

#BoostFediForwards :boosts_appreciated:

In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?

Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?

Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!

The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.

Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.

https://delightful.coding.social/delightful-fediverse-experience/

#UrgentPlatitude: Our #future is created today, not #tomorrow.

https://socialhub.activitypub.rocks/t/vacancy-commons-custodians-help-increase-fep-sustainability-and-progress/8640

See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.

https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836

https://social.coop/@smallcircles/116379158584600016

#FediJobs #Vacancy #Job #Jobs #Volunteer

cc @evan relating to earlier #TagsPub discussion we had on the matter.

This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.

Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.

More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.

#NoBots #nobot #fedi22 #NoTagsPub #Botiquette

cc @evan relating to earlier #TagsPub discussion we had on the matter.

This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.

Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.

More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.

#NoBots #nobot #fedi22 #NoTagsPub #Botiquette

@aslakr @leanderlindahl

🤔 Off-topic reformulation of the procedure in general terms.. In areas where PeerTube isn't post-facto interop leader itself, it should hope a reasonably broadly adopted #FEP consensus exists, or follow the post-facto leader in that particular application area and accept the upstream dependency to that part of the #ActivityPub specs the leader owns (and hopefully cares for, beyond their own needs, with good design and documentation).

@aslakr @leanderlindahl

🤔 Off-topic reformulation of the procedure in general terms.. In areas where PeerTube isn't post-facto interop leader itself, it should hope a reasonably broadly adopted #FEP consensus exists, or follow the post-facto leader in that particular application area and accept the upstream dependency to that part of the #ActivityPub specs the leader owns (and hopefully cares for, beyond their own needs, with good design and documentation).

FEP-9f9f: Collections has been published:

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

It seems to cover the basics, let me know if I missed anything.

#fep

RE: https://socialhub.activitypub.rocks/ap/object/4f422d20555601ca6e73b35b830cf74d

FEP-9f9f: Collections has been published:

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

It seems to cover the basics, let me know if I missed anything.

#fep

RE: https://socialhub.activitypub.rocks/ap/object/4f422d20555601ca6e73b35b830cf74d

I know there is some ongoing work, eg. https://socialhub.activitypub.rocks/t/fep-07d7-a-custom-url-scheme-and-web-based-protocol-handlers-for-linking-to-activitypub-resources/3588.

Some people will argue against this, but the Atmosphere is (slowly) decentralizing (https://stefanbohacek.online/@stefan/116126040489956521) and it will soon run into the same issues we're dealing with, like being asked to log in when you click a link to a post that's not on your server/AppView/what have you.

I'm sure they will figure this out, with their deep crypto VC money pockets, but if we can figure this out first, it could really give us a major advantage.

#fediverse #mastodon #FediDevs #MastoDevs #FEP #standards