88
submitted 5 months ago by cypherpunks@lemmy.ml to c/fediverse@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] thepaperpilot@incremental.social 35 points 5 months ago

I agree with this take, and recently I actually read this article that criticizes how server centric fedi is as a whole. If it's hard and expensive for a layperson to self host, but you need to have an account associated with a specific server, then you're going to end up with a system where you're under the whims of a instance owner still. Not to mention the whole pick a server step severely hurts our adoption rates.

I like the idea of having an account just being a public and private key pair. Theoretically you could make one client side, use it to sign your messages, and servers could verify the signature and distribute your post without needing to have an explicit account for you. You could send every message to a random instance and it'd still work. You wouldn't have to worry about links to the "wrong instance" and you wouldn't have to attach your identity to a instance that might shut down or be bought by a bad person. The server would be essentially irrelevant.

[-] Jayjader@jlai.lu 16 points 5 months ago* (last edited 5 months ago)

I align with that article 's conclusion; in fact such a "fediverse browser" is exactly what I think the fediverse needs to fully replace closed/proprietary/traditional social media.

However, some of their arguments seem off. For example, for the client to be able to choose/implement it's own sorting algorithm, it seems to me that it would need to have access to all posts. At that point, your client is just another server, with all the problems that we're originally trying to avoid.

I have the same problem with your proposal / nostr's approach: you may obtain a portable identity but all the "content" tied to that identity still has to live somewhere - someone else's server or your own.

[-] thepaperpilot@incremental.social 4 points 5 months ago

Yeah, I disagree with that part as well. I think it's fine for servers to store the content and provide endpoints for specific queries/sorts, and expecting the clients to have all the posts is a tad extreme.

In this case, yes the data needs to live somewhere, but that's the nature of having data be retrievable.

load more comments (4 replies)
this post was submitted on 30 May 2024
88 points (93.1% liked)

Fediverse

17735 readers
25 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