putting a moratorium on changes

How Regroup works now.

• If you don’t know the URL, you can’t view it.
  • →Knowing the URL for browsing = having browsing privileges
• Issue a separate URL for editing
  • →Knowing the URL for editing = having the authority to edit

This is the same mechanism as Google Docs etc. It’s also a need that people who start using Scrapbox often mention.

• Example
  • Can’t you just show one page in the PRIVATE PROJECT to others?” →No, you can’t.
  • Can’t you just give someone else editing privileges on one page in a public project?” →No.
• I guess Scrapbox is a design philosophy that emphasizes linking within a project. As parallel work becomes more and more popular, it will become increasingly difficult to use a design in which access rights to all documents are tightly coupled with “whether you are a member of the project or not”.
• Example - Slack single channel guest - Guest space in kintone

Casual access rights control of “know the URL or not

• Not just “view” and “edit.”
• For example, what if there is an editing war with more than one person with editing privileges?
  • → In the case of Wikipedia, “protection” takes place
    • Wikipedia:Editorial battle - Wikipedia
    • Wikipedia:Protection request - Wikipedia

So I thought it would be nice to have the power to stop editing.

Low priority, at least not necessary until the emergence of a Regroup Map edited by multiple people. pRegroup2020

---

This page is auto-translated from /nishio/変更凍結 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.