A single-document basic [Fediverse] interop spec, ie.
This could be done as a “minimal profile” of a stack that contains a subset of AP [ActivityPub], AS [ActivityStreams], and Webfinger
This would be even easier if you leave out Webfinger. To my knowledge Mastodon is the only project that requires it.
A branding program for products that have passed the test suite
I doubt that this can really work in an ecosystem without any central authority like the Fediverse. Whos stopping someone from putting the label on their software wrongly. Or more realistically, who will remove the label from a software which passed the test suite before, but fails after a new test was added?
A set of web “intent buttons” for Like, Follow, Post, etc that work across sites
There is already remote follow but the others might be useful additions.
The next few points are rather vague and need more details to discuss properly. But its nice to see that more people are starting to think about these improvements.
Interesting to see the section on suggestions for more universal user accounts.
@maegul @lemmyreader
I definitely agree with this suggestion:“Improved identity management across the Fediverse
* Easy-to-use single-sign-on across servers. Use case: I use several apps for different content types (like micro blog and video). Bonus: they all post from the same identifier
* Easy-to-use persona management. Use case: I have a personal and a work account, bonus if they can be on the same server Identifiers not tied to the domain name system”https://reb00ted.org/tech/20230425-w3c-activitypub-wishlist/
I currently have a Mastodon, Pixelfed, Lemy, and PeerTube account. A single ID across all of them would be amazing.
Not just that, but it would really help accelerate the uptake of other Fediverse services if users could simply login with their Mastodon account.
Pixelfed is a better UX for photos, so why not let Mastodon users use it for that?
It might be good if somebody added the single account thing to fediverse-ideas.
I cannot add it myself, because I would feel the need to explain why a thinner ActivityPub architecture such as bovine solves the problem without effort.
@ajsadauskas I have a strong feeling that the more convenient “Easy to use single sign on across servers” will be, the less secure it will also be.
#SingleSignOn is #SinglePointOfFailure.
I vote for security over convenience.deleted by creator
Interesting indeed… Not sure about all the other points (have not checked), but even if I repeat myself:
Easy-to-use single-sign-on across servers. Use case: I use several apps for different content types (like micro blog and video). Bonus: they all post from the same identifier
:ballot_box_with_check:
OpenWebAuth in Zot (Hubzilla) and Nomad (streams)Easy-to-use persona management. Use case: I have a personal and a work account, bonus if they can be on the same server
:ballot_box_with_check:
Multiple identities, not only on the same server, but (if you wish so) tied to the same account (same login+credentials) from where they can be switched with a click.Plus, in Hubzilla, each identity can have multiple profiles to show to different contact lists (This is a bit over the top, maybe, hardly anyone uses it, but you can show a different faces and profile data to different privacy circles, and post to different pricavy circles, even from the same identity)… Streams skipped that for ease of use.
Identifiers not tied to the domain name system
:ballot_box_with_check:
In Zot & Nomad, every identity has an own address-independent ID+hash which can be cloned to multiple addresses (one of which can be defined as the currently “primary” address, but you can access everything from any clone).Sorry, I am aware that I am naming Hubzilla and streams often currently - But it seems the functionality it offers is currently in focus, but not widely known…
Not sure if it’s related, but I recently found some people who are trying to clarify and improve the ActivityPub specs : https://codeberg.org/fediverse/fep
