Less Wrong is a community blog devoted to refining the art of human rationality. Please visit our About page for more information.

bogus comments on Open thread, January 29 - ∞ - Less Wrong Discussion

5 Post author: LessWrong 28 January 2018 10:44PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (34)

You are viewing a single comment's thread. Show more comments above.

Comment author: bogus 29 January 2018 03:44:07PM 5 points [-]

There is an alternative interface to the new site at Greater Wrong. It has a few problems (namely, it's hard to access archived content; all you get is a day to day listing of posts) but compared to Lesser Wrong it's at least usable. LW2 should support it officially in addition to the Lesser Wrong website, and perhaps even add features like logging in and posting content through it.

Comment author: saturn 29 January 2018 07:08:02PM *  3 points [-]

Hi, I'm the one who created Greater Wrong. I'm intending to announce it more widely once it doesn't have so many conspicuously missing features, but it's something I'm working on in my spare time so progress is somewhat gradual. You can, however, already log in and post comments. You can use your existing LW 2.0 username/password or create a new one. Let me know if you have any problems.

Comment author: username2 30 January 2018 04:48:58PM 2 points [-]

Thank you very much. I read LW primarily for the discussions that are spurred by posts/articles and the comments are effectively impossible for me to read with the standard interface. On a small glance/browse I'm very encouraged about trying Greaterwrong as my regular reading mode.

Comment author: LessWrong 30 January 2018 09:52:22PM *  1 point [-]

Excellent job. You got bonus points for writing it in Lisp. I assume you've read SICP?

Comment author: saturn 02 February 2018 09:55:12AM 0 points [-]

Parts of it, anyway.

Comment author: efenj 09 February 2018 03:23:07PM 0 points [-]

Thanks very much!

If the only thing that remained of Greater Wrong was the javascript-free access to the Less(er)Wrong homepage (I mostly disabled js in my browser in the aftermath of spectre, plus js somehow makes scrolling (sic!) on LesserWrong agonisingly slow), it would be a huge value-added for me! I also like the accesskey-based shortcuts for home, featured etc.

However, it's also a much nicer and faster interface for reading the comments and even the content!

(Testing with js enabled: no noticeable slowness; the comment navigation system is neat, though I doubt whether I'd actually use it.)

Comment author: cousin_it 30 January 2018 01:01:08PM *  0 points [-]

Thank you for doing this!

Comment author: bogus 29 January 2018 08:37:35PM *  0 points [-]

Thanks for adding this, then! Personally, I'm just waiting to create an account/log in there until the 'final' LW-importation goes through. (Users who were late setting the e-mails to their accounts here did not have these imported to LW2 initially, which can lead to all sorts of problems. But a new importation from LW's updated user list can fix this - or maybe it can't, but then there's no loss in just creating a new user!)

It would be nice to have more than just a single page of 'new' content, since as is, it can even be hard to check out all recent posts from the past few days, or whatever. It's great that the archive is available though. (Similarly, it would be great if we could access more of a user's posting and commenting history directly from their user page. On LW and LW2, you can see everything that a user has posted to the site simply by browsing from the userpage, and many LW users do rely on this feature as a de-facto 'index' of what they've contributed here.)

Comment author: saturn 02 February 2018 09:54:39AM 2 points [-]

It would be nice to have more than just a single page of 'new' content, since as is, it can even be hard to check out all recent posts from the past few days [...] more of a user's posting and commenting history

Done :)

Comment author: cousin_it 03 February 2018 12:13:22AM *  1 point [-]

