As someone else pointed out, the word "non-public" is used to distinguish from the existing data, where everything is public. I'm not the guy who wrote it, but if I had to guess why that language was chosen, it would be because there's a lot of emphasis on spaces being scalable up to millions of users (think paywalled Patreon content, or something similar), and private implies a much tighter restriction.
Set up a space with just you and your collaborators, put all your tangled data for a repo in it, do a little extra work on the knot implementation to actively authorize SSH connections (as that wasn't a concern when everything was public) and now that's a private repo.
Comments
Let's go, tangled.sh is about to have private repos
You sure about that? From my reading nothing about this is private.
As someone else pointed out, the word "non-public" is used to distinguish from the existing data, where everything is public. I'm not the guy who wrote it, but if I had to guess why that language was chosen, it would be because there's a lot of emphasis on spaces being scalable up to millions of users (think paywalled Patreon content, or something similar), and private implies a much tighter restriction. Set up a space with just you and your collaborators, put all your tangled data for a repo in it, do a little extra work on the knot implementation to actively authorize SSH connections (as that wasn't a concern when everything was public) and now that's a private repo.