Again, the point is that the non-mobile URL redirects to the mobile URL. You're not "sharing a mobile page's URL," you're just sharing the URL for the page you're on. You didn't choose to be on a mobile-specific page. And again, your user agent does matter, because that's how you got to the mobile URL in the first place. Returning HTTP redirects is not supposed to mean "here's a new URL that's different from the one you requested, oh any by the way you can't share this new URL." An HTTP redirect is supposed to mean "the resource you requested is now at a new URL."
> Again, the point is that the non-mobile URL redirects to the mobile URL.
And I would argue that this is not only the point but the problem we are talking about. It makes the m. pages appear all over the Internet although they are less suitable for some devices (they are, I'd argue, even less usable because, e.g., the page history is missing when you are not logged in).
