Earlier quoted context omitted.
I understand all of that and still disagree with the claim that mobile readers should never share a Wikipedia URL containing on the "m." subdomain. I simply do not agree. They got to that URL probably without every explicitly asking for a mobile-specific page, so they ought to freely share that URL. Moreover, this "mobile" design is in fact more responsive than the "desktop" design, and some people might even prefer…
No one is saying that mobile readers shouldn't ever share a URL on the "m." subdomain (despite them, quite literally, saying that). The criticism is that Wikipedia even has 2 separate resources for the same article and that the default behavior on "m." is to share the mobile resource while that's not the same case for the "en." subdomain (or other language variants). The only thing being said is that it should be con…
Show HN: I made a modern web UI for Wikipedia
341–350 of 426 posts
Re: Show HN: I made a modern web UI for Wikipedia
#342Earlier quoted context omitted.
I agree with you except the one pain point that Wikipedia still continues to use "m.*" sub-domains for displaying mobile content. I know most people exclusively use mobile these days but I use desktop browsers for reading more than 60% of the time and its really annoying to click on a Wikipedia link on HN/Reddit and having it open the mobile site on desktop. It's OK to use m.* subdomains instead of reactive design bu…
What bothers me most about this is that if you go to www on a mobile device, it redirects you to m - that's great, and probably the "right" thing to do. There is probably a "View Desktop Version" link on the mobile page, somewhere. But if you go to the m subdomain on a desktop device, there's no easy way to get to the desktop version without manually changing the URL. If you can redirect from www to m, surely you can…
Re: Show HN: I made a modern web UI for Wikipedia
#343Earlier quoted context omitted.
I might be ok with "the mobile reactive version everywhere" if it didn't also lack a bunch of features. Not being able to easily get to the talk page to contextualize what you're reading makes the mobile site very frustrating.
Note that a link to the talk page has recently been added to the top of the mobile page.
Re: Show HN: I made a modern web UI for Wikipedia
#344Wikipedia itself is also working on a new UI: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improveme... The English Wikipedia isn't one of the "early adopter wikis" but if you visit, say, the French-language Wikipedia you can see the changes (e.g., different width to improve readability).
Re: Show HN: I made a modern web UI for Wikipedia
#345I am one of those people who actually like Wikipedia the way it is. It's what I hoped the web to become. But i am sure there are people who will appreciate your effort. Thank you for your work.
I agree with you except the one pain point that Wikipedia still continues to use "m.*" sub-domains for displaying mobile content. I know most people exclusively use mobile these days but I use desktop browsers for reading more than 60% of the time and its really annoying to click on a Wikipedia link on HN/Reddit and having it open the mobile site on desktop. It's OK to use m.* subdomains instead of reactive design bu…
Re: Show HN: I made a modern web UI for Wikipedia
#346I am one of those people who actually like Wikipedia the way it is. It's what I hoped the web to become. But i am sure there are people who will appreciate your effort. Thank you for your work.
Re: Show HN: I made a modern web UI for Wikipedia
#347Earlier quoted context omitted.
Thats a fun one to solve! @media (hover: none) and (pointer: coarse) { That allows the dev to select for devices that do not have a mouse and such rely on touch targets, to increase the sizing. I've been implementing this myself recently in our web application, while still allowing us to change the layout to fit the narrow width! I'm sure there are some devices it doesn't fit perfectly for though. This stuff is capit…
> capital-H hard You mean quote-unquote Hard?
The implementations for these have some... complications, the device sets we now deal with are huge, and making sure there are no idiosyncratic bugs that creep up when using them is legitimately a fair bit of work.
Re: Show HN: I made a modern web UI for Wikipedia
#348For folks who appreciate elements from this redesign, I'd love to humbly suggest checking out the Wikipedia iOS app from the Wikimedia Foundation. The app supports 4 reading themes, is privacy friendly, includes: truly private reading history, trending articles, a persistent TOC on iPad, on this day in history, language and multilingual support, in the news, random articles, bookmarking and folder-ing capabilities, a…
I do have a question: Wikipedia on mobile is insanely fast. Much faster than the desktop or mobile site. What media APIs do you use to pull the content for the mobile app?
Re: Show HN: I made a modern web UI for Wikipedia
#349Earlier quoted context omitted.
This is kind of incredible. Have you considered images just take up full width?
Half of cutting the images is a space saving thing. Wikipedia is a pretty big website, and (like the rest of my web presence) I'm hosting the mirror on a single small consumer hardware server. I'm keeping all the wikipedia pages as compressed HTML, and if you look at the sources you'll see it's very bare bones, most pages are like 50 Kb, yet the total is still 21 Gb. I don't think I have the space or bandwidth for se…
Have you attempted to convert them to plain text and serve those? Or is there no real savings there?