this post was submitted on 28 Jun 2023
35 points (100.0% liked)
Moving to: m/AskMbin!
19 readers
1 users here now
### We are moving! **Join us in our new journey as we take a new direction towards the future for this community at mbin, find our new community here and read this post to know more about why we are moving. Thank you and we hope to see you there!**
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I do think that if Redditors (like me) arrive in waves and continue to set the tone, we will see pressure on front-end developers to figure out a way to conflate identically named communities in the end-user UI. It would take federation in a slightly different direction than expected, but it provides resiliency in its own way. For instance if a large instance supplies 50% of the "tech" articles and defederates or collapses, users still get 50% of the experience with no additional effort. I'm sure there are knock-on effects I'm ignoring, though.
I could imagine something similar to reddit's multisubreddit feature, whereas in this case it's different magazines/communities from different instances or even services.
I think a possible way forward for this that won't necessarily affect federation directly is to allow a user to combine different subscriptions into a custom "list" or custom "magazine"/"community". Then on the user end, it looks like 1 combined feed, but in the back end, it's still just a bunch of federated communities.
Yeah, I don't think any changes to the back-end or to Activitypub would be needed. If something were to come around, I think it would be on the UI side, an app or a change to the web front-end of kbin or lemmy that allows custom "multireddits," or simple collapse of identically named comms/mags. I would even say it should be an option, not a standard behavior.