If my home instance is lemmy.ca, and I want to create and moderate a community about, say, Japanese woodworking (random example of a subreddit I follow), isn’t it a bit odd for that community to be hosted by lemmy.ca? If somebody else later created a community of the same name on lemmy.ml or lemmy.jp, would people be more likely to join those communities as they seem more “official”?
On one hand, joining multiple instances just for “better” vanity URLs for new communities seems wrong (and annoying to manage), on the other hand it’s odd that I’d arbitrarily impose the traffic associated with a community completely unrelated to Canada onto lemmy.ca. How is this supposed to work?
Say I was looking for a community like yours. Since yours is the first one I will likely see much more activity on it and skip the one with 0 if it was created afterwards just for the vanity url.
Since lemmy.ca says it’s not restricted to non-Canadian topics and welcomes all, I see nothing wrong if you create it there. Also, if the content isn’t images uploaded through Lemmy, I wouldn’t worry about taking up resources, as storage space seems to be the limiting resource, not traffic (in the form of bandwidth or CPU time).
Yep. I think the best way going forward is to pretend instances don’t exist as much as possible.
Im only just looking into the fediverse. But as I see it, ideally, some future feature of lemmy would allow communities centered around the same thing on different nodes, to merge, that is, to be federated between them. Maybe by mutual consent from the mods of both.
This would help discoverability immensely, and also allow one to sub to a “local” community but have posts appear to users subbed to the “same” community on their local instance, as well as see posts from users posting to their instances connected community.
It would be a bit like a crosspost, except any given post would still live on the actual server it was posted from, the feed just gets aggregated from all the different “mirror” communities.
Critically, it should always be possible to disconnect, as well. To have those two timelines of content seamlessly unzip from each other, taking their respective comment threads with them, but allowing both communities to separate again and continue.
This would also provide redundancy in cases of instances going down, perhaps to re-appear later, perhaps not.
