Well, duplicate communities might also be on purpose, to lessen centralization. I see many that try to migrate away from lemmy.ml, and this community is one of them. I agree that it might be a bit confusing, but it is easily worked around by subscribing to both communities.
Would it be hard to check if a community already exist in the instance and it’s federeted instance on creation ?
Same logic when I subscribe to a community, I should be able to auto subscribe to any duplicate on the “federation”. It could be an option (like a checkbox newt to the subscribe button) that can be disabled but is on by default.
What is stopping a post on a community to be copied automatically to the other community on the federation ? They could be marked as duplicate and the feed could dedupe this. The comments could be unified. Is this impossible?
I’m new to Lemmy and I’m not a rust dev. Sorry if I’m saying something stupid.
Well, duplicate communities might also be on purpose, to lessen centralization. I see many that try to migrate away from lemmy.ml, and this community is one of them. I agree that it might be a bit confusing, but it is easily worked around by subscribing to both communities.
Would it be hard to check if a community already exist in the instance and it’s federeted instance on creation ?
Same logic when I subscribe to a community, I should be able to auto subscribe to any duplicate on the “federation”. It could be an option (like a checkbox newt to the subscribe button) that can be disabled but is on by default.
What is stopping a post on a community to be copied automatically to the other community on the federation ? They could be marked as duplicate and the feed could dedupe this. The comments could be unified. Is this impossible?
I’m new to Lemmy and I’m not a rust dev. Sorry if I’m saying something stupid.