[REPORTED] Can't respond to my own question anymore on bunq Together

NDR

Hi!

Last couple of days I've been communicating with Bastiaan on bunq Together, and now all of a sudden I can't reply to my own question anymore.

This is what happens when I hover the reply button:

And this what what happened after I clicked it:

TL;DR | ANSWER

Caused by using a code block in your reply (inline code is fine). Fix:

In Firefox turn CSP off by pasting about:config in the address bar and set security.csp.enable to false;
Look up the post you used the code block in and change it to a quote block;
Then turn CSP back on (security.csp.enable to true).

Now you can use your browser of choice again ^^

Jakob-Y

André I'm experiencing similar issues on Together on the web lately. Judging from the browser console, there are some CSP issues (not the first time I've seen these crop up on Together and other bunq products). Therefore it's likely just a bug.

You can kind of work-around this by going to the page of the user that made the comment, then look for the same comment on their user page and reply from there. That has been working consistently for me. Or configure your browser to ignore CSP.

NDR

Jakob You can kind of work-around this by going to the page of the user that made the comment, then look for the same comment on their user page and reply from there.

That unfortunately doesn't work for me :/ Tried turning off AdBlockers, Shields in Brave, Private Window, VPN and as you suggested. All in Brave, Safari and Firefox. To no avail.

Jakob-Y

André Tried turning off AdBlockers, Shields in Brave, Private Window, VPN and as you suggested. All in Brave, Safari and Firefox.

Yeah it's nothing to do with Adblock, it's just a CSP being improperly configured. In Firefox for example you should be able to set security.csp.enable to false in about:config. For Chrome there's an add-on that can do this.

Best to only do this with a browser you don't actually use for anything else (at least during the time CSP is disabled), as it's an important security mechanism for the web nowadays.

Bastiaan

André Looks like a bug, which is caused by the code or output you've quoted in your response 🤔

NDR

Bastiaan You were almost right!

It's the fact that I used a code block instead of inline code. I tested it in a new thread and for me it isn't possible to respond anymore now:

https://together.bunq.com/d/45076-test-to-see-if-bunq-together-breaks

Explains why earlier this week I was only able to reply to this post from mobile as well:

https://together.bunq.com/d/44832-getting-a-authorization-request-response

NDR

Jakob Bastiaan TL;DR | ANSWER added at the top. Deleted al my posts that weren't relevant. Do you guys want me to put in a bug-report for this? Or are the devs at bunq already aware of it?

Nikoleta

André Hi there 👋

This is not yet reported from what I see. Can you please tell me if the issue persists on your end, so I can forward it further?

Jakob-Y

Nikoleta 🇧🇬🇬🇧 Hi Nikoleta just go to this thread and try to reply to any of the posts therein: https://together.bunq.com/d/45076-test-to-see-if-bunq-together-breaks It won't work if you're using a desktop browser because of the CSP issues that I have reported above and that Andre has been so kind to track down when they're happening.

Nikoleta

Jakob Thank you, I checked it and it does not work for me either. I'll check this with our team and see if we can provide a solution to this 👌

Nikoleta

Hi All!

We received an update from the developers that this is Bug in Flarum (the platform we use to host Together) and there's not a lot we can do about it, I am afraid. Your understanding would be appreciated 🙏