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 😢 😭)
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
that’s because all of my new comments have been on this thread, which is opened by monyetbot which other instances consider non-existent, and so all comments on this thread are auto-rejected because the opening poster is rejected
it may be a related issue, but as crabby has discovered, the monyetbot user itself is rejected by other instances, and other instances can’t list a user that doesn’t exist in their db as mod
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
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
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.
unfortunately, something has gone wrong:
https://lemmy.zip/c/cafe@monyet.cc
https://lemmy.world/c/cafe@monyet.cc
https://lemmy.ml/c/cafe@monyet.cc
https://lemm.ee/c/cafe@monyet.cc
https://beehaw.org/c/cafe@monyet.cc
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 instanceby any chance running thesame databaseas 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) anddoes not have federation disabled(2 instances with the same name both sending federation traffic could possibly badlyconfuse 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:
cafebefore 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 😢 😭)
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
can you search for the bot username
@monyetbot@monyet.ccin 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/waiter_bot@monyet.ccis okay, so it is not that other instances are auto-rejecting bot usersI put the name directly into my search bar, didn’t exists
maybe instances are rejecting bots that have admin status?
but that would not really make sense
https://lemmy.zip/u/zen@monyet.cc
Your latest comment is 19hours ago, so maybe it take their sweetass time to link
that’s because all of my new comments have been on this thread, which is opened by monyetbot which other instances consider non-existent, and so all comments on this thread are auto-rejected because the opening poster is rejected
correction, i also posted in
announcements, but that is not federated to lemmy.zip:https://lemmy.zip/c/announcements@monyet.ccit is federated to lemmy.world though, and my last comment on there is from
announcementsHmm, fair enough
This happened before but it was marked as resolved, any thoughts?
it may be a related issue, but as crabby has discovered, the monyetbot user itself is rejected by other instances, and other instances can’t list a user that doesn’t exist in their db as mod
The bot’s first comment was 12 days ago though T_T
Maybe it take more than just one comment to get federated 🤔
I have no idea honestly
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
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
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
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.
if it ran on a subdomain of monyet.cc, then it shouldn’t be a problem