this post was submitted on 13 Feb 2022
4 points (100.0% liked)

Fediverse

17708 readers
26 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
4
Towards a Greater Federated Architecture (deadsuperhero.com)
submitted 2 years ago* (last edited 1 year ago) by deadsuperhero@lemmy.ml to c/fediverse@lemmy.ml
8 comments fedilink hide all child comments
 

Over the years, I've been studying a handful of different fediverse platforms that bring a lot of interesting concepts to the table.

As someone that has studied and reported on the developments of these various systems, I've decided to put together a summary of things I'd like to one day put into my own federated platform, should I ever develop enough brainpower to actually develop one.

you are viewing a single comment's thread
view the rest of the comments
[–] pizza_is_yum@slrpnk.net 2 points 2 years ago* (last edited 2 years ago)

Agreed 100% on the account proliferation and type asymmetry points. The way things stand, right now, the user's choice of account provider will determine what actions they can take on the fediverse as a whole. It is a wholly unfortunate state of things.

An interesting exception would be Owncast's "Fediverse auth" option for stream chatting. That sends a One-Time code to your mastodon inbox for authentication.

As @jackalope@lemmy.ml suggested, Solid would be a shoo-in for your "User Data" server. If, that is, Solid could shake off some of its sheer conceptual gravity. People say the fediverse has a geek problem, i.e. only geeks use it. Well, I think Solid has a worse version of that problem. It is only approachable by the deepest loremasters of geekdom. They are also still vague on its actual operation. What's more, they are still deliberating what their actual security model will look like.

Which makes me sad, because the Solid sounds exactly like what we architecturally need.

EDIT (3:25 am EDT): Just wanted to add on here, I really think that "linked data" and SPARQL were bad, possibly self-defeating decisions for the Solid project. I sorta see their motivation–they want that sweet, sweet flexibility. But I think this approach is not a good solution.

EDIT again: added links