This is mostly unrelated and out of scope for your feature, but from time to time I’ve been wondering about what the minimal workflow for correcting typos would be, for both authors and readers. Some options:
Commenting with a list of typos: The current version. Requires making a list while reading, then putting it in a comment; other users might suggest duplicate typos; meta comments like typos detract from other comments; plus they don’t get visibly deprecated once addressed by the author; etc.
Typo comments (or suggested edits) à la Google Docs or this new LW feature: Typo suggestions include the location of the typo; other users who want to suggest the typo see that it’s already been noticed and don’t duplicate it; this meta stuff is clearly separated from normal LW comments; etc. Typo suggestions still don’t get visibly deprecated once addressed by the author, unless the author can delete comments.
Suggesting changes in a version control system like Git: While forking on Github has tons of overhead, the basic workflow is quite simple: users suggest typo edits to the document, and then the author can confirm or reject them with one button. However, if typo suggestions are associated with users, this might have some weird implications wrt licensing and authorship. (IIRC some entertainment businesses like Wizards of the Coast don’t accept user suggestions per company policy, lest the suggesters later claim that their suggestion was implemented without compensation.)
This is mostly unrelated and out of scope for your feature, but from time to time I’ve been wondering about what the minimal workflow for correcting typos would be, for both authors and readers. Some options:
Commenting with a list of typos: The current version. Requires making a list while reading, then putting it in a comment; other users might suggest duplicate typos; meta comments like typos detract from other comments; plus they don’t get visibly deprecated once addressed by the author; etc.
Typo comments (or suggested edits) à la Google Docs or this new LW feature: Typo suggestions include the location of the typo; other users who want to suggest the typo see that it’s already been noticed and don’t duplicate it; this meta stuff is clearly separated from normal LW comments; etc. Typo suggestions still don’t get visibly deprecated once addressed by the author, unless the author can delete comments.
Suggesting changes in a version control system like Git: While forking on Github has tons of overhead, the basic workflow is quite simple: users suggest typo edits to the document, and then the author can confirm or reject them with one button. However, if typo suggestions are associated with users, this might have some weird implications wrt licensing and authorship. (IIRC some entertainment businesses like Wizards of the Coast don’t accept user suggestions per company policy, lest the suggesters later claim that their suggestion was implemented without compensation.)