Like last month, this is a once-monthly updates for LessWrong team activities and announcements.
Please also feel free to use the comments section on this post as a Schelling point to give feedback, file bug reports, or ask questions you have about the site. (You can also email us, ask a question, use Intercom, or message us via our FB page.)
We successfully shipped Link Previews in September. Now when you hover of an embedded link you get a pop-up, for internal links to LessWrong posts you get a preview. See the full announcement here.
Improvements to the Community Map
In the course of supporting SSC Meetups Everywhere, we've made a few improvements to the community map on our Community page.
- In addition to Groups and Events, now users can also add themselves to the map together with some info about what they're looking for or willing to do, e.g. someone can list themselves as willing to arrange local meetups if there are enough people in their area.
- You can sign up for event and group notifications, as well as notifications for once there are N people within a given radius from you.
- The UI has been improved.
- The map is now more performant.
For more information about the LessWrong community section, including the different event types (LW/SSC/EA/MIRIx), see the relevant section of our FAQ.
Although we hoped to deliver them in September, the subscriptions overhaul and new editor are still under works. Unless things go terribly wrong, they should be released this month. Convert Comments to Posts is currently blocked behind some tech debt.
We might announce plans for additional near-term features once we've completed our Q4 planning.
On September 26th, 1983, Stanislav Petrov, a Russian lieutenant colonel, decided not to report an [in fact false] alarm of incoming missiles from the US, thereby likely preventing nuclear war. September 26 has since become a Rationalist community holiday celebrating the calamity that did not occur that day and reminding us of the dangers present in a world powerful dual-use technologies.
LessWrong commemorated Petrov Day this year from the unilateralist curse angle and turned the site into a live exercise and experiment. A big red button was placed on the homepage and 125 users were given launch codes with the power to bring down the frontpage for 24 hours.
The LessWrong frontpage on Petrov Day
Though some considered it, hearteningly, no one entered launch codes and LessWrong remained safe.
Read the full debrief here.
September was the month for SSC Meetups Everywhere. To support this, the LessWrong team placed the community map on the frontpage for most of the month. Over a hundred SSC Everywhere meetups took place over the month and Scott Alexander, MIRI team members, and a few others went on tour to visit them.
Meetups for LessWrong, Slate Star Codex, Effective Altruism, and MIRIx continue to happen throughout the year. Check them out on the community page.
Curated Emails are currently down
Users subscribed to emails for curated posts may have noticed these haven't been coming through. We're aware and have a fix, however the fix is risky to the rest of the site and we've been waiting for a good opportunity to test it, hopefully soon. The RSS feed for posts, including curated posts, is working fine.
Q3 was Metrics Quarter
In Q3, the LessWrong team experimented with targeting a metric. While we have no expectation that any simple metrics could reliably track our long-term goals and values, it seemed instructive to see how much we could move a simple metric if we really tried. For a quarter, we attempted to follow Paul Graham's advice and get 7% weekly growth on a value that mattered.
Stand by for a post describing the experiment and how it went.
Ways to Follow LessWrong
We've been expanding the number of ways people can consume LessWrong content beyond the site. These now include:
- Email (to be restored soon)
- [Regular posts being made since July] Facebook
- [New account] Twitter: @lesswrong
- [New account] LinkedIn
The Facebook, Twitter, and LinkedIn accounts receive regular updates M/W/F of a mix of curated posts, top all-time content, and outstanding new content.
Feedback & Support
The team can be reached for feedback and support via:
- Comment on this post
- Intercom (icon in the bottom right, you might have to edit your user settings)
- Email us at email@example.com or firstname.lastname@example.org
- Ask a question on www.lesswrong.com/questions
- [New] by messaging us on our Facebook page.
Hints & Tips: The All Posts Page
LessWrong has a powerful All Posts page which can serve as an alternative to the frontpage. It's URL is www.lesswrong.com/allPosts. The All Posts page has:
On textboxes for comments/posts, I noticed that the documentation is for the rich text editor regardless of what option I have set in preferences (I have markdown). To be clear, markdown formatting works; it's just that the documentation tells me to e.g. use Cmd-4 for LaTeX rather than dollar signs. I tried switching to rich text and back to markdown, but the problem persists.
report incoming missiles
pass on a report of incoming missiles [which was a false alarm]
Looking forward to this:
Errata: The RSS link in the "Ways to Follow LessWrong" section leads to the Facebook page.
What's the typical timeline for a post to be approved by the moderators? I'd just like to know so I can plan accordingly.
It's generally a few hours on average.
Note that the very first time you post you have to be approved manually, as part of our 'deal with spam' plan. Afterwards, it'll still be a few hours before a mod will reliably have decided whether to frontpage your post, but it'll at least show up reliably on /allPosts, personal-blog-enabled-frontpages, and in recent discussion.
(We're also planning to make a change where, once we've moved something to frontpage, it's "bumped" to the front of the frontpage a second time, so days where it ends up taking awhile before a mod reviews the frontpage queue, you won't be at a disadvantage in terms of frontpage-eyeballs, although this unfortunately isn't true yet)
On LessWrong's GraphiQL, I noticed that hovering over keywords no longer provides documentation help. (See here for what the hover-over used to look like.) Would it be possible to turn this back on?
Huh, don't think that was intentional. Will look into it.