I don’t understand how Lemmy intends to do it when the different instances are federated, if several instances create the same community for example…is that possible?
I don’t understand how Lemmy intends to do it when the different instances are federated, if several instances create the same community for example…is that possible?
Interesting idea!
/u/dessalines, would you like to comment?
An issue I just thought of is how initial instance mods would be appointed (for new instances etc.), but that could be done by instance admins or community vote? Or it could be the first user to subscribe from that instance.
/u/AgreeableLandscape The communities on different instances will be totally different, with its own posts, mods, etc. So
instance1/c/news
will be totally different frominstance2/c/news
.Unrelated thought, you think it would be a good idea to send notifications about new comments to everyone above in the comment tree? So in this case, notify you, /u/muirrum and /u/AgreeableLandscape about my post?
I thought about it, because I think that’s the way twitter does it. But IMO for reddit-style it shouldn’t, there are some reddit threads that have dozens of nested comments, where the original parent commenters aren’t even a part of it anymore. I’d personally want mentions to be explicit if they aren’t in a direct response.
Totally agree but could it be better to have this setting as an option? In small communities, it could be useful, in large ones could be not. Let’s have a choice.
We could have an option to follow a particular point in the comment tree, but by default I don’t think that would be a good idea since discussion tends to evolve as thread depth increases, and notifying users about every comment can cause problems with most of them being out of context.
I feel like that would needlessly complicate federation, as described in other places on this thread (https://lemmy.ml/post/31114/comment/2943 etc).
Having different servers, many of whom aren’t connected, having different “versions” of the same community, that share some data, but not all, would be infinitely more complicated.
I see your point, however I think community fragmentation is an issue that will need to be resolved, and having separate communities for each instance won’t help with that.
What if instance A wants to make a
/c/news
, and have control over it, but that name is already taken?Fragmentation means community owners actually get full control over anything they want to create.
Ah, I see. How will communities across instances be differentiated?
With different identifiers. So if you’ve subscribed to both communities, you will see a
posted by X to instance1/c/news
, andposted by Y to instance2/c/news
.Communities are totally different from hashtags, which have no moderation and anybody can put anything they want in them.