Official Pixelation Skin!

[surt]

For some reason text looks perfectly sharp and readable on my phone in the Android version of Chrome.

[Indigo]

Thanks for the kind words everyone.  I'm really happy everyone is liking it

I just pushed a number of fixes including the unread posts/replies pages and font tweaks

@Surt:  Can you post screenshots so I can contrast the two?

[Ai]

Before the fix was pushed, fonts were clear but the POST REPLY /FEATURED/etc text looked misaligned. Now all texts are some amount blurry. I know that's the opposite of what others were reporting. Firefox 44.0.2 on Arch Linux x86_64, using infinality-bundle for font rendering.

Screenshot link with slight edit (inset blown-up section)

Doesn't seem too bad, but is especially apparent on the POST REPLY / FEATURED font.
Edit: I think the text zoom level may be wrong (non-default) in this shot. However, I just checked at default zoom and the blurring is equally present.

[Indigo]

if this is the degree of blurring that people are reporting, then it's way too subtle for me to care about - that's just OS font-antialiasing.  That looks fine to me.  I don't think there's much I can do to improve it - that's just how fonts are rendered by the browser/OS

[surt]

Looks much blurrier than that for me Chrome on windows:

It looks like it isn't doing any hinting.

Android I think it's just the much higher pixel density masking the blur.

With the old theme text rendered fine for me.

[Ai]

Hmm. To me that also looks like OS font rendering.
 * Stem snapping on the H is different
 * Subpixel handling looks less sophisticated (but can't tell this for sure.. maybe just less sharpening applied.)
I guess I could probably also get a result like that by adjusting Infinality's settings.

At the moment I'm considering the blurring as only relevant on the POST REPLY/ TOPIC SUMMARY... font.. which I think probably IS badly hinted.

EDIT: with the help of woff2sfnt and FontForge.. it looks like it isn't hinted at all. I tried to autohint it, but encountered an error about characters containing "self-intersecting" paths when generating a TTF

EDIT2: hm, actually looks better when I dragged it into GIMP (which renders exactly the same, but without subpixel offsets). Also looks pretty decent with antialiasing off (except the left upright of the H, which looks too thin unAAed). I'll see if I can force it to autohint.

[Gil]

Yeah, I think the issue here is that the fonts used are badly hinted. For me, I mainly dislike the hinting on the main text font.

[A2J2TIWARI]

Amazing work guys! Really really great! I opened the site and was like "WOOOAAHHH!!"

Thanks for all this

[HarveyDentMustDie]

I'm so glad to see that new skin is officially activated. Great job guys, very slick and modern design.

[Parkerbaby]

In the title of the Re: part at the top of posts, the 'l' and 'i' are identical.