Skip Navigation
148 comments
  • I suggested an idea to fix this, that I called "thread entanglement". I had suggested it for Kbin specifically, before, but honestly the base Lemmy software could use something like this. I'd love to see some sort of smart merging of duplicate threads like this be possible.

    • As others have mentioned in that thread. It would be better as an option from the user side rather than site wide forced implementation. I hope you open a GitHub issue/discussion in the repository so the idea could get more exposure.

    • Adding this as an issue on the Lemmy GitHub would be a great idea.

  • If the title text is the same it should just squash them, show you all the options on further inspection.

    • This is my preferred option. Requires no underlying change to ActivityPub or federation, just makes the end user experience more pleasant until/unless communities gain more distinct personalities that would result in fewer reposts.

    • Better yet, it should semi-force you to post as a crosspost which would remove the duplicate from end user feeds. Especially if there's already a post on another community with a matching content link.

  • I appreciate the poster sharing the article to multiple communities/instances, but would be nice if the Lemmy front-end could batch these (maybe with a link like "appears in a@b, b@b, c@a ...") if the user + link + title all hashed out to the same thing.

  • On one hand yes annoying but on the other I'm grateful for their effort in generating post

  • Wef err Voyager has a thing that will block things that you have already looked at.

    That might help

  • Give it some time my dude. Devs are working to fix these issues. Eventually we will get there

  • This bugs me too. There are various GitHub issues about grouping communities. As far as I know, no one has gotten to 'em yet.

148 comments