I was a bit bothered by the noisy look of the front page, so I took a shot at restyling it: screenshot, pastebin. Not insisting that you should use it (I'm using it as a browser stylesheet anyway) but just thought I'd share.

Edit: whoops, this affects other pages in surprising ways. I'll try to fix it tomorrow.

Comment author: SaidAchmiz 06 February 2018 04:54:07AM 1 point [-]

Thanks for this—it's great! I went ahead and tweaked your modification a bit and elaborated on it, and now it's available on GW as a selectable theme (note the theme selector widget at the top-left of the page).

Any further suggestions on improving the theme are welcome! (See here for the grey-theme CSS as it currently stands.)

P.S. If anyone else wants to post or send us additional alternate themes, please do!

Comment author: cousin_it 06 February 2018 03:51:46PM *  0 points [-]

Very cool, and thank you for cleaning it up!

I'm not very happy about the typeface used for body text, the longer paragraphs kinda make my eyes bleed. Arial at 1rem would look more scannable to me. But this might be subjective, and in any case I can just fix it for myself.

Comment author: SaidAchmiz 06 February 2018 06:15:48PM *  0 points [-]

Yeah, I totally understand your complaint. Take the following as me explaining why it (and many similar things) are done this way, and definitely not dismissing what you're saying:

Fonts are tricky.

It's hard to appreciate how tricky they are, until you try and make a website that's readable for everyone, everywhere.

Rendering bugs, for example. You get a font that looks great on a Mac—it looks terrible on Windows. You find one that looks good on Windows, it glitches out on Linux.

Then there's things that aren't "bugs" but more like "differences"—rendered font weight is different on Mac vs. Windows/Linux.

There's browser differences: Chrome and Firefox (or, more precisely, Webkit/Blink and Gecko) anti-alias letterforms differently (at least on Windows).

There's device differences: what looks good on a hi-DPI screen doesn't look so great on a lower-res screen (and vice-versa!).

Of course these things interact. (Otherwise it would be too easy, right?) Chrome on a Retina Macbook vs. Firefox on the same Macbook vs. Firefox on a Linux box vs. Safari on an iPhone vs. Safari on an iMac vs. Opera on the same iMac vs. Opera on Windows vs. Chrome on Windows vs. etc. etc. etc.—all are ever so slightly different in how they will render the very same text.

Sometimes you can correct for this. Pick a font that works best on most platforms; detect the remaining platforms, serve a different font to those. (GreaterWrong does this for the UI font—Mac and Linux users get one font, Windows users get a slightly different font. I am betting 99% of people won't ever notice or realize this… which is the point, of course; if we didn't take this additional step, then people would notice, because there'd be visible glitches.)

Often, though, you can't. (For example, there's a particular longstanding browser bug in how text renders on mobile devices (specifically having to do with hyphenation) that we can't properly fix, because there's no way to reliably detect whether any given client can or can't do that particular thing correctly. This is why the text column is left-aligned on mobile clients. The alternative would be having most users see well-formatted text, but having a large minority of users see very glitchy, hard-to-read text; this is unacceptable.)

And, as you say, some things are just subjective (at least in part; it's almost never totally subjective).

So while I absolutely try to ensure that everyone gets as close to a perfect reading experience as possible… compromises are inevitable (and I really do mean "inevitable", not "meh, too much work"; no amount of effort short of "literally be Apple or Google, and maybe not even then" would fully solve this problem).


All that having been said, though, could you tell me what sort of device/OS/browser/etc. you're viewing the site on? Every piece of user feedback helps! :)


Edited to add: Whatever corrections you make, even if we don't/can't adopt them into the "official" version of the theme, I encourage you to submit them to userstyles.org—it's likely that some other people will share your preference, and this'll make the browsing experience better for at least some of them.

Comment author: cousin_it 06 February 2018 08:06:09PM *  0 points [-]

Maybe something like this? Before, after. I'm not insisting that you use it, but it's closer to what I had in mind...

Comment author: SaidAchmiz 06 February 2018 09:38:33PM *  0 points [-]

The title / post-meta styling is an improvement, I agree. As for the body test—what OS / browser / etc. is that?

Edit: I ask because, from what I've seen, Fira Sans is more readable on more platform/browser/device combinations than Concourse, as a body text font. In this case it's closer to the opposite… let me ask you this: how much of the difference between the two versions you screenshotted, for you, is made by the body text size, as distinct from the typeface per se?