Error
Unrecognized LW server error:
Field "fmCrosspost" of type "CrosspostOutput" must have a selection of subfields. Did you mean "fmCrosspost { ... }"?
Unrecognized LW server error:
Field "fmCrosspost" of type "CrosspostOutput" must have a selection of subfields. Did you mean "fmCrosspost { ... }"?
Relevant Beta Feature for LessWrong posts: Google-Docs-like editing
This doesn’t work on public posts.
Alternative MVP
Copying the Wiki feature and renaming it “Community Posts Beta”
Appears in menu sidebar
It’s another category of post like short forms but it appears in the regular homepage with an icon to signal that it’s collaborative. E.g. something like this (this is Spotify collaborative playlists icon for the curious):
The launch could be as simple as getting 3 EA groups to use the feature as part of their next group activity
E.g. spend 2 hours in groups of 3-4 people choosing a question of interest (e.g. like Nathan’s examples in the “more detail section”) basically try to make progress on it. It could be good to find a list of questions we actually think are important.
maybe they try to find the main arguments for and against around a cause, and then try to find evidence to evaluate the strength of the claims
groups can then publish the results, and future groups could either choose to improve existing posts if the topic is interesting or just make their own.
Once LW’s realtime editing feature is more developed that would be the ideal thing for community posts
To be clear, this is a regular post that be edited by anyone. So it’s quite unlike the EA Forum Wiki.
I could see that it would be better to have another name for what you’re suggesting than “wiki posts”, since there is a risk of conflation between that and the EA Forum wiki articles.
What would you suggest? Collaborative posts?
Yeah, that’s a plausible candidate. Or something else in that ballpark. Though I guess you want to distinguish them from posts that are co-authored in the standard way.
Better?
Haha, you’re implementing your own system. :)
That’s an interesting suggestion. I guess one objection could be that there is a risk of conflation with the community tag. Otoh, I guess that almost any term you could reasonably use is used for something else as well, so I’m unsure how much weight to put on that. It seems like less of an issue than it is regarding the term “Wiki”.
Alternatively, wiki pages could have karma and be creatable by anyone. That would solve the problem too.
“Open posts” perhaps?
If you want to make suggestions to this post, reply and I’ll make you a coathor and you can add them yourself.
Thanks for posting this Nathan. It brings to mind community wiki answers on stack overflow, which I do think are useful.
My current best guess is that we would not prioritize this soon, though I have added it to our triage queue.
Though my point is that very little tech needs to be built.
The most minimal of MVPs is to change norms on the wiki.
To achieve this you could create a “community user” and share the pass on top of the post. People would login with it, make changes and explain them in the comments. Not sure if sharing the pass would be against the Forum’s rules.
That would be a massive effort for people to do and I’m almost certain few would. Cool idea though.