It seems like you updated your webpage in the wake of the meme incident. But it has made it unbearable to read. Whilst I was able to read the article in reader mode, the ~ page is virtually an eye sore to browse right now.
Yeah, sorry, that came a bit harsh. I’m just a bit salty, because i dislike monospace and white-on-black for reading. But i’m working on something, that lets the user choose the reading settings. In the meantime, i just create a usercss (Stylus) for pages i see often.
But that’s another reason i’m salty; please don’t do * {…} CSS hacks. Just set the rule on body, because children inherit, if not set otherwise. And * is the worst for performance, use the rightmost selector instead.
no problem! i’m frequently described as “abrasive” so i guess what goes around comes around…
i do appreciate the CSS tip(s) – that stylesheet is a few years old with many alterations over time, so there are bunch of weird hacks that i’m not even sure why they’re there. off the top of my head, for some reason the header is a div-within-a-div: #header and #header_internal. no idea why. :P
Your website is refreshingly simple and also manages to be unique looking. I like it!
thank you! html pandoc template + nginx; i write my pages in markdown.
It seems like you updated your webpage in the wake of the meme incident. But it has made it unbearable to read. Whilst I was able to read the article in reader mode, the ~ page is virtually an eye sore to browse right now.
shit i forgot about that, thank you for the reminder
I don’t. Please make the header and footer smaller or non-floating on mobile. And padding of the text is too wide too.
And on desktop,
* {…}rules are not good behavior. Firefox complains about quirks mode too.Edit: this is about the website, the tech, not your blog. Didn’t got to read that yet.
yeah, it’s pretty unoptimized for mobile. on my todo list.
where does firefox complain about that?
also i should change the license footer, you’re right
Yeah, sorry, that came a bit harsh. I’m just a bit salty, because i dislike monospace and white-on-black for reading. But i’m working on something, that lets the user choose the reading settings. In the meantime, i just create a usercss (Stylus) for pages i see often.
But that’s another reason i’m salty; please don’t do
* {…}CSS hacks. Just set the rule onbody, because children inherit, if not set otherwise. And*is the worst for performance, use the rightmost selector instead.no problem! i’m frequently described as “abrasive” so i guess what goes around comes around…
i do appreciate the CSS tip(s) – that stylesheet is a few years old with many alterations over time, so there are bunch of weird hacks that i’m not even sure why they’re there. off the top of my head, for some reason the header is a
div-within-a-div:#headerand#header_internal. no idea why. :P