#fep — Public Fediverse posts

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/

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/

Recurring Events in Federation

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

UNLZ. La izquierda recupera en sociales la secretaría de género

https://fed.brid.gy/r/https://periodismodeizquierda.com/unlz-la-izquierda-recupera-en-sociales-la-secretaria-de-genero/

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!

#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

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

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?

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?

I'm often inspired to share my thoughts, expound upon something I've read that sparks that inspiration, or pose a bit of socratric reasoning in discourse. Sometimes we actually edjumacate ourselves by asking the tough questions rhetorically. Sometimes it's even more effective if we share those quests with others. It can be a phrase, a paragraph, or a sentence that ignites that quest for understanding within me, and whether I'm simply working it through it myself for my own sake or a genuine desire to share some kind of enlightenment or wisdom with others, I usually feel better doing it in the public eye at the end of the day when all is said and done.

There's a bit of a stir in the Fediverse. Darnell offers us some valuable considerations and specifics in the link to his blog post below.

For me, I think the most interesting part when you read between the lines is, ...

> This latest move could be a way for Meta to use Threads to thwart any potential ActivityPub powered rivals in the Fediverse (like Pixelfed, Friendica & WordPress).

Note that nowhere is masto even listed there - it's insignificant. The #ActivityPub powered rivals in the #Fediverse cited are what have been considered for many years the direct corollaries to #InstaSPAM and #Faceplant, respectively, which of course are the exceedingly capable platforms #Pixelfed and #Friendica.

In all of that, considering that #WordPress is the big game changer here of most recent repute, enjoying a 42% market share of all websites worldwide certainly blows away anything Meta has to offer, but even though it is past the 4th of May, Faceplant and InstaSPAM still do comprise the #phantom_menace flavor of this week.

- Pixelfed has a very nice interface for browsing images. Unlike InstaSPAM however, there isn't this overwhelming nausea attending user accounts with duck-ass selfie-kisses blown into bacteria laden bathroom mirrors, or the overwhelming shitposting of memes scraped from other non-verbal teenage neanderthals. So yes, there's less traffic, typically, but actual photos of things that are actually important and relevant to the people posting them, and more so, liked and boosted by people who appreciate such sentimentalism or professional art. On the downside, is Pixelfed's relatively lackluster editor that fails to provide the poster with paragraph breaks in the WebUI with any reliability, it's mastocrap-like paltry 500 character limit per post, and a complete lack of formatting capabilities (i.e., Markdown or BBCode, Etc.). Having said that, the 500 character limit is easily remedied in a single entry of a config file, which is a blessing to many who have resorted to using the #A11Y alt-text fields to provide the descriptions and narratives for images uploaded, but the other sophomoric qualities of the editor leave massively huge run on paragraphs for the reader to endure - like this one, for example :p

Other awesome projects either spawned directly from, or inspired by the success of Pixelfed are the FediDB research database, which although pretty, leaves much to be desired with respect to completeness; Sup, a client/server federated chat app model; Loops, a closed beta service that aims to position itself as a replacement for, and similar to YouTube shorts; and PubKit, a tool service in closed beta at this time that attempts to service the same or similar tests that the production https://funfedi.dev/ resource does.

- Friendica was once a platform that closely mimicked the look and feel of Faceplant. And then it wasn't, as the Faceplant monoverse continued to evolve in look and feel, and Friendica lagged in what I typically refer to as "Prettiness". Those days are long past, Friendica looks better and better with each and every successive release, and there's an obvious effort on improving the UX for users, making it much more intuitive, and the UI, tending to the "Prettiness" that I do indeed place so much emphasis on.

Once the original darling of the Fediverse, Friendica is once again at the top of the heap with a few others. This does not include the increasingly marginalized masto brand, as more and more adoptees continue to turn their backs to that has-been flagship.

