Everyone who’s subscribed to the same communities will see all of each others’ comments. The ones that won’t be seen are those in communities a user intentionally doesn’t subscribe to, which is a good thing.
And putting the choice of where conversation takes place in the hands of the OP isn’t good. There’s already issues with the first poster in a “no duplicate submissions on the same topic” community getting to set the tone for conversation through title and text. This just makes it worse. Downvoting a bad link still means the conversation is being denied in the community of users’ choice and the solution to that is allowing duplicates, which is just the status quo plus extra spam.
cynber@lemmy.ca 1 year ago
This still relies on everyone using the same app/front-end.
I guess I’m thinking about how it would be helpful in more general cases. If someone has an issue with a FOSS app, and they ask about it in two small communities, it would be much better to have the troubleshooting discussion in one place rather than have both communities missing part of the context.
Ultimately in your example, the user can still make both posts, this doesn’t change that. It just directs the comments to one post’s comment section rather than having it spread out.
Still it’s good to think about. Would a good middle ground just be the first implementation then? To link to the post that OP intends to be the main discussion thread, but people are free to ignore that if they want.