Dat private/public link types

[max-mapper]

Would it be useful to have a distinction between public and private links encoded in dat.land/dat URLs in general?

E.g. right now lets say we run a download stats crawler that connects to all dat swarms of publicly listed dats on dat.land, and monitors # of peers, download volumes etc. If the urls had e.g. /secret or /private somewhere in them, the crawler could ignore them.

It isn't so much an issue for our official crawler, where we will only crawl publicly listed dats from a single place, but I'm thinking more to limit damage of a dat link that accidentally gets shared somewhere that wasn't supposed to be shared. This also kinda reminds me of robots.txt, maybe we can just use one of those checked into the repo?

[juliangruber]

I would like to throw in having { "private": true } inside dat.json, similar to robots.txt

[juliangruber]

Do you think "private" should mean it's simply unlisted, like an unlisted youtube video, or should it be like with git where you need to be signed in to see it in the UI and need to sign in with your CLI?

[okdistribute]

It might be helpful to engage in a short exercise where we describe how the user would engage, in what scenario:

For example,

1. user creates a dat. It's by default private. User sends link to friend. User grants friend write access. Can friend make it public?
2. User creates private dat. Shares link w friend. User changes dat to public. Is the old link still valid?
3. User creates private dat. Adds title description and author to dat.json. Makes it public. Does it show up immediately on dat.land?
4. User creates private dat. Is logged in the desktop app and web ui. Does it show up in the web ui?