92
submitted 1 month ago by cypherpunks@lemmy.ml to c/fediverse@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] Jayjader@jlai.lu 16 points 1 month ago* (last edited 1 month 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 1 month 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.

this post was submitted on 30 May 2024
92 points (93.4% liked)

Fediverse

17019 readers
20 users here now

A community dedicated to fediverse news and discussion.

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

Getting started on Fediverse;

founded 4 years ago
MODERATORS