The write detect is rather naive unless you're logged in. There's a few reasons it might be doing this.
- It sends an event that fiatjaf signed a long time ago, it's possible you've blocked this event/user from writes as it might appear to be spam on your end
- It's possible that NIP-20 is causing problems, I can check.
I'll look into this tomorrow and let you know.