Tantek Çelik<p>✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.<br><br>The consumer Infinite Scroll Web leaves us feeling empty.<br><br>Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.<br><br>A week ago when we wrapped up <a class="" href="https://indieweb.social/tags/IndieWebCamp" rel="nofollow noopener" target="_blank">#<span class="p-category">IndieWebCamp</span></a> Portland and I was reading Kevin Marks (<a class="" href="https://indieweb.social/@kevinmarks" rel="nofollow noopener" target="_blank">@kevinmarks@indieweb.social</a>) live-tooting of the demos<a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-1" rel="nofollow noopener" target="_blank">¹</a>, I noticed a few errors, typos or miscaptures, and pointed them out in-person.<br><br>Kevin was able to quickly edit his toots and update them for anyone reading, thanks to <a class="" href="https://indieweb.social/tags/Mastodon" rel="nofollow noopener" target="_blank">#<span class="p-category">Mastodon</span></a>’s post editing feature and its support of <a class="" href="https://indieweb.social/tags/ActivityPub" rel="nofollow noopener" target="_blank">#<span class="p-category">ActivityPub</span></a> Updates. But this shouldn’t require being in the same room, whether IRL or chat.<br><br>We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.<br><br>13 years ago I wrote<a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-2" rel="nofollow noopener" target="_blank">²</a>:<br><br>&nbsp;“The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”<br><br>Now I want the Read Write Suggest-Edit Accept-Edit Update Web.<br><br>The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).<br><br>Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.<br><br>If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.<br><br>Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?<br><br>To enable such UIs and interactions across servers and implementations, we may need a new type of response<a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-3" rel="nofollow noopener" target="_blank">³</a>, perhaps with a special property (or more) to convey the edits being suggested.<br><br>There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the <a class="" href="https://indieweb.social/tags/IndieWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">IndieWeb</span></a> wiki:<br>* <a class="" href="https://indieweb.org/edit" rel="nofollow noopener" target="_blank">https://indieweb.org/edit</a><br><br>Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.<br><br>For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:<br><br>✏️ Suggest Edit<br><br>and link it to an edit URL for the static file for the post.<br><br>I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:<br><br><a class="" href="https://tantek.com/github/cassis/edit/main/README.md" rel="nofollow noopener" target="_blank">https://tantek.com/github/cassis/edit/main/README.md</a><br><br>This will start the process of creating a “pull request”, GitHub’s jargon<a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-4" rel="nofollow noopener" target="_blank">⁴</a> for a “suggested edit”.<br><br>After completing GitHub’s ceremony of entering multiple text fields (summary &amp; description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash &amp; Merge”, “Delete fork”, etc. to accept the edit.<br><br>It’s an awkward interaction<a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-5" rel="nofollow noopener" target="_blank">⁵</a>, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.<br><br>We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.<br><br><a class="" href="https://indieweb.social/tags/readWriteWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">readWriteWeb</span></a> <a class="" href="https://indieweb.social/tags/editableWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">editableWeb</span></a> <a class="" href="https://indieweb.social/tags/suggestEdit" rel="nofollow noopener" target="_blank">#<span class="p-category">suggestEdit</span></a> <a class="" href="https://indieweb.social/tags/acceptEdit" rel="nofollow noopener" target="_blank">#<span class="p-category">acceptEdit</span></a><br><br>References:<br><br><a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-1" rel="nofollow noopener" target="_blank">¹</a> <a class="" href="https://indieweb.social/@kevinmarks/113025295600067213" rel="nofollow noopener" target="_blank">https://indieweb.social/@kevinmarks/113025295600067213</a><br><a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-2" rel="nofollow noopener" target="_blank">²</a> <a class="" href="https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11" rel="nofollow noopener" target="_blank">https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11</a><br><a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-3" rel="nofollow noopener" target="_blank">³</a> <a class="" href="https://indieweb.org/responses" rel="nofollow noopener" target="_blank">https://indieweb.org/responses</a><br><a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-4" rel="nofollow noopener" target="_blank">⁴</a> The phrase “pull request” was derived from the git command: “git request-pull” according to <a class="" href="https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/" rel="nofollow noopener" target="_blank">https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/</a><br><a href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-5" rel="nofollow noopener" target="_blank">⁵</a> “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.<br><br>This is post 20 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">100PostsOfIndieWeb</span></a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener" target="_blank">#<span class="p-category">100Posts</span></a><br><br>← <a class="" href="https://tantek.com/2024/242/t1/indiewebcamp-portland" rel="nofollow noopener" target="_blank">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br>→ <a class="" href="https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed" rel="nofollow noopener" target="_blank">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a></p>