I had forgotten that I had previously answered this issue here ! There, I noted that
at the time, Roamresearch told me over email that they would fix this issue.
It would be better for us not to update Hook to deal with non-RFC compliant websites. Customer may wish to ask Roam for status/ETA about when they will change their construction of URLs.
Hook could in the future provide an advanced preference to deal with websites that treat “#” differently (possible involving a service that lists such websites), but I’d rather postpone that.