I mainly use the Mlem app, and today I got a notification that I had one new inbox item. When I checked my inbox, I saw that it was empty.

Before I submitted a big report, I wanted to see what happened on the lemmy.world website. As shown in the attached screenshot, it too shows one unread item, but nothing in the inbox.

So I’m led to believe this is an issue with the server. And if not, then at least I have done my due diligence before reporting this to the Lemmy devs.

In either case, is there anybody here who could help me get this resolved; or at least pointed in the right direction?

Thank you!

  • dohpaz42@lemmy.worldOPEnglish
    2·
    6 months ago

    Looks like DABDA@lemm.ee was correct. It was the piped bot that replied to a video I posted in a comment. Once I enabled bot accounts, I was able to mark it read and disable the bot accounts option again.

    Thank you!

    • DABDA@lemm.eeEnglish
      2·
      6 months ago

      Awesome, glad I was able to help!

      That bot has long been a thorn in my side, both due to that Lemmy bug but relatedly because I used to include Piped links with all my YT ones but the bot doesn’t(/didn’t?) check for them before replying anyway. I’ve never created a bot but I can’t imagine it’s more than like a single line to do a regex search for the exact link it intends to post and aborting if it’s found.

        • DABDA@lemm.eeEnglish
          1·
          6 months ago

          The Piped bot is checking comments for instances of a YouTube domain and video id (I don’t know specifically what it triggers on) and then replies with a link to that video id as a Piped-based one. But what it should also do is check if the initial comment also contains the Piped URL it’s about to post and then not reply with a duplicate of that same address.

          For example I’d post something like

          And the bot would reply offering the exact “Piped mirror” address I had already linked to. This would happen regardless of if I used custom link text or just left it as a raw URL so the bot clearly wasn’t doing a check of either method.