4 ms·
It isn't done out of malice. People simply copy paste whatever is in their browser. "m." subdomains are just a totally outdated concept and I wish they would d
by paxys 5y ago
It isn't done out of malice. People simply copy paste whatever is in their browser.
"m." subdomains are just a totally outdated concept and I wish they would disappear entirely. It is trivial for the web server to detect what device type, OS, screen size etc. the user is on and serve content accordingly.
- handrous 5y agoI use the "m." subdomain on some sites on purpose, when on the desktop—though not on Wikipedia, as they cut so much content out of the "m" site, it's awful, I don't even like it on mobile, though if it actually had all the content I'd probably prefer it everywhere. That's more convenient than having to change my user agent or simply having mobile versions unavailable unless I shrink my browser window down to phone-sized.
- grlass 5y agoI prefer m.xkcd.com because the alt-text is easier to access
- deleted 5y ago[deleted]
- dspillett 5y ago> "m." subdomains are just a totally outdated concept Yes. Some might argue otherwise, but I'm with you there except… … sometimes the mobile version of a page is preferable as it cuts out a load of crap including adverts and other distractions, just giving you the information actually being linked to. So "m." type links or other "force mobile view" options can be accidentally useful for a purpose beyond what their designer intended. > It is trivial for the web server to detect what device [properties] No, it is not trivial to do this reliably server-side with no client-side assistance. It is much better where possible to do it client-side with well-designed CSS (maybe, but not necessarily, making use of media queries and such). There is an exception here too: if you want to send less data to the mobile client, instead of sending everything you would send to others and adjusting styles to alter the display for small screens and finger-based input, then you need to either try detect the UA's properties or given the user an explicit "full or minimal" option (which may put you back to offering an "m." URL or equivalent so a user can jump direct to the minimal version).
- marcosdumay 5y agoIf your site is not responsible and you have a mobile version, please, place a mobile selector on the header of your pages, and a cookie on the client with the option.
- atatatat 5y agoWhat about all of the users and clients who don't allow you to place cookies?
- marcosdumay 5y agoWell, letting your users tell you the correct answer does not stop you from trying to guess all you want when they don't tell you anything.
- deleted 5y ago[deleted]
- onkoe 5y agoIt is out of malice. And I have the same malice https://en.m.wikipedia.org/wiki/Wikipedia%3AEnable_mobile_version https://en.m.wikipedia.org/wiki/Wikipedia%3AEnable_mobile_ve...
- noobermin 5y agoDoesn't a link to a wiki article automatically redirect to a mobile version anyway if you're on mobile?
- willio58 5y agoThese days if you follow responsive design (why wouldn’t you?) you’ll never need an m. subdomain. I don’t think Wikipedia should have any less functionality or information on mobile.