I agree; many of those concerns seem fairly dominated by the question of how to get a well-aligned ASI, either in the sense that they'd be quite difficult to solve in reasonable timeframes, or in the sense that they'd be rendered moot.  (Perhaps not all of them, though even in those cases I think the correct approach(es) to tackling them start out looking remarkably similar to the sorts of work you might do about AI risk if you had a lot more time than we seem to have right now.)

Oh, unfortunate.  Will think about how to reconcile those, then.

Yeah, you click the "paragraph" dropdown and change it to one of the heading options while having your cursor on the relevant line of text.

@Raemon and I have shipped some improvements to the editor experience.

The two major changes displayed above are:

1. @Raemon cleaned up the options at the bottom of the editor.  They used to look like this:
    

   

2. I implemented a basic command palette, available both in the post and comment editor.  To open it, press ctrl/cmd + shift + p (same as the VSCode keybinding), or ctrl/cmd + /, because the first keybinding is "open an incognito window" on Firefox.  The goal is to improve the discoverability and accessibility of various editor features, some of which previously required you to open the toolbar to use.
   
   It behaves the same way as most other command palettes - esc to exit, up/down arrow to cycle, enter to execute the selected command, and also shows you the native keybindings for executing any given command.

Another minor QoL improvement is the right-click behavior in the editor.  Previously, the only reliable way to open the inline toolbar was to manually highlight some text.  If you tried to right-click to open the toolbar, this would happen to you:

Now it's this:

(Note that most of the functionality inside of the toolbar is either trivial or available more easily via the command palette - I guess it's now easier to convert something to a heading, block quote, or list?)

As always, let us know if you run into problems, or have other thoughts on the changes.

Thanks for the report, this should be fixed now.

(Also, to clarify, we were already on React - it's mostly other bits of framework glue that got tossed out/replaced/etc.)

We shipped "draft comments" earlier today.  Next to the "Submit" button, you should see a drop-down menu (with only one item), which lets you save a comment as a draft.  Draft comments will be visible underneath the comment input on the posts they're responding to, and all of them will be visible on your profile page, underneath your post draft list.  Big thanks to the EA forum for building the feature!

Please let us know if you encounter any bugs/mishaps with them.

Concerning!  Intercom shows up for me on Firefox (macos), will see if there's anything in the logs.  How does the LLM integration being broken present itself?

You have a typo where the second instance of let belief = null; should presumably be let belief = undefined;.

(Also, I think "It'd print an error saying that foobar is not defined" is false?  Confirmed by going to the browser console and running that two-liner; it just prints undefined to the console.)

Interesting mapping, otherwise!

• They very briefly discuss automated AI alignment research as a proposal for mitigating AI risk, but their arguments against that plan do not respond to the most thoughtful versions of these plans. (In their defense, the most thoughtful versions of these plans basically haven't been published, though Ryan Greenblatt is going to publish a detailed version of this plan soon. And I think that there are several people who have pretty thoughtful versions of these plans, haven't written them up (at least publicly), but do discuss them in person.)

Am a bit confused by this section - did you think that part 3 was awful because it didn't respond to (as yet unpublished) plans, or for some other reason?