User Profile


Recent Posts

Curated Posts
starCurated - Recent, high quality posts selected by the LessWrong moderation team.
rss_feed Create an RSS Feed
Frontpage Posts
Posts meeting our frontpage guidelines: • interesting, insightful, useful • aim to explain, not to persuade • avoid meta discussion • relevant to people whether or not they are involved with the LessWrong community.
(includes curated content and frontpage posts)
rss_feed Create an RSS Feed
Personal Blogposts
personPersonal blogposts by LessWrong users (as well as curated and frontpage).
rss_feed Create an RSS Feed

LW client-side comment improvements

1 min read
Show Highlightsubdirectory_arrow_left

The Stable State is Broken

Show Highlightsubdirectory_arrow_left

Recent Comments

I think - I hope - we could discuss most of those without getting into the more culture war-y parts, if there were sufficiently strong norms against culture war discussions in general.

Maybe just opt-in rather than opt-out would be sufficient, though. That is, you could explicitly choose to allow C...(read more)

I would strongly support just banning culture war stuff from LW 2.0. Those conversations can be fun, but they require disproportionately large amounts of work to keep the light / heat ratio decent (or indeed > 0), and they tend to dominate any larger conversation they enter. Besides, there's enough ...(read more)

Without commenting on the merits and costs of children at Solstice or how they ought to be addressed:

Having attended the East Bay solstice both this year and last, it was my impression that there was significantly more noise made by children during parts when the audience was otherwise quiet this ...(read more)

> It is if we define a utility function with a strict failure mode for TotalSuffering > 0.

Yeah, but... we don't.

(Below I'm going to address that case specifically. However, more generally, defining utility functions which assign zero utility to a broad class of possible worlds is a problem, beca...(read more)

Good catch. Don't think I'm going to change the behavior, as there's complex cases where there's no obvious behavior: suppose you have a highly upvoted comment, whose parent and grandparent are both below the threshold. Do you color it in the widget differently from its parents? Do you expand both i...(read more)

Huh. Try the most recent version (as of just now).

The way it currently works - at least, the way I designed it, and the way it seems to work for me - is that it doesn't remember anything between visits, but rather determines which comments are new since your last visit by looking at the highlight provided by LW's server. If there were comments made...(read more)

Ah. That's much more work, since there's no way of knowing if there's new comments in such a situation without fetching all of those pages. I might make that happen at some point, but not tonight.

It seems to work for me. "Continue this thread" brings you to a new page, so you'll have to set the time again, is all. Comments under a "Load more" won't be properly highlighted until you click in and out of the time textbox after loading them.