Welcome to the New Forum!

By Aaron Gertler 🔸 @ 2018-11-08T00:06 (+13)

Thanks for joining us as we launch the new EA Forum!

We're thrilled to be sharing the Forum with you. We hope that it will become the online hub for figuring out how to do good.

We strongly recommend that you start by reading two posts, which set out the goals for the EA Forum, and explain what's new.

The original EA Forum was built to foster intellectual progress and help the community coordinate. We've taken those ideas even further with the new version, adding new features and moderation policies to promote healthy discussion.

We hope you'll explore everything the Forum has to offer! Let us know if there's anything we can do to improve your experience; you can email us or use the blue speech box in the lower-right-hand corner.


undefined @ 2018-11-08T06:00 (+18)

Credit where credit is due: we are deeply indebted to the Less Wrong team for letting us use their codebase and providing assistance with the transformation and migration.

undefined @ 2018-11-15T04:37 (+7)

Archive.org doesn't seem to be archiving articles from the new forum properly, which would be really valuable in my opinion. When I consult a post on Archive.org, it briefly shows up, and then the post disappears, and all I see is "Sorry, we couldn't find what you were looking for." For example: https://web.archive.org/web/20181113212118/https://forum.effectivealtruism.org/posts/4r3ZpiEoWft62yPwv/crohn-s-disease.

undefined @ 2018-11-15T06:26 (+4)

Yeah, this is an unfortunate interaction with archive.org trying to be too clever about our Javascript (we send a completely fine HTML version of each page on initial pageload, and then later send the javascript, in large parts to make sure crawlers work, and this seems to work fine for Google and other crawlers, but archive.org tries to load the full JS package, then run it, and then get confused about why running the JS package from a completely separate URL with half of the files missing doesn't work).

If anyone has a solution to fixing this, I would be glad to help them create a pull request for that on our Github repository.