After increasingly pervasive betrayals of both the #FOSS and #DeSoc philosophies and advocates for the past couple of years, eventually revealing it's own EEE aspirations by actively conflating it's masto brand and registered trademarks with that of Fediverse. Even worse, overtly engaging in an onboarding scheme that actively funnels new #Fedizens to one masto machine in particular, in grand, deprecated silo fashion, the masto corporation has populated one of the largest monolithic vertical gardens in the Fediverse itself. The sad part is that, being just another twitter clone, it still has no sense of community and offers nearly a million users a single point of failure. Ouch!

This masto mega-silo problem becomes even less relevant when you visit the Friendica page above, and gloss over the phenomenal feature set and attention given to interoperability with a shopping list of other platforms, protocols, and clients, including:

RSS/Atom, StatusNet, GNU social, Diaspora, SMTP/IMAP, Bluesky, Tumblr, GNU Social, pump.io, Libertree, Blogger, WordPress, Twidere, AndStatus, Bitlbee, Choqok, Frentcl, Gwibber, Hotot, IdentiCurse, Pidgin/Purple, Mustard, Pino, TTYtter.

Now, you might note that Twitter/X has walled off its deprecated monolithic garden, but that doesn't mean that the client and other toolsets that work with those APIs don't still work just fine with Friendica. And we're not even stating the obvious here - ActivityPub clients like Husky, Fedilab, and Sengi work just fine with Friendica, including Friendiqa and Relatica - two fine examples among the numerous choices you have for native Friendica apps for Android and desktop.

For more of an in-depth read on Relatica, here's an article I published a while back

The second most interesting thing that Darnell mentions, I think, has to do with the verbiage in which he characterizes Existing and traditional Fediverse powered platforms. Rivals. He calls them, "...ActivityPub powered rivals". Hmmmm....

I do believe that's the first time I've actually heard it put quite like that. But it's true. to be certain, it wasn't, not by a longshot, just a little while ago, but now? Well, it's nothing that we've done here in the Fediverse, except for continue to just ignore what's going on with the #subjugated_chattel that have all but succumbed to the #Sunnyvale_Syndrome, and get on with the good work of building and #dogfooding FOSS. But, ...

It's got a lot to do with what you might call interlopers, carpetbaggers, snakeoil salesmen, infestation, or maybe just plain old encroachment of aged and abusive #dreadnoughts into the Fediverse that stubbornly adhere to their deprecated, monolithic silo model of privacy farming technologies.

Hitherto all of these ActivityPub refits and forays into a Privacy mindful and respecting network of social communications systems, people kept using terms like Alternatives, for ActivityPub powered platforms such as the three main platforms mentioned in Darnell's blog article.

Now, they're being elevated to the rank of Rivals? But we, we, didn't do anything!

Neither did the GPL'd Linux Kernel - it just continued to do what FOSS does. It doesn't care what thinks it may be in competition with, or what considers it a threat, or rival or yes, REPLACEMENT for things like Faceplant and InstaSPAM.

Yes, FOSS just lumbers and chugs right along, relatively oblivious to whatever the proprietary, closed source contemporaries think of it - with respect to Linux, It actually entered the jurisdiction of a market dominated by Microsoft, IBM, and a couple of others, was lampooned and ridiculed, until it was considered a Cancer, by Microsoft CEO Steve Ballmer, but this wasn't Microsoft or others encroaching into a space where only Linux and the BSDs resided...

This time it is different, because it's the other way around, but the end result will be the same. In the meantime, the perceived hostile invader, at the moment, is Zuckerberg's Meta. This isn't an EEE in the works, it's a desperate attempt to reach and hold onto the the coping that lines the deep end of a swimming pool which InstaSPAM and Faceplant must learn to swim in, and yet cannot - in the meantime, until it is able to tread those waters, it is feebly dog-paddling toward the edge where a handhold can be made while it is fitted with water-wings.

