Blaze (he/him) @lemmy.dbzer0.com to Fedigrow@lemm.eeEnglish · 23 days agoLemmy Needs to Fix Its Community Separation Problempopcar.bearblog.devexternal-linkmessage-square123fedilinkarrow-up199arrow-down110cross-posted to: blogging@programming.devlemmy@lemmy.mlfediverse@lemmy.mlfediverse@lemmy.world
arrow-up189arrow-down1external-linkLemmy Needs to Fix Its Community Separation Problempopcar.bearblog.devBlaze (he/him) @lemmy.dbzer0.com to Fedigrow@lemm.eeEnglish · 23 days agomessage-square123fedilinkcross-posted to: blogging@programming.devlemmy@lemmy.mlfediverse@lemmy.mlfediverse@lemmy.world
minus-squareBlaze (he/him) @lemmy.dbzer0.comOPlinkfedilinkEnglisharrow-up1·9 days agoEvidence shows that all over the platform there’s one community which becomes the main one for a given topic !europe@feddit.org !fediverse@lemmy.world !gardening@lemmy.world !crochet@lemmy.ca People are free subscribe to either, both, or none. Subscribers can, but posters are not going to crosspost their content to all the communities available on a topic And adding a feature where a community can follow another solves pretty much all issues one could have with fracturing. That’s not even on the roadmap of Lemmy, Piefed or Mbin, is it?
minus-squareacockworkorangelinkfedilinkEnglisharrow-up1·9 days agoProposal 3 according to another comment on this thread.
Evidence shows that all over the platform there’s one community which becomes the main one for a given topic
Subscribers can, but posters are not going to crosspost their content to all the communities available on a topic
That’s not even on the roadmap of Lemmy, Piefed or Mbin, is it?
Proposal 3 according to another comment on this thread.