this post was submitted on 17 Jun 2023
227 points (100.0% liked)

Technology

39410 readers
144 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago
MODERATORS
 

In my opinion, there are two big things holding Lemmy back right now:

  1. Lemmy needs DIDs.

    No, not dissociative identity disorder, Decentralized Identities.

    The problem is that signing up on one instance locks you to that instance. If the instance goes down, so does all of your data, history, settings, etc. Sure, you can create multiple accounts, but then it's up to you to create secure, unique passwords for each and manage syncing between them. Nobody will do this for more than two instances.

    Without this, people will be less willing to sign up for instances that they perceive "might not make it", and flock for the biggest ones, thus removing the benefits of federation.

    This is especially bad for moderators. Currently, external communities that exist locally on defederated instances cannot be moderated by the home-instance accounts. This isn't a problem of moderation tooling, but it can be (mostly*) solved by having a single identity that can be used on any instance.

    *Banning the account could create the same issue.

  2. Communities need to federate too.

    Just as instances can share their posts in one page, communities should be able to federate with other, similar communities. This would help to solve the problem of fragmentation and better unify the instances.

Obviously there are plenty of bugs and QoL features that could dramatically improve the usage of Lemmy, but these two things are critical to unification across decentralized services.

What do you think?

EDIT: There's been a lot (much more than I expected) of good discussion here, so thank you all for providing your opinions.

It was pointed out that there are github issues #1 and #2 addressing these points already, so I wanted to put that in the main post.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] AskThinkingTim@kbin.social 5 points 2 years ago

Lemmy needs me to be able to login.....Let's start with the basics.

[–] lightingnerd@kbin.social 4 points 2 years ago* (last edited 2 years ago)

I think #1 is a great idea, but it would take a lot of work and would probably be a pain to phase-in and phase-out across all platforms, but I do think it's a good idea, at least to offer as an option. While I am loathe to mention anything cryptocurrency and NFT-related, creating a simplified distributed ledger and smart contract system that would propagate through federated communities seems like an interesting idea. Alternatively, creating a way for users to specify their other usernames on other servers in a small bio in a profile page could be a possible compromise.

Your point #2 also sounds great, but I don't think this should be allowed between communities on defederated instances, because there's laws in many countries that can classify the act of hosting/providing certain content to be criminal. Therefore, if say if server_a resides in country_a, and country_a allows piracy, and server_b in country_b, and country_b considers it a criminal act to propagate certain information about piracy, the server_a/piracy and server_b/piracy might have different restrictions to discuss piracy. However, a less-informed mod may attempt to federate server_a/piracy and server_b/piracy, and insodoing accidentally make the owner/host of server_a unknowingly complicit in a criminal act.

I'm not a lawyer, and of course this is not intended to be legal advice, but I think that the effort would better be spent on implementing a solution to the decentralized identity problem, than the de-fragmentation of similar communities.

One other nugget to consider, assuming we were to replace Reddit, and the sum of the users on the fediverse were to achieve similar numbers to Reddit's glory days--we would definitely be scraped for AI training data. By keeping the communities fractured, that makes it far more difficult for a company to easily scrape all the information needed. While it might be trivial right now, in the ideally decentralized structure that the fediverse would take, it would take a lot more requests for a server to chase out every strand on every network.

