Adding my tinfoil hat theory outside of the report: I think this is a "hidden feature" of the desktop/web client where links with invalid message IDs (like /1) take you to the top of the channel they specify and it's simply interpreted differently by the mobile app. Adding random numbers as the message ID shows a "Messages failed to load" error, maybe because i'm going over the size of a regular ID as if you only add a few you're sent to the top. Adding non-number characters opens the browser so fully unrecognized.
Thread
Comment by Synnef