Messages from the bot are not marked as consenting?
On this page: https://www.answeroverflow.com/m/1091370232033050746
We see a thread that contains only two messages, one from me and the other from the AO bot itself. For some reason, the AO bot message is not public. Additionally, I am a member of the server, so I'm not sure why I can't see all messages anyway.
Probably any bot should be marked as consenting automatically, since they can't opt-in themselves and... they're bots.
Answer Overflow
About: #package-development - League of Extraordinary FoundryVTT De...
This thread is not for discussions about Foundry package development, but for discussing the purpose of this forum.
13 Replies
That’s weird since you’re signed in your should be able to see that message I’ll investigate that
Also agreed on bots should be marked as consenting, will update that
Funny enough, I was just working on a feature for our custom bot, and someone mentioned that hopefully the results would be indexed by AO. And my response was "I assume they are"
Can you try signing in and out to see if that fixes you not being able to see them when signed in? It’s working for me on my end
Yes, signing out and back in did seem to fix it.
The message has no body though
Doesn't seem like the embed is being retrieved.
Did you manually revoke the sign in via Discord? It’s possible your token expired or something that could have caused it
The embed content is stored although not displayed at the moment, that needs to be added
No, I just hit sign out on the site.
And then when I signed back it, it asked me to authorize again.
Hmm interesting, I’ll keep an eye on that and see if it was just a fluke or if it pops up again - the site should do a better job of reprompting you to sign in
So it probably was an expired login, but it just didn't tell me?
Yeah I’m guessing the token became invalid for some reason
It was actually another user that pointed this out to me.
So not completely a fluke probably.
Ah ok, I’ll investigate it and see if I can recreate it thanks for bringing it up - sorry about that
Not a big problem, thanks.
@rhyssul remember you also have to tackle embeds