this post was submitted on 25 Sep 2024
132 points (95.8% liked)
Asklemmy
43947 readers
638 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
no, it's a feature, not a bug, that we can have more than one community for discussing the same topic here; makes it harder to censor
There has to be a better way to keep the strengths of federating without partitioning the community smaller and smaller until there is no community left.
Can you imagine Lemmy with a similar amount of Reddit users? Anytime you'd post, you'd have to replicate it between X number of instances (for visibility). Conversations would be fragemented and duplicated, votes would be duplicated. To me this almost sounds like "work"...
There has to be something better.
For example, instead of "every instance is an island". Meaning the current hierarchy is "instance" - > "community" - > "post" - > "threads". We could instead have "community (ie: asklemmy)" - > "post (ie: this post)" - > "instance (Lemmy.ml, Lemmy.world, etc)" - > "threads (this comment)".
From a technical perspective, it would mean that each instance would replicate the community names and posts. Which is already beginning done (this post is a perfect example), but as long as each instance would share a unique identifier to associate the two communities/posts as "the same thing" (and this could simply be the hash of the community /post name). Everything else would be UX. Each instance would take ownership of the copy of the community and post, which means they could moderate it according to their standards.
~~Especially given that the above link points to lemmy.ml, an instance notorious for harbouring tankies & amplifying pro-authoritarian talking points.~~
The link is .ml but points to a thread in .world. My bad ๐
no, we are posting to a community on lemmy.ml here, that link points to a community hosted on lemmy.world (as displayed on lemmy.ml)
idc because neither of those is my instance, I subscribe to communities regardless of what instance they're hosted on
Confusing... My instance is .world, and I similarly subscribe to communities regardless of instance. So seeing a .ml link had me go ๐จ tankie instance for a second, conveniently failing to notice that A: that post is in .world, but seem from .ml; and B: this post is in .ml.
My bad ๐
Though I would suggest OP to see if they can fix the link to one that changes the specific link based on the visitor's instance
I fixed the link. For some reason the Lemmy Client (Voyager) keeps generating '.ml' links (even though I'm on Lemm.ee)
This whole identical thread really confused Voyager, I thought I was seeing double.