Even though both Tom (everyone's friend) and Eugen are happily traveling around the world snapping photographs and flirting with photography as a hobby, #Mark_Zuckerberg really doesn't wanna be #Myspaced.

If you don't move, you atrophy.

But Friendica, WordPress, and Pixelfed? Well, they're just FOSS, and they're just doing what FOSS does - exist, improve, and evolve. independently and irrespective of commercial threats by would be competitors.

Existing Fediverse platforms continue to onboard new Fedizens hourly, that's not slowing down, and it isn't going to either. Some of these n00bs are straddling the fence until they get their sea legs, existing in both worlds, while others are just cutting ties with the deprecated monolithic silos and jumping into the pool head first.

This phenomena of adoption and the logarithmic increase in onboarding and the deployment of new Fediverse instances is only going to pick up pace as the masses of users on platforms like #Threads and #Bluesky continue to become aware of the Fediverse, and the freedoms they can enjoy in social communication through leveraging WordPress, Pixelfed, and Friendica (and it goes without saying, all the rest of the wonderful platforms too).

With a community facade that pretended to hold the reigns of masto having been dropped, leaving a new 501(c)(3) masto corporation in the US steered by the likes of Twitter founders themselves, the steam is running out on that brand, and although Meta, via Threads, is certainly welcome to participate in the #FEP process (they actually are), there's really no foothold with which they can insert a toe and dictate very much at all that the community itself isn't inclined to adopt already, independently and without concern of capture by well funded special interest groups - like the new US masto corp.

But in closing, let's get back to why all of this doesn't even really matter where existing traditional Fediverse platforms are concerned - or the millions of users actively engaged on those thousands of hubs and instances:

Because it's FOSS, it evolves organically, and just doesn't care about that kind of stuff, lolz.

#tallship

⛵

.

RE: https://one.darnell.one/users/darnell/statuses/112405069391666443

@darnell

@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

@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

@hrast I've seen this passing by in #fediverse discussions many times, but always in fleety timelines.. aka lost-in-time no further #ideation lines :)

This is a good #idea to describe in more detail in the ideas inbox. Staging ground for the #FEP process and #SocialHub #ActivityPub developer community, if there are people willing to pick them up. And then in turn perhaps staging ground for further standardization by #W3C #SocialCG.

https://codeberg.org/fediverse/fediverse-ideas/issues

#SX #SocialCoding #SocialWeb

@hrast I've seen this passing by in #fediverse discussions many times, but always in fleety timelines.. aka lost-in-time no further #ideation lines :)

This is a good #idea to describe in more detail in the ideas inbox. Staging ground for the #FEP process and #SocialHub #ActivityPub developer community, if there are people willing to pick them up. And then in turn perhaps staging ground for further standardization by #W3C #SocialCG.

https://codeberg.org/fediverse/fediverse-ideas/issues

#SX #SocialCoding #SocialWeb

@hrast I've seen this passing by in #fediverse discussions many times, but always in fleety timelines.. aka lost-in-time no further #ideation lines :)

This is a good #idea to describe in more detail in the ideas inbox. Staging ground for the #FEP process and #SocialHub #ActivityPub developer community, if there are people willing to pick them up. And then in turn perhaps staging ground for further standardization by #W3C #SocialCG.

https://codeberg.org/fediverse/fediverse-ideas/issues

#SX #SocialCoding #SocialWeb

@hrast I've seen this passing by in #fediverse discussions many times, but always in fleety timelines.. aka lost-in-time no further #ideation lines :)

This is a good #idea to describe in more detail in the ideas inbox. Staging ground for the #FEP process and #SocialHub #ActivityPub developer community, if there are people willing to pick them up. And then in turn perhaps staging ground for further standardization by #W3C #SocialCG.

https://codeberg.org/fediverse/fediverse-ideas/issues

#SX #SocialCoding #SocialWeb

@hrast I've seen this passing by in #fediverse discussions many times, but always in fleety timelines.. aka lost-in-time no further #ideation lines :)

This is a good #idea to describe in more detail in the ideas inbox. Staging ground for the #FEP process and #SocialHub #ActivityPub developer community, if there are people willing to pick them up. And then in turn perhaps staging ground for further standardization by #W3C #SocialCG.

https://codeberg.org/fediverse/fediverse-ideas/issues

#SX #SocialCoding #SocialWeb

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

@cwebber @spritelyinst

After a few years of following your invaluable input, I have to ask whether you've participated in the https://codeberg.org/fediverse/fep community which addresses these very issues?

If not, then why not?

If so, what have been your personally most significant contributions to this #DeSoc and #legacy_silo_averting free namespsce?

Kindest regards,

Bradley

#tallship #FOSS #Fediverse #FEP #lemmur #Spritely #ActivityPub #ActivityStreams #extending #extensions #engagements

⛵

.

Having @mikedev totally onboard with FEP-ef61 is a super big deal, not to mention that only fully open standards will be implemented, averting capture by special interest lobbies.

I see cracks forming across the ice of the barren mastolake ;) 🪵🪓

