[โ€“] 5 points 1 day ago* (last edited 1 day ago) (2 children)

Hmm, I think this is an issue with the default Lemmy UI only. The API has all three post, it displays correctly on the other apps I tried, and it's federating out correctly: https://piefed.ca/c/wwater@lemmy.ca

I suspect this is because the default Lemmy UI does not render "duplicate" posts when they appear on the same page, and instead places them as "crosspost" links on the oldest post. If you go to !wwater@lemmy.ca and look the entry for your Oct 28th post, there is a "cross-posted to: wwater" note on it with a link to the missing post.

I will need to look into if this is intended behaviour or a bug. In the meantime, you can likely fix this by making each post unique. I see that wwater.ca/example redirects back to wwater.ca nicely. So you could edit the Nov 4 posts to wwater.ca/2026-11-04 and the Lemmy UI should treat it as a unique post.

  • source
  • [โ€“] [S] 2 points 1 month ago (2 children)

    the first time you press the "Next" button, it takes 5+ seconds to load?

    Yes, that's correct

    And it takes that long every time you press the "Next" button (for subsequent pages)?

    Yes, I'm not certain if it takes exactly the same amount of time as the first time, but it's definitely long.

  • source
  • parent
  • context
  • [โ€“] 2 points 1 month ago* (3 children)

    So just to be clear - if you load the main page, it's pretty fast, but the first time you press the "Next" button, it takes 5+ seconds to load? And it takes that long every time you press the "Next" button (for subsequent pages)?

  • source
  • parent
  • context
  • [โ€“] [S] 2 points 1 month ago

    It definitely shouldn't be an account wide setting that's for sure. Should work the same as hiding tbh because now the mark read on scroll feature on my app hides too much. I'd only want to hide read posts in ALL and my subscriptions really.

  • source
  • parent
  • context
  • [โ€“] [S] 2 points 2 months ago (2 children)

    I force refreshed the page; cleared the cache; and opened it in Firefox, Ungoogled Chromium, and Vanadiaum (mobile) and nothing seemed to fix it. Only on Firefox I was greeted with :

    504 Gateway Time-out nginx

  • source
  • parent
  • context
  • [โ€“] [S] 2 points 2 months ago (4 children)

    It was the website via Firefox. Sorry, I didn't check with another browser because I wasn't logged in with any other one at the time. I don't see the same issue with the app, Thunder, on my phone.

    I'll double check with different browsers later tonight and force refresh the page too then report back. Thank you for responding!

  • source
  • parent
  • context
  • view more: next โ€บ