5 ms·
en.m. is NOT a seperate resource from en.. It is the SAME resource because it has the SAME content and because editing the content on EITHER changes the content
by jfrunyon 5y ago
en.m. is NOT a seperate resource from en.. It is the SAME resource because it has the SAME content and because editing the content on EITHER changes the content on the other. It is a different PRESENTATION of the content, which should be served at the same URL. This is WHY HTTP has such headers as Vary and Accept.
If en.m. is asking for the mobile version, then en. is asking for the desktop version, yes? So why does en. redirect to en.m. on mobile?
- thaumasiotes 5y agoSo that mobile users following existing wikipedia links can view mobile pages instead. It reflects the fact that standard pages existed before mobile pages did.
- dkonofalski 5y agoThat's not true. There are functional differences between the en.m and the en. versions.
- jfrunyon 5y agoOkay, and? Again, they both display the same content, and edits made to either one affect the other. I don't know why you think it's relevant that there are (supposedly) "functional differences", sockpuppet.
- dkonofalski 5y agoSockpuppet? And who exactly would I be sockpuppeting for? Big Wiki? It's relevant that there are functional differences because those are not presentational differences. HTML is for content, CSS is for presentation. If the HTML is different, then it's a different resource and, therefore, gets a different resource locator (URL).