This is part of why concepts like #JsonLD Framing ( https://www.w3.org/TR/json-ld11-framing/ ) exist, but these sorts of tools come with substantive performance penalties and increases in complexity.
But we can absolutely 100% address this in something like a #FEP.
I don't even think it would be especially hard.
Something I'm chewing on.
Oh and there *is* a #FEP that covers this, last edit 3 weeks ago
#FEP5624 Per-object reply control policies
https://codeberg.org/fediverse/fep/src/branch/main/fep/5624/fep-5624.md
Hat tip Evan who I don’t necessarily bring into my reply chain, but saw post about this just now.
That's giving #meta far too much credit. More likely scenario is they will start declaring changes to their bespoke version of the protocol, and the #fep folks will scramble to catch up and or futilely reign it in.
Instances friendly with #threads will make the change, and the slow fork away will begin.
Idle thought — what happens when a server is temporarily down? According to #ActivityPub spec, sending instances should re-deliver:
> For federated servers performing delivery to a third party server, delivery SHOULD be performed asynchronously, and SHOULD additionally retry delivery to recipients if it fails due to network error.
Deliberately vague by design, I wonder if there's an #fep that specifies something more, e.g. exponential backoff, batching, when to give up, etc.
@tw1tch Fediverse Enhancement Proposal: https://codeberg.org/fediverse/fep (#FEP)
Basically it's a way of creating consensus across projects and a grassroots evolution process for the fediverse.
@strypey sorry, how does connecting with other networks relate to moving services with connections intact?
#XMPP has #XEP, for servers to specify what features they support. Unless AP servers start enforcing that supported #FEP s be specified, you don't know that a new kid (bully?) on the block will both federate and support account portability (or when they stop supporting something).
In “What are plans for?” (1989) Philipp #Agre and @Meaningness dismantle #FEP 20 years before #Friston et al proposed it.
@dada_drummer There's the makings here of a really excellent #FEP on how to address this sort of challenge in #ActivityPub, come to think…
@jrp In general:
* Various posters in the #fediverse under a variety of hashtags
* #SocialHub
* The public #SWICG mailing list and discussions
* The #Mastodon github repos
* The #w3c github repos
* The #FEP repos
#fediverse #socialhub #swicg #mastodon #w3c #fep
@smallcircles @trwnh
@fedidevs@a.gup.pe
@fedidevs@venera.social
That's great news!
And the discussions continue at:
https://socialhub.activitypub.rocks/
Thanks for your tirelessly consistent commitment to advancing #Fediverse adoption and #ActivityPub development for the past several years too - your efforts continue to be an inspiration for all concerned #Fedizens!
#tallship #FEP #SocialHub #SocialCoding #swicg #FOSS #fediverse-city:matrix.org
⛵
.
#fediverse #activitypub #fedizens #tallship #fep #socialhub #socialcoding #swicg #foss
That's a great suggestion, and I encourage you to consider submitting a draft. It's basically the same as the #IETF process and once the FEP ball is rolling it is self-correcting.
Anyone can participate here: https://codeberg.org/fediverse/fep and this could aid in platforms facilitating migration between any instance instead of just away from mastodon during this increasing exodus trend from it.
FEP is the way forward.
#tallship #Fediverse #ActivityPub #FEP
⛵
.
#ietf #tallship #fediverse #activitypub #fep
Here's someone who's really thinking about things. I wish he wouldn't brand his button masto but he makes an attempt to justify the use of that brand - his heads in the right place though 👍
https://jeremy.hu/the-case-for-native-handling-of-fediverse-actions/
As far as the answer to his wisdom in the last paragraph though...
https://codeberg.org/fediverse/fep
And most (non-headless) Fediverse platforms do support mastopub API, so the button will prolly work with #Pleroma, #Friendica, Etc.
#tallship #Fediverse #FEP #ActivityPub @jeremy
⛵
.
#pleroma #friendica #tallship #fediverse #fep #activitypub
I don't suppose anyone has a link to either #ActivityPub documentation about groups or whatever #FEP mentions them?
https://healthexec.com/topics/healthcare-management/healthcare-policy/unitedhealthcare-cut-back-prior-authorization-paperwork?utm_source=newsletter&utm_medium=cvb_news Others need to do the same…it is just all about greed… #insurance #healthinsurance #fepbcbs #bcbs #fep
#insurance #healthinsurance #fepbcbs #bcbs #fep
El Festival Estéreo Picnic #FEP sigue siendo uno de los eventos peor organizados de Colombia. Las bandas comienzan a tiempo y el sonido es muy bueno, y eso está muy bien, pero qué desastre todo lo demás: la distribución del lugar, el manejo de tráfico, las comidas, el lugar mismo. Hay que hacer una inversión enorme de energía para poder realmente disfrutar de la música. Me alegra no haberles dado ni un solo peso este año.
How I might write an #FEP for this…
Specify requiring an Actor that represents the Server and can be found at a well-known (webfinger or equivalent) location that contains the metadata.
This can be included in the user information or separated.
Then you have essentially a better specified version of a user-agent. "I am running the glitch fork of Mastodon x.y," "I use limited federation," "I support channels based on a microsyntax," "I have implemented FEP-1234," etc.
@rabble Also see the contemporary comments by garrinm on the #FEP for #IdentityProofs here:
https://socialhub.activitypub.rocks/t/fep-c390-identity-proofs/2726/21