Lemmy

12546 readers

24 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

If the ideal setup is many medium sized instances rather than a few huge ones, wouldn't that mean users would need to subscribe to duplicate communities in all of those instances? (sh.itjust.works)

submitted 1 year ago by spiritedpause@sh.itjust.works to c/lemmy@lemmy.ml

41 comments fedilink hide all child comments

Otherwise, if we have a lot of medium sized instances but the most popular communities are hosted on just a few huge instances, doesn't that defeat the purpose of distributing load across many instances?

If that's the case, how do we solve the cumbersome user experience of having to subscribe to the same community over and over again across a ton of medium instances?

you are viewing a single comment's thread
view the rest of the comments

[–] untitled_liar_liar_sequel@lemmy.world 4 points 1 year ago (3 children)

I wonder how feasible it would be to set your instance up to aggregate content from duplicate communities.

[–] meldrik@lemmy.wtf 6 points 1 year ago* (last edited 1 year ago) (1 children)

We need something like "Multi-subreddits", where you can combine communities into the same entity. Only issue is that a lot of the same posts are posted a cross all the same communities.

[–] untitled_liar_liar_sequel@lemmy.world 2 points 1 year ago

I've been thinking about this all morning and have come up with this:

When the link is the same, we can just union on the thread and sort it as any other thread.

When the link is not the same, but the content is similar, I wonder if you could run a semantic comparison (I'm only just starting to learn about this), and when the comparison scores above a certain threshold, union the threads.

Self-text posts might just make sense to leave alone.

load more comments (1 replies)