Please stop the encoding of URLs in community posts!
For whatever reason, when you add a FS URL to a community post and press enter, the URL has encoding (i.e., percent encoding) added to it, and it renders the URL unfollowable. For example, if someone is asking for help on a FS record with the URL "https://www.familysearch.org/ark:/61903/3:1:3QS7-L9W5-1ZSH?i=1587", it becomes:
Note that every colon symbol after the initial scheme and double slash gets changed into the percent encoded "&3A", and if someone tries to click through the URL, FS responds with an error:
Tech-savvy users know how to drop the bad link into a URL decoder to get a usable URL but most do not.
As a side not, I don't understand why only the colons are being encoded and not the slashes, the question mark, and the equal sign as well; all are considered "reserved characters" in RFC 3986.
Hopefully it's easy to fix.