private/public division
https://gyazo.com/dddfcdd9d1c94ddc9aa1f28acac3bc85
When doing the Writing Method, instruct students to write down anything that comes to mind without thinking about whether or not it is appropriate to publish such a thing. https://gyazo.com/33f535d056d023797f70e7adf4e06906
However, in services where information is separated by public/private, this is disconnected.
It is inevitable that "non-language" cannot be put on the service, but the public/private split is a design problem that can be solved.
Shouldn't everything that is output go into the "personal/private" space by default?
This solves the problem of "[🌀Where should I write?
Attribution of information "to publish or not to publish" should be decided after the fact.
Even if it's published after the fact, it's not moving to another space.
All together subject to search
In other words, not "private group/public group" # False dichotomy
A default private group that includes everything and a select group of publicly available items, the former encompassing the latter.
I was thinking about the design of Regroup. ---
This page is auto-translated from /nishio/private/publicåˆ†æ– 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.