With my limited understanding, it seems like if the Discourse/Ember router does not recognize a URL, then it should trigger a full page load of that URL in order to give other parts of the stack a chance to respond to the URL instead (e.g. your web server or your back-end application). Is there a reason why this is not being done?
I don’t need the raw links very often, but I do use them to help show other people how to use Markdown. Also, being able to link to the RSS feeds and categories of a forum is important, and those links are broken because of this bug. If you have RSS feeds and categories but you cannot link to them, then it makes it pretty hard to tell people about them.
This issue has been posted at least 5 times, and the number of distinct users who either posted or liked one of those posts is currently 10.
The only good workaround is to use something like TinyURL.com. People reading my posts will not know that they have to middle click; they will assume that I posted a bad link.
As posted, those that would be interested in seeing raw / json / rss are savvy enough to know how to do it.
If you want to use the results in a post the simple fool-proof ways are educating members or putting the example inside a code fence.
I see no compelling need to use tiny URLs, but I’m probably not understanding your use case.
My use case would be linking to some part of the forum that is not known to the Discourse/Ember router (RSS feed, categories, raw text) and letting users left-click on the link to see the content that I linked to, because that is how they are accustomed to following links.
Would this analogy make sense? Imagine you had a calculator that crashed when it encountered the number 3893831283381. Then imagine the developers of the calculator questioned how often that particular number is needed.
Would it make sense for me to appeal to the CommonMark standard? I kind of thought that users should be able to read that standard in order to understand what they can post on a Discourse forum, and I am pretty sure it does not mention anything about an Ember router breaking links.