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?
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?
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're viewing a single thread.
I wonder how feasible it would be to set your instance up to aggregate content from duplicate communities.
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.
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.
A multi-community feature like multi-reddit wouldn't be that hard to implement. Basically build a subscribe list that isn't owned by a specific user and come up with a way to link them by name and ID. Being able to share community subscribe and block lists would seem a useful evolution of Lemmy.