https://fediversity.site/channel/streams?mid=https://fediversity.site/item/d9dd01e1-96fd-4306-9bd9-27c2ebe1a1d5

#tallship #FOSS #Fediverse #Streams #ActivityPub (and beyond) #DeSoc #Nomadic_Identity #FEP

⛵

.

First preprint about my work at Schrödinger:

We show how to predict ligand efficacy via absolute binding free energy perturbation on different receptor conformations — confirming and utilizing the principle that the functional response of a receptor is mainly determined by the thermodynamics of ligand binding.

https://chemrxiv.org/engage/chemrxiv/article-details/64b1cccaae3d1a7b0db45aa8

#FEP #FreeEnergy #LigandEfficacy #GPCR #DrugDiscovery #DrugDesign #Thermodynamics #GPCRs #BindingFreeEnergy

#ThoughtProvoker :blobhyperthink:

App-centrism is a re-centralization force in the #ActivityPub fediverse.

For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.

Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.

The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.

The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.

#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.

• the first stable release of Mitra with full support for that level of nomadicity is officially rolled out
• silverpill declares that everything necessary for Hubzilla/(streams)/Forte-level nomadic identity via nothing but ActivityPub is cast into FEPs and finalised

• Situation:
  
  • You have an account on digitalcourage.social with one channel, [email protected].
  • You want to move to troet.cafe.
• Step 1: You create an account on troet.cafe.
• Step 2: There can't be accounts with no channels. You have to add a channel.
  So you choose to move your channel [email protected] from digitalcourage.social to troet.cafe.
• Step 3: Your channel [email protected] is cloned over to troet.cafe.
• Situation now:
  
  • You have an account on digitalcourage.social with the main instance of your channel; its identity is [email protected].
  • You have an account on troet.cafe with a clone of your channel; its identity is still [email protected].
• Step 4: All data on your channel is synchronised over from your main instance on digitalcourage.social to your clone on troet.cafe. Posts, images, other files, followers, followed, settings, lists, filters etc. etc. pp. Everything.
• Now the main instance and the clone are identical.
  Up until here, the process of moving is the same as the process of cloning. What follow is exclusive to moving.
• Step 5:
  
  • The clone on troet.cafe is promoted to main instance.
  • As there can be only one main instance for each channel, the former main instance on digitalcourage.social is demoted to clone.
• Situation now:
  
  • You have an account on digitalcourage.social with a clone of your channel, formerly the main instance; its identity is [email protected].
  • You have an account on troet.cafe with the main instance of your channel, formerly a clone; its identity is [email protected].
• Step 6: All your connections on servers of nomadic software are changed from [email protected] to [email protected], both locally on the servers that you are on and locally on the servers that they are on.
• Step 7 (AFAIK, this only happens on (streams) and Forte in reality): All your outbound connections ("followed") on servers running non-nomadic software receive a follow request from [email protected] which, to them, is an all-new, independent identity.
• The actually move is done. What follows is the clean-up that really makes the move a move, namely taking care that nothing is left behind in the old location.
• Step 8: When these last steps are finalised, your clone on digitalcourage.social is deleted. After all, you wanted to move, not to clone.
• Step 9: As your account on digitalcourage.social has no channel on it anymore, the whole account is deleted.

