201
Is there a way to not see duplicate of the same topic across different communities? (sh.itjust.works)
submitted 6 days ago by to c/fediverse@lemmy.world
71 comments fedilink hide all child comments
 

Hi everyone!

I’m really enjoying the Fediverse through Lemmy and Peertube.

Two creators I enjoy and follow on the Fediverse are Dash and Gardiner Bryant (both work on The Bryant Review) as their content is really enjoyable.

Sadly they are the target of my post as they shares their content on many different communities that I follow.

Today I had 5 times the same topic on RetroDeck (great project too) on my feed on Lemmy (Voyager).

It is the same on PieFed (Interstellar).

This is really annoying and I haven’t found a way to not show these duplicates. Do you know about one or is it worked on?

Also when crossposting, it would be great if everything appeared under on post. Is it feasible?

Sorry if it’s easy and I just missed it. In a way I hope it is because it would mean that the Fediverse is festure rich😇

Edit: Added Dash as she was in fact the one who published the article. Also it appears that the issue is only on mobile apps since both the browser of Lemmy and PieFed don't have it.

Edit 2: Using the Progressive Web App of PieFed seems to have solved the issue for me

you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 5 days ago (5 children)

This would break the way many users use Lemmy & Co. I'm happy about users that cross-post.

I only follow communities I subscribe to. Let's say I follow B but don't follow A. If a user posts something related to topic A and topic B only in a community A, which I don't follow, I would miss information interesting to me. When the user cross-posts to community B as well, then I'll also see that useful post.

Also, even the same topic/community appears on different instances, and some users may not even be aware of the same community in other instances. They would miss useful or interesting information without cross-posting.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] -5 points 5 days ago (4 children)

    It is okay to miss out on something. If nobody crossposts it, it probably wasn't that interesting anyways.

    If you are afraid that you are missing out on some content, then look at the crossposts in your followed communities. Maybe the communities that were the origin of the crossposts are interesting, and worth joining? Then you'll also see all their posts in the future.

    If you want to see all posts that could remotely be relevant to you, you ultimately will have to follow all possibly relevant communities anyways. Because most users post their things simply to one community and call it done. And that's ok and good, and does not need changing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 5 days ago* (last edited 5 days ago) (3 children)

    I could completely reverse your argument, insisting on why you should do differently.

    It's completely subjective.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 5 days ago* (last edited 5 days ago) (2 children)

    You want to argue that people should post their posts to more communities?

    And why do you want to insult me?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 5 days ago* (last edited 5 days ago)

    I'm not insulting anyone (edit: that was because of a typo, see other reply). I don't want to argue. I'm simply saying that the position or preference is subjective: neither I or you can make an objective argument of why someone ought or oughtn't to cross-post.

    The simple proof is that you're unhappy about cross-postings – and surely I have no right to say that you should be happy about them instead. And at the same time I am happy about cross-postings – and you have no right to say that I should be unhappy about them instead.

  • permalink
  • fedilink
  • source
  • parent