a. Upon signing up for the a platform on the Fediverse the user would be redirected to the "Create your Passport" You would create your unique username. Once signed up you would then have an account on every platform connected to the Fediverse.

b. If someone friends/follows you on one platform they would automatically follow you on all platforms. Insuring that communities and friends could stay connected across platforms.

c. The passport for the user would show your feed on all platforms and allow you to selected which platform you want to see your feed from, also allowing you to directly search your content so you could find a post for whatever reason you need.

d. For the subscriber it would show them your feed and allow them to easily find your content.

e. Tons of customization options including the ability to monetize and or set a subscription fee for the video, blogging, and other "arts" platforms.

Safe Guards

You would be allowed to set your privacy setting to, Public, Subscribers Only, Approve Subscribers, Mutual Friends only, Private (Requires link)

Benefit

Would allow stream less interaction across the whole Fediverse and really get it going. No more having to create a different account on each platform and now you can claim an identity and keep track of your communities, also each site would directly help "advertise" the others.

you are viewing a single comment's thread
view the rest of the comments

[–] fjordo@feddit.uk 14 points 23 hours ago

I like the concept, but personally I see the decentralised nature of the Fediverse as a benefit rather than a hindrance, and moving all identity functionality to a centralised system would create more problems than it solves.

Suddenly you'll have a single point of failure for the entire Fediverse. A very appetising target for hackers and DDOS attacks.

An alternative that's in the spirit of your idea would be to allow for auth delegation, i.e. if you sign in with an Activitypub ID rather than a plain username, redirect to that instance to sign in then redirect back to the instance you started from, auth token in hand.

The nice thing about this approach is it's basically just OAuth 2. It's familiar, simple to implement and built in to a lot of web frameworks already. The only extra step would be advertising the server's auth URL via the nodeinfo endpoint, which is fairly trivial to do.