Perhaps in this sense, it might be wise for instances to allow specific community defederation(ie, where server_a and server_b are federated, but server_a does not allow server_b/piracy to propagate(this may already be possible, IDK), but I do not think it would be wise to allow community to community federation.

TL;DR: #1 is a great idea, OP, and it could be implemented in a simplified distributed ledger that propagates through federated communities, and uses a simplified smart-contract--or the problem could be solved by a compromise that allows users to specify their usernames for other instances in a small public bio. Addressing #2, this could cause legal problems in specific scenarios, rather it is more important for any instance to be able to disallow the propagation of specific communities from a federated server (if this isn't already possible).

[–] sibloure@beehaw.org 4 points 2 years ago

The idea of federating communities does sound like a good idea. Now that I think of it I'm surprised that isn't already a thing.

[–] Mintyytea@kbin.social 4 points 2 years ago

I think number 1 is important so it’s easier to move. Otherwise we could feel centralized to one instance rather than feeling free to federate

[–] someguy3@lemmy.ca 4 points 2 years ago

I like your points.

Short term they need to work on the "all front page". It doesn't seem to give me popular posts from all instances, it's full of 2 to 3 to 4 day old posts that were never very popular. I have to manually go around (like to this community) to find content.

[–] JollyRoberts@kbin.social 3 points 2 years ago (1 children)

@DaughterOfMars

For #1 - ive thought about that.

My thought would be something like a small LDAP type server. Self-hostable. You make a user like myuser@mydomain.net and its honored as a log in for the various fediverse stuff.

So like it could hold the subsciptions for the communities on the various threadiverse servers you connect to localy, and when you open say lemmy.ml, part of the info sent for your user would be a list of communities you are subscibed to on lemmy.ml.

If it just handles the user auth, then it could also be a user auth for other fedivers stuff too. PixelFed, and Mastodon, etc. Each service could have its own sub section of the user object's info.

You would still probably end up with a "home" instance you would use, but if that home instance becomes untenable, or goes away, then you would just pick a new instance and log in there with your myuser@mydomain.net account.

Im not a good enough dev to code it, but thats my idea anyway.

load more comments (1 replies)
[–] Sal@mander.xyz 3 points 2 years ago (2 children)

You can create a one-person instance and hold your identity there.

If you what you want is for every server to hold your identity, you have to trust all servers. I think that an evil admin would be able to impersonate any user from any instance if that were the case. How do you delete your account? Can an any admin delete your account everywhere? Which one is the real "you"?

[–] Widget@kbin.social 3 points 2 years ago

I would assume the same way any other system with untrusted nodes works: with the client authenticating by use of a cryptographic signature on everything they submit.

load more comments (1 replies)
[–] xtremeownage@lemmyonline.com 3 points 2 years ago (25 children)

Regarding point 1- if people would just stop signing up on lemmy.world, lemmy.ml, and beehaw.org, because they have the most people-

Things would go much smoother!

Pick an instance based on uptime, or hell, create your own instance.

Piling all of the eggs into a single basket is destined to result in failure.

[–] Mintyytea@kbin.social 3 points 2 years ago (1 children)

It could help too if maybe on the sign up page, if an instance is getting full, they suggest some instances that are less full to join. That way people can be guided without having to do research on their own (before they’ve even decided to commit to the fediverse)

load more comments (1 replies)
[–] Spzi@lemmy.click 2 points 2 years ago (6 children)

if people would just stop signing up on lemmy.world, lemmy.ml, and beehaw.org, because they have the most people-

Things would go much smoother!

Somehow I trust the individual instances to self regulate. When an instance thinks it should not grow any further at the moment, it can close for new registrations, and users will naturally flock to others which are still open. I don't see this as a responsibility of the users, and in case of users completely new to lemmy, I also don't see how they could make a reliably informed decision.

load more comments (6 replies)
[–] someguy3@lemmy.ca 2 points 2 years ago (1 children)

I signed up with lemmy.ca and I regret it. It doesn't load "all" content very well so I have to hunt to find content. Hopefully they will fix it.

[–] xtremeownage@lemmyonline.com 2 points 2 years ago (1 children)

We can only go up from here!

Also, cannot promise my instance is any better, but, your welcome to try it. https://lemmyonline.com/

Its working quite nicely today though.

[–] someguy3@lemmy.ca 2 points 2 years ago (1 children)

It's not an instance problem, it's a Lemmy sorting/loading/ranking problem. It doesn't seem to show very well popular posts from other instances like beehaw or lemmy.ml.

[–] xtremeownage@lemmyonline.com 4 points 2 years ago

Known issue, going to be fixed soon in the 18.0 release. Until then, just gotta sort by new.

load more comments (22 replies)
[–] tom42@lemmy.one 3 points 2 years ago

Thank you for finding and writing the words for it.

Both points describe very well what I miss at least in Lemmy like Fediverse platforms.

[–] average650@beehaw.org 2 points 2 years ago (1 children)

Well, #1 is kind of impossible now. Different people can have the same ID on different instances.

#2, unless they really want to just be their own separate community completely, like an entirely different website, then yeah of course. That's the point. Regarding the current major defederation, my understanding is that this not meant to be permanent and is a different situation. It's a workaround basically.

[–] DaughterOfMars@beehaw.org 4 points 2 years ago

Using DIDs would involve a completely different system. Everyone would have to create a new identity anyway.

[–] heartlessevil@lemmy.one 2 points 2 years ago

How do decentralized identities interact with unique usernames? By Zooko's triangle, if identities are distributed and secure (implied by unique), the names are not human-meaningful. So we would be identified by public keys rather than usernames, like Tor onion addresses. Am I understanding this right?

[–] jeena@jemmy.jeena.net 2 points 2 years ago (1 children)

I don't understand the first one, why would we want that? Wouldn't it be enough to make it possible to move accounts similar to how mastodon does it (but including your local content)?

My bigger problem is that if a instance goes down then the community is gone. I like how Matrix has solved it that you can have aliases and the content gets replicated on other servers, etc. Then even if people defederate then you still have your old copy and people can keep using it.

load more comments (1 replies)
load more comments
view more: ‹ prev next ›