* FEP-ef61: Portable Objects

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

* FEP-61cf: The OpenWebAuth Protocol

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

"Many of these [Zot/Nomad] ]ideas are being ported to ActivityPub in the form of Fediverse Enhancement Proposals (FEPs).

... Streams ... is working with Mitra to create the first implementation of nomadic identity over ActivityPub. This includes working on several related FEPs about identity proofs and conversation containers.

Our goal is for these technologies to spread throughout the fediverse."

https://opennomad.net/page/nomad/home

#fediverse #ActivityPub #Zot #Nomad #FEP

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

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

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

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

@phnt @happy-programming @Profpatsch

What was also interesting re: #GNUSocial is the unfortunately retracted #ActivityPub #FEP on Unbound Groups i.e. groups (or organizations) that are not bound to a single instance.

See #FEP2100 at https://codeberg.org/fediverse/fep/src/branch/main/fep/2100/fep-2100.md

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

New #FEP view:

https://socialhub.activitypub.rocks/t/proposal-explore-page-with-filterable-fep-table/8572/3?u=naturzukunft

#activitypub

Follow account, but only its posts about [that].
Follow account, but only its posts not about [that].
#fep #fediverse 😈

FEP website now displays the number of implementations for each implementable proposal:

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

These numbers are based on the information that authors provide in the "Implementations" section of a proposal.

By default, proposals are informational, so authors need to opt in by adding type: implementation to the metadata block.

#fep #fedidev

@silverpill @raphael @julian @mariusor

The killer app for the fediverse is not nomadic identity. That is either a protocol capability or may refer to an Identity Management app, a solution design.

Problem is, it is no use discussing here. No convergence takes place, other than spontaneous / random convergence. But it does not lead anywhere, not to a common consensus. Not to robust foundations to build on without continuous worries that things break. Microblog communications does not support this, and lacking that support manual processes are needed.

Even the #ActivityPub #FEP only offers convergence to certain extent. The process is a band-aid, a best-we-have.

In analogy of the horserace, spontaneous convergence and ad-hoc alignment on FEP puzzle pieces by implementers equates to the horseback riders figuring out some basic rules to avoid serious accidents. But this FEP adoption at the same time warps the track, hems them in, alters reality and the future.

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

Recently, there was a discussion about generic #ActivityPub servers. Several people claimed that they were working on one, but it turned out that their "generic" servers only support activities defined in the ActivityPub specification. Such a server shouldn't be called generic. It is not difficult to build, neither it is an interesting concept because competing protocols (e.g. Nostr) already offer much more.

I've been writing a #FEP that describes how to build a real generic server. It is not finished yet, but I feel like now is a good time to publish it:

FEP-fc48: Generic ActivityPub server

This kind of server:

- Can process any object type, and can process non-standard activities like EmojiReact.
- Compatible with FEP-ae97 clients.
- Does not require JSON-LD.

I attempted to implement it when I was researching security properties of FEP-ae97 API: https://codeberg.org/silverpill/fep-ae97-server. Back then I didn't know what to do with side effects, but now I think that we can simply force clients to specify them.

Special thanks to @mariusor and @trwnh for their input.

#C2S

There's now a proper rendered web interface for FEPs at https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink, https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.

Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.

I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)

#fedidev #fep #fediverse #ActivityPub

@toddsundsted

Btw. #GrassrootsStandards and standardization processes (such as the #FEP process) are a topic of Social coding commons and Social experience design, and we have a multi-author blog at https://coding.social ..

If you wish you might publish these results there as a report to spread about.

#SX #SocialCoding #SocialWeb #ActivityPub