4as/ChatGPT-DeMod

Refreshing the Webpage with a Conversation Open Will Result in Messages Getting Flagged

Closed this issue · 5 comments

This extension works great. I've used it via mobile and desktop with great success. However, I've recently noticed (not sure if a GPT update did this...) that if you have a conversation window open and you refresh the webpage (necessary sometimes when it hangs or there's an error) then upon the conversation reloading, many messages show up as flagged with the dreaded "This content may violate our content policy. If you believe this to be in error, please submit your feedback — your input will aid our research in this area."

Any thoughts on this?

4as commented

I'm not sure if I understand. If you refresh your conversation, all messages that were already flagged for moderation will remained flagged after refresh, there is no going back. Unless you mean that refreshing will cause all messages being flagged? In which case I didn't observe that behavior. Can you provide details on how to reproduce that behavior? And on what browser are you? Also what version of DeMod are you using?

Yes, refreshing will CAUSE the messages to be flagged. Messages that were previously unflagged will be flagged upon webpage refresh...it's very odd. You can load in and out of the conversation without issue, but if you are in a specific conversation and hit webpage refresh, that's where the error arises.

To reproduce I would create a conversation that has wording/phrases/content that would typically be flagged, get several message/replies in and then hit refresh within your browser.

I'm using Chrome Version 113.0.5672.92 (Official Build) (arm64).

I'm using DeMod version 1.8.

4as commented

I see now what you were talking about. OpenAI has apparently been rolling out a new feature that allows people to share their conversations. If you access the conversation directly (like use the URL or... refresh it - it is the same thing) it is now being checked internally on their servers. Since the check is internal there is no way to workaround it.
I'm going to see if DeMod could be used to block or redirect any attempts at accessing a conversation directly through the URL.

4as commented

I just pushed an update that will redirect any attempts at refreshing or accessing the conversation directly back to the "new chat" page.