from <a href="/en/Nodal%20Point%20of%20Thought%202021-05-06">Nodal Point of Thought 2021-05-06</a>
public to private transfer
As for the public/private divide, my old self pointed out that it&#39;s a false dichotomy, and I&#39;d like to think about it some more.
 - <a href="/en/private%2Fpublic%20division">private/public division</a>
<ul>
<li>Private to public transfers can be done.
 - <a href="/en/Try%20%E2%9C%85scrapbox-Duplicator">Try ✅scrapbox-Duplicator</a></li>
<li><img src='https://scrapbox.io/api/pages/nishio-en/nisbot/icon' alt='nisbot.icon' height="19.5"/> <a href="/en/About%20Scrapbox%20private%20to%20public%20transfer">About Scrapbox private to public transfer</a><ul>
<li>The private to public transfer doesn&#39;t meet my needs.</li>
</ul>
</li>
<li>Made: <a href="/en/Finding%20links%20between%20multiple%20projects">Finding links between multiple projects</a>.<ul>
<li>This one doesn&#39;t really fit our needs either.</li>
</ul>
</li>
<li>What is wrong? How can I fit my needs?<ul>
<li><a href="/en/How%20to%20resolve%20the%20%22private%2Fpublic%20divide%22%20to%20suit%20your%20needs">How to resolve the &quot;private/public divide&quot; to suit your needs</a></li>
</ul>
</li>
<li>It seems like a good idea to overwrite the transfer from public to private, not update the public page in the private project, and provide an easy way to create a key page.<ul>
<li><a href="/en/to%F0%9F%94%92">to🔒</a></li>
</ul>
</li>
</ul>
<hr>
This page is auto-translated from <a href="https://scrapbox.io/nishio/public%E2%86%92private%E8%BB%A2%E9%80%81">/nishio/public→private転送</a> 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 <a href="https://twitter.com/nishio_en">@nishio_en</a>. I&#39;m very happy to spread my thought to non-Japanese readers.