Skip to main content

When users want to reply to topics, they often open multiple topics in different tabs, but because there the CSRF token has a limited time they receive errors when they try to post. When the error 'Something went wrong’ happens, users lose the post they have typed and they need to do it again. That doesn't motivate people to help others.

I understand the CSRF token is for security, but the way it works now it feels more like it's punishing users for using the platform in a natural way.

Could the length of the CSRF be loosend or is there another option to reduce those erros? Or at least make sure the user doesn't lose their typed message when this error happens.

Even if the validity period for the token can’t be increased, the token can be validated in the background on a regular interval. That would let the UI team make the ‘Send’ button inactive if the token is expired and/or show a helper message below the response box to describe that ‘something’ that goes wrong before it goes wrong.