- cross-posted to:
- fediverse@lemmy.ml
- rust@lemmy.ml
- rust@programming.dev
- cross-posted to:
- fediverse@lemmy.ml
- rust@lemmy.ml
- rust@programming.dev
The problems faced and solutions mentioned seem particularly relevant to !fediverse@lemmy.ml and !fediverse@lemmy.world
I think I agree with their proposed solution
One issue might be that users lose some control over which communities they see content from. If example@lemmy.ee, example@lemmy.ca, and example@lemmy.ex are all connected in this way, but I despise something about example@lemmy.ex, I can’t follow either of the others?
Which could be solved by a toggle on the community. The next question then would be what the default is, and I think more content would be better than less.
The last issue is how much more confusing this will be for new users, which I don’t know how to solve because I don’t quite understand it myself
I think it would be pretty easy to sort in your 1+2+3 case. Let users natively ban instances.
Say you hate instance 3. If you go into the 1+2+3 thread, you will only be able to see or interact with 1+2 comments, as all others wont even load for you.
The tricky part is if 3 users can see or interact with your comments. It might be the case that you literally just wont see anything downthread if one of them replies to you.
That would work well :)
I think it would also be helpful to have a way to see only one instance.
Say for example, some regional variants of communities group up (ex. The Canadian community for X + the general community for X)
Sometimes you might want to see all the content, and sometimes it might be helpful to just see the local content. A toggle or custom view would be nice to have