Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I made a modern web UI for Wikipedia

modernwiki.app

Post reply on HN
Print view View original

411–420 of 426 posts

Re: Show HN: I made a modern web UI for Wikipedia

#411

Post by leokennis »

bagelpigeon wrote: post #292

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…

Absolutely love the Wikipedia app. My two biggest wishes for it are (on iOS):

- Move the search button from the top right (very hard to reach) to the bottom menu (or some other more reachable place)

- When using “auto dark mode”, allow me to choose the not-pitch-black dark theme

Re: Show HN: I made a modern web UI for Wikipedia

#412

Post by naikrovek »

jasonkester wrote: post #406
naikrovek wrote: post #405

Earlier quoted context omitted.

> I never knew what windows called it before, so there was no way to get rid of it in settings. The settings pages aren't that big. You could read through it all in 5 minutes. Did you look? I mean sometimes things are annoying and you just can't be bothered to dig around to find the thing that turns it off, but at least in this case, it's easy: Settings > System > Multitasking > Snap windows

You can't possibly be serious. Out of curiosity, I just opened Windows 10 Settings. I see sixteen top level options. I opened the first one and it had 16 submenus, the first of which is two pages tall and has 8 additional settings links from it. Of course, Control Panel is also a place it could be hiding, and it's even bigger. So, no. One does not simply click on every single thing in settings hoping to find the anno…

I am serious. counting pages won't change how long it takes to actually understand where things are.

you don't have to read every last word... you are just trying to get a vague feel for what is in there.

takes 5 minutes, max.

Re: Show HN: I made a modern web UI for Wikipedia

#413

Post by Tmpod »

malermeister wrote: post #360
inykt wrote: post #267

Earlier quoted context omitted.

I agree, and I have already left using reddit. What's the alternative to some random content consumption (like reddit)? Like hacker news but for non-technology topics. I can suggest wiby.me 's random button to discover new sites with modern opinions.

There's various Lemmy [1] instances. Maybe one of them works for you? [1] https://join-lemmy.org/

+1 for Lemmy. The project still has quite a lot to improve on, but it is already really great! I'd love to see the community/network grow and evolve :)

disclaimer: I run lemmy.pt and use the platform on a daily basis

Re: Show HN: I made a modern web UI for Wikipedia

#414

Post by Tmpod »

Biganon wrote: post #384
eterevsky wrote: post #361

Earlier quoted context omitted.

Wikipedia's style is almost perfect except for one thing that bugs me: the line width in desktop style is unlimited, meaning in a big window it can be hundreds of symbols long, which is pretty bad from the readability standpoint ( https://baymard.com/blog/line-length-readability ).

They've changed that, but so far I've only seen the change on French Wikipedia. I think they test it on us before broader release.

Yeah they have changed some other Wikis too (like Portuguese). I think this is up to each wiki's governance (afaik they are somewhat independent) to opt-in on the new design.

I'm not sure I like it. The better line width is really welcome, but I'm tad uneasy about the rest. And as far as I can recall, it doesn't have a dark theme (yet).

Re: Show HN: I made a modern web UI for Wikipedia

#415

Post by thaumasiotes »

jfrunyon wrote: post #409
dkonofalski wrote: post #316

Earlier quoted context omitted.

I'm just jumping into this now but you're not really listening to what the parent is saying. You seem to be acknowledging their point but then ignoring what they're saying. No one is talking about what should happen. They're saying that, as you've confirmed, m.* is a separate resource from en.* because they exist as 2 separate pages on wikipedia.org. On the en.* page, people on mobile are incorrectly redirected to m.…

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…

So that mobile users following existing wikipedia links can view mobile pages instead.

It reflects the fact that standard pages existed before mobile pages did.

Re: Show HN: I made a modern web UI for Wikipedia

#416

Post by dkonofalski »

tshaddox wrote: post #407
dkonofalski wrote: post #401

Earlier quoted context omitted.

> I disagree that ordinary visitors to the website should need to or indeed should manually manipulate the URL of the page they’re on in order to share it with someone else. Everyone agrees with you on this point. You shouldn't need to manually manipulate anything but, because Wikipedia keeps a desktop resource and a mobile resource, there is a distinction and so you do need to manually manipulate it if you're sendin…

> because Wikipedia keeps a desktop resource and a mobile resource, there is a distinction and so you do need to manually manipulate it if you're sending a link from mobile to someone else and don't know their device. As I've explained, even knowing their device is not sufficient, because someone on a desktop device may prefer the "mobile" design (which is responsive) or someone on a mobile device may prefer the desk…

That wasn't my point, though. My point is that the mobile version and the desktop version are explicitly different resources. They do not load the same page. Therefore, they should have separate URLs. The very first parent comment stated that sending the "m." URL should load the mobile version of the page regardless of the device being used and they're correct. The fact that people are redirected there from the main URL is the problem, not the fact that they're sending the link to the mobile version since that's the "correct" behavior according to URL standards.

Re: Show HN: I made a modern web UI for Wikipedia

#417

Post by dkonofalski »

jfrunyon wrote: post #409
dkonofalski wrote: post #316

Earlier quoted context omitted.

I'm just jumping into this now but you're not really listening to what the parent is saying. You seem to be acknowledging their point but then ignoring what they're saying. No one is talking about what should happen. They're saying that, as you've confirmed, m.* is a separate resource from en.* because they exist as 2 separate pages on wikipedia.org. On the en.* page, people on mobile are incorrectly redirected to m.…

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…

That's not true. There are functional differences between the en.m and the en. versions.

Re: Show HN: I made a modern web UI for Wikipedia

#420

Post by seppel »

tshaddox wrote: post #281
thaumasiotes wrote: post #257

Earlier quoted context omitted.

> If I am on a public web page of a particular resource I should be able to share the URL to anyone else. Neither my user agent nor the other party's user agent should matter. This is how mobile wikipedia pages behave. What part of that do you disagree with? Share a mobile page's URL and the person following your link will see the same page you do, no matter what your user-agent is, no matter what their user-agent is…

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…

> 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).

Post reply on HN