361–370 of 426 posts
I 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.
Otherwise, OP, you have injected cancer in to a cancer free patient and called it a remedy.
Earlier quoted context omitted.
Whoa, I had no clue about these key-combos. So handy! Thanks!! For anyone curious, MS has a useful summary of how this works here: https://support.microsoft.com/en-us/windows/snap-your-window...
No problem, I did it by accident, and you can also drag the windows to the corners and overshoot to have them, top is full, left and right is half that side, the link you posted mentions that, I am actually surprised you never accidentally discovered either. I have that in KDE as well.
Earlier quoted context omitted.
I just used win+ arrow keys, never missed the resizing.
Whoa, I had no clue about these key-combos. So handy! Thanks!! For anyone curious, MS has a useful summary of how this works here: https://support.microsoft.com/en-us/windows/snap-your-window...
I never knew what windows called it before, so there was no way to get rid of it in settings.
Why you need this permission "Read your browsing history"? I think you only need access to: "*://*.wikipedia.org/*"
If “modern web UI” means “performs none of the functions of a web Ui” then you nailed it.
For 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…
Earlier quoted context omitted.
This is hard and often done wrong- mobile phones are usually high dpi and have gotten quite large, so it can be hard to distinguish between a large phone and half a desktop screen. Some people get quite annoyed by being bumped into a mobile experience when you resize your window from fullscreen on a laptop.
I also get annoyed when I get bumped to the "mobile" "experience" even when I'm on a smartphone. With reactive design, "request desktop site" generally doesn't work, either. I really, REALLY prefer desktop mode for almost everything, relying on pinch to zoom.
It shouldn't, because with proper reactive design therre are no "mobile" and "desktop" versions but only one version that adapts to the viewport size. If you want a larger viewport that should be solved at the browser level by providing the website with a larger viewport. Seems firefox behaves this way while chrome does something weird that increases the viewport a bit but then still "intelligently" scales some text.
Earlier quoted context omitted.
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…
Gotchya. All good then. Excellent work and insight :) Have you attempted to convert them to plain text and serve those? Or is there no real savings there?