In T323169#8398928, @Mvolz wrote:

I've checked, and the urls work locally for me.

Usually in this situation I'd assume we'd been blocked upstream for traffic, but it's odd it'd be inconsistent if that's the case.

Can you provide URLs that DO work? I've tried a few more and none of them work.

BTW on nytimes.com alone, it appears to work. Specific types of links appear to be failing. Here are some examples that fail for me:

Underlining all links by default is not a good usability choice for Wikipedia, and there is a reason why most sites with a high density of links (like Google search results pages) have moved away from underlining by default for all users. There is solid evidence that when there is a high density of links, underlining negatively impacts readability.

Tacsipacsi is correct. I also pointed out in the discussion what they say about per-page inconsistency also being potentially confusing. I personally find it useless/annoying to have the purple visited style on my watchlist and contributions page but others could feel differently. I leave it up to the team to decide how to approach it—the largest audience here is readers, who generally can’t customize the style for themselves as easily as an editor/logged in user, so I think optimizing for them and giving editors tools to customize to their preferred needs is probably fine.

No, headings are for page contents / articles not discussion. It should be
subject or topic or something similar so newbies can understand.

Ping. This is still fugly and broken looking.

Looks great!

This current desktop login UI didn't come about until after I left WMF actually, and is an unintended result of someone changing the button styles as far as I can tell. I emailed Jared about it being wrong privately when I noticed it.

In T73240#1398123, @Volker_E wrote:

WMF is caring with several people involved about getting different problems from this task being improved/resolved. Already published changes 217707 and 220610 are both addressing the issues with the serif headers in non-latin languages like Hebrew, Japanese and Korean with two approaches.

In T73240#1361394, @Tgr wrote:

FWIW Japanese, Russian and Chinese are 7%, 5% and 3% of the total pageviews respectively (all other non-Latin scripts are below 1%, though probably still a high share cumulatively). Obtaining more feedback about those languages would be a good next step.

In T73240#1351627, @Jorm wrote:

Which ones are those? I'm serious. Are there examples of software designed for use on 250+ languages that we can learn from? Or are we blazing trail here?

In T73240#1351608, @Jorm wrote:

Since (as has been argued endlessly) defining specific fonts creates insane degrees of problem with internationalization, moving towards the generic makes sense.

In T73240#1344759, @Tnegrin wrote:

Hi all -- there is a lot of context here which I've been trying to catch up on regarding the typography refresh and associated issues, so I apologize if I'm asking redundant questions.

1. There definitely seems to be an issue with our default font stack on linux (per @Quiddity) It seems inarguable we should figure out how to fix this but changing the default stack for this specific problem seems a bit coarse.

I noticed this change tonight while editing, and I just wanted to chime in to say that I really love it. Reaction on the largest Wikimedia site is so far pretty mild,[1] esp. compared to other interface changes like font updates ;-)