#fep — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fep, aggregated by home.social.
-
Recurring Events in Federation
Just a short update to let you know things are still moving forward! The last months have been used to gain insight how and to which extend recurring events and series of events (as well as related events in general) might work in federation and be of benefit. This has involved a lot of exploration, design iteration, and discussions with people who are building or operating in this space. More interviews are planned to deepen this understanding further. If you want to have a chat about this, […]https://event-federation.eu/2026/05/15/recurring-events-in-federation/
-
Recurring Events in Federation
Just a short update to let you know things are still moving forward! The last months have been used to gain insight how and to which extend recurring events and series of events (as well as related events in general) might work in federation and be of benefit. This has involved a lot of exploration, design iteration, and discussions with people who are building or operating in this space. More interviews are planned to deepen this understanding further. If you want to have a chat about this, […]https://event-federation.eu/2026/05/15/recurring-events-in-federation/
-
Recurring Events in Federation
Just a short update to let you know things are still moving forward! The last months have been used to gain insight how and to which extend recurring events and series of events (as well as related events in general) might work in federation and be of benefit. This has involved a lot of exploration, design iteration, and discussions with people who are building or operating in this space. More interviews are planned to deepen this understanding further. If you want to have a chat about this, […]https://event-federation.eu/2026/05/15/recurring-events-in-federation/
-
Recurring Events in Federation
Just a short update to let you know things are still moving forward! The last months have been used to gain insight how and to which extend recurring events and series of events (as well as related events in general) might work in federation and be of benefit. This has involved a lot of exploration, design iteration, and discussions with people who are building or operating in this space. More interviews are planned to deepen this understanding further. If you want to have a chat about this, […]https://event-federation.eu/2026/05/15/recurring-events-in-federation/
-
Recurring Events in Federation
Just a short update to let you know things are still moving forward! The last months have been used to gain insight how and to which extend recurring events and series of events (as well as related events in general) might work in federation and be of benefit. This has involved a lot of exploration, design iteration, and discussions with people who are building or operating in this space. More interviews are planned to deepen this understanding further. If you want to have a chat about this, […]https://event-federation.eu/2026/05/15/recurring-events-in-federation/
-
UNLZ. La izquierda recupera en sociales la secretaría de género
-
https://www.europesays.com/es/535415/ Noticias breves. 5 de mayo de 2026 #Actualidad #breves #Cofares #ComunidadDeMadrid #ES #España #FEP #Health #MinisterioDeSanidad #Salud #Sanitas #Spain
-
Commercial Wire and Cable Market in the Netherlands | Report – IndexBox https://www.byteseu.com/1976665/ #Braid #BuildingAutomationSystems(BAS) #CommercialWireAndCable #DataCenterRackToRackConnectivity #ElectronicsMarketReport #FEP) #FiberOptic(SingleMode #FirePerformanceStandards(CM/CMR/CMP #forecast #Insulation/JacketingMaterials(XLPE #LSZH #MachineAndProcessControlWiring #MarketAnalysis #MultiMode) #Netherlands #PowerDistributionWithinBuildings #pvc #Shielding&Armoring(Foil #SWA)
-
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!
-
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!
-
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!
-
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!
-
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!
-
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?
-
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?
-
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 (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 (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 (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. -
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).
-
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).
-
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).
-
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).
-
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).
-
> 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.
-
> 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.
-
> 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.
-
> 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.
-
> 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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
#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.
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
-
#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.
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
-
#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.
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
-
#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.
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
-
#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.
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
🤔 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).
-
🤔 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).
-
🤔 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).