Fediverse Enhancement Proposals
Fediverse
7
Posts
6
Posters
8
Views
-
A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.
The FEP Process is an initiative of the SocialHub developer community, a liaison of the W3C Social Web Incubator Community Group.
Discovered this today. If you're on the developer side of things or are interested in how the Fediverse / ActivityPub is being built and enhanced, take a look at this codeberg repo.
-
A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.
The FEP Process is an initiative of the SocialHub developer community, a liaison of the W3C Social Web Incubator Community Group.
Discovered this today. If you're on the developer side of things or are interested in how the Fediverse / ActivityPub is being built and enhanced, take a look at this codeberg repo.
Thats super cool!
-
A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.
The FEP Process is an initiative of the SocialHub developer community, a liaison of the W3C Social Web Incubator Community Group.
Discovered this today. If you're on the developer side of things or are interested in how the Fediverse / ActivityPub is being built and enhanced, take a look at this codeberg repo.
Indeed, this is where the majority of improvements to the Fediverse are shared for archival.
The very way Lemmy Piefed Mbin and NodeBB can communicate and synchronize communities is detailed in those FEPs. Check out FEP 1b12.
-
Hi Melroy from Mbin. It's true what you are saying Julian. These FEPs forms the basic of the fediverse.
But at the same time I hate those FEPs alot. I would rather see a more detailed and better described ActivityPub protocol v2.0 or 3.0. My point is that the current ActivityPub is way too vague.And we need dozens of various FEPs to get the features we actually need and want to get the basis features of today. Currently it's hard to read, there is no single document. No single source of truth. All FEPs are actually optional to implement. And it's a mess.
Could you imagine if an internet standard like http or TCP was documented like this? It would never have worked.
-
A Fediverse Enhancement Proposal (FEP) is a document that provides information to the Fediverse community. The goal of a FEP is to improve interoperability and well-being of diverse services, applications and communities that form the Fediverse.
The FEP Process is an initiative of the SocialHub developer community, a liaison of the W3C Social Web Incubator Community Group.
Discovered this today. If you're on the developer side of things or are interested in how the Fediverse / ActivityPub is being built and enhanced, take a look at this codeberg repo.
I knew that there was some kind of unifying force in the Fediverse. Thanks for sharing it.
-
Hi Melroy from Mbin. It's true what you are saying Julian. These FEPs forms the basic of the fediverse.
But at the same time I hate those FEPs alot. I would rather see a more detailed and better described ActivityPub protocol v2.0 or 3.0. My point is that the current ActivityPub is way too vague.And we need dozens of various FEPs to get the features we actually need and want to get the basis features of today. Currently it's hard to read, there is no single document. No single source of truth. All FEPs are actually optional to implement. And it's a mess.
Could you imagine if an internet standard like http or TCP was documented like this? It would never have worked.
>Currently it's hard to read, there is no single document. No single source of truth.
We can make it happen.
I am currently working on this: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md. It's a guide for developers, but in the future it may be used as a base for a more formal specification.
-
>Currently it's hard to read, there is no single document. No single source of truth.
We can make it happen.
I am currently working on this: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md. It's a guide for developers, but in the future it may be used as a base for a more formal specification.
Hmm, how do you reconcile the fact that not all FEPs are applicable to all application types?
For example soft deletion is preferable but not required...
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
> If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.
Thanks, it's this.
Edit: oh interesting, I looked into it. We serve the absolute URL in HTML but not in markdown. I had no idea threadiverse apps read the markdown. Neat!
-
Not sure if you're already aware, but that relative link there is broken in Lemmy, Mbin, and Piefed.
If you used it manually, I'd suggest not using relative links in posts targeted at users from software that hasn't implemented them yet.
If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.
-
@rekall_incorporated@piefed.social said in [Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]](/post/https%3A%2F%2Fpiefed.social%2Fc%2Ffediverse%2Fp%2F1568622%2Ffediverse-wide-cross-instance-cross-platform-link-substitution-ux-improvement-thoughts):
> This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.I don't think this is true at all.
The average user doesn't know what Lemmy is, let alone the political views of their core development team.
But don't worry, it's like that joke about vegans:
How do you know the Lemmy devs are politically dubious? Don't worry, someone on the threadiverse will tell you.
-
How the links act is different from client to client. If you click the link in the Lemmy web UI, it will take you directly to Lemmy.wtf, but if you used Voyager (iOS client), it will automatically redirect to your own instance.
This is something that should be built into the Lemmy web UI.
You can also use browser addons. I have an addon that redirects me to my own instance, if I click on a link in my browser. I also have an addon that takes me from YouTube to Peertube, if the video also exist in PeerTube or if I click a PeerTube link, it takes me to my instance.
Also how dare you criticise the awesome TLD .wtf, which is clearly an abbreviation of “What The Fediverse”?!
-
I've seen that being used. It works fine for more technical users, but it's just an extra pain point.
If you make links, you need to apply the service Different UI from whatever instance/client/platform that you are using.I much prefer Piefed's soon to be released link substitution feature.
-
Mbin has had that feature for a while too
-
It's a temporary workaround but the experience is still clunky
-
Well; atleast for lemmy, there's https://lemmyverse.link/ ; which fixes exactly what you mention. You send that link, other people choose their instance in the redirect, and boom!
