• Naomikho@monyet.cc
    1·
    1 year ago

    🎉Finally released the post auto-scheduling feature for Monyet.cc! I can already smell lots of required enhancements and other features that will require implementation… probably time to create a dedicated backlog for MonyetBot lol

    • zen@monyet.cc
      0·
      1 year ago

      unfortunately, something has gone wrong:

      https://lemmy.zip/c/[email protected]

      https://lemmy.world/c/[email protected]

      https://lemmy.ml/c/[email protected]

      https://lemm.ee/c/[email protected]

      https://beehaw.org/c/[email protected]

      all of them have the 28th july daily thread, but not today(29th july)'s, also looking at the sidebar on those instances, monyetbot is not listed as mod.

      you mentioned testing monyetbot on a dev instance. is the dev instance by any chance running the same database as this one (as in, all communities/posts/users from here are viewable there too, up to the time the db snapshot was taken, that is) and does not have federation disabled (2 instances with the same name both sending federation traffic could possibly badly confuse other instances)?

      the easy fix, without having to do too much debugging would be to try registering a new bot user, and see if it can be added as mod and accepted by the other instances, or you could try unmodding and then remodding monyetbot first.

      (unmodding and remodding would help if it was the modding that did not federate, another issue could be the membership of monyetbot in the community not federating, so perhaps try making monyetbot unsubscribe and resubscribe)

      edit: if this is not given attention, i think all future daily threads by monyetbot will not be available on other instances (oh god, i so hope i am wrong)

      edit 2: the instances are a mix of 0.18.2 and 0.18.3, so i don’t think the new version is the issue here

      edit 3: i think the main questions to ask are:

      • is the dev instance you tested the bot on running a snapshot of the monyet.cc db?
      • does the dev instance have federation turned on?
      • did you mod the bot on the dev instance in a community called cafe before doing it here on the main instance?

      if the answer is yes for all 3, then the modding event may have been sent out to other instances from the dev instance first, and so now the modding event from the main instance is no longer accepted by them, and with that all posts from the bot no longer federate (and neither do replies to those posts 😢 😭)

      • Naomikho@monyet.cc
        0·
        1 year ago

        No, the dev instance has its own database. Its whole ecosystem is separate from this one. It does not run the same snapshot. Last I remember, I think it did not federate, but I might be mistaken here… For the last question, the answer is yes because I had to emulate the scenario as closely as possible.

      • Annoyed_🦀 🏅@monyet.cc
        0·
        1 year ago

        If you check the bot via other instance, the user simply didn’t exists. It likely due to this is the bot first post so it take some time to register the user to other federated instance…me think

            • zen@monyet.cc
              0·
              1 year ago

              i think it has been more or less confirmed, that for some reason monyetbot is not appearing as user on other instances, and with that all posts started by monyetbot will not federate, and neither will comments to those posts

              edit: i don’t think posting any more comments under monyetbot will solve the problem, as the search box is supposed to find users even with 0 comments, so other instances are just not accepting monyetbot

        • zen@monyet.cc
          0·
          1 year ago

          can you search for the bot username @monyetbot@monyet.cc in the search box of those other instances?

          if it does not appear, then we’ll very likely need to change bot usernames due to it not being accepted by other instances

          edit: just checked https://lemmy.zip/u/[email protected] is okay, so it is not that other instances are auto-rejecting bot users

      • zen@monyet.cc
        0·
        1 year ago

        oh great, lemmy turned all those links to other instances into links to our instance, so if you click on them you don’t see the issue

        • Naomikho@monyet.cc
          1·
          1 year ago

          I can see the issue if i open in incognito mode, but MonyetBot has been moderator of cafe for a while on monyet.cc actually. I’m not sure if both instances can affect each other though, as dev is monyet.lol, not monyet.cc