We don’t have any plans yet; we might circle back in a year and build a leaderboard, or we might not. (It’s also possible for third-parties to do that with our API). If we do anything like that, I promise the scoring will be incentive-compatible.
Kinda. There’s source code here and you can poke around the API in graphiql. (We don’t promise not to change things without warning.) When you get the HTML content of a post/comment it will contain elements that look like <div data-elicit-id="tYHTHHcAdR4W4XzHC">Prediction</div> (the attribute name is a holdover from when we had an offsite integration with Elicit). For example, your prediction “Somebody (possibly Screwtape) builds an integration between Fatebook.io and the LessWrong prediction UI by the end of July 2025″ has ID tYHTHHcAdR4W4XzHC. A graphql query to get the results:
We don’t have any plans yet; we might circle back in a year and build a leaderboard, or we might not. (It’s also possible for third-parties to do that with our API). If we do anything like that, I promise the scoring will be incentive-compatible.
. . . Okay, I’ll bite.
Edit: And-
Now, I don’t suppose that LessWrong prediction API is documented anywhere?Kinda. There’s source code here and you can poke around the API in graphiql. (We don’t promise not to change things without warning.) When you get the HTML content of a post/comment it will contain elements that look like
<div data-elicit-id="tYHTHHcAdR4W4XzHC">Prediction</div>
(the attribute name is a holdover from when we had an offsite integration with Elicit). For example, your prediction “Somebody (possibly Screwtape) builds an integration between Fatebook.io and the LessWrong prediction UI by the end of July 2025″ has IDtYHTHHcAdR4W4XzHC
. A graphql query to get the results: