cooper12

On the mobile site, go to the settings in the sidebar and enable Advanced Mode.

And no, they won't ever get rid of categories. It's just that the phone variants of the site are very heavily geared towards a specific type of reader, at the expense of editors or other types of users. They have been trying to address this over incremental updates though, such as now showing talk pages.

> they gave each language a different Cyrillic orthography than the rest to fragment them even further

That doesn't seem correct to me. Different languages require different orthographies because they have different phonetics. Compare the Latin script when used for English to German to Vietnamese to Turkish. Same thing with the Arabic script with Persian and Urdu. When tailored orthographies aren't used, the written representation becomes a poor representation of speech. Though even then it might not have been a perfect fit in the first place, requiring digraphs or diacritics. Or the spoken language can diverge.

They're also using a monospaced font for the body text and aren't limiting the line length.

    ffmpeg -i foo.mp4 -c:v h264_videotoolbox -b:v 1600k foo_out.mp4

On macOS, this uses hardware acceleration to reencode a video at a lower bitrate. My macbook is from 2012, so this does make a notable difference. There's also "hevc_videotoolbox" for H.265 if your machine supports it.

I read it as "[you] double-time[d] me, oxface", with "ox face" being meant as an insult.

SKIP is about matching the kanji to a pattern and counting the strokes of the two portions. This is more about inputting the kanji's constituent parts themselves.

For example, say we have the kanji 訓. For a SKIP-based lookup, you'd see this as 言|川, and you probably know that's 7 and 3 strokes. Whereas with this approach, you could type in the parts, e.g. いう (backspace) to get 言 and かわ to get 川. A lot faster when kanji have many parts or you're not so sure about the stroke counts. Yes, SKIP would be more helpful if you don't know the parts.

Setting your user agent would only be considered hacking by the same people who think the Internet is a series of pipes. The browsers themselves copy each other's user agents for interoperability, so it's far past the point that changing it to look like another agent would be considered devious.

OED (an older edition):

> the process of renovating and improving a house or district so that it conforms to middle-class taste

In this case, it's making the internet conform to Google's taste. Seems to be an appropriate use of the term, even if in the more recent sense we think of it as displacement of people or local businesses.

SSR = Server-side Rendering, if anyone else was unfamiliar like me.