You can link to a topic with just the number: /topic/1. Everything after that is fine. If your browser copy pastes urls like that there isn't much else that can be done.
Issues with Posting from Behind Untangle or Watchguard
We are guessing that this is a Socket.io problem. Users sitting behind certain firewalls, namely Untangle and Watchguard, can see the site now (did not used to even be able to do that) but cannot post.
@scottalanmiller This post outlines the main issue, seems a lot of firewalls will block websockets on any port, however most will allow them if they're on port 443 (usually for remote desktop reasons).
Not sure what the best plan of action is here though. I read on the linked article above that Chrome does something slightly different and can sometimes work with Websockets on any port.
@scottalanmiller I have noticed this when i am at work. Some places i visit have a watchguard firewall and i am unable to connect properly to my forum. This forum seems to work ok though.
We've had people test Chrome, FF and IE... none work at the sites with these two firewall products, sadly. HTTPS might work. That's a pain until free certs are widely available Not practical to have tons of them.