{"action":"created","issue":{"url":"https://api.github.com/repos/solid/solid-spec/issues/129","repository_url":"https://api.github.com/repos/solid/solid-spec","labels_url":"https://api.github.com/repos/solid/solid-spec/issues/129/labels{/name}","comments_url":"https://api.github.com/repos/solid/solid-spec/issues/129/comments","events_url":"https://api.github.com/repos/solid/solid-spec/issues/129/events","html_url":"https://github.com/solid/solid-spec/issues/129","id":385226946,"node_id":"MDU6SXNzdWUzODUyMjY5NDY=","number":129,"title":"Is /public really such a good idea?","user":{"login":"JornWildt","id":274072,"node_id":"MDQ6VXNlcjI3NDA3Mg==","avatar_url":"https://avatars1.githubusercontent.com/u/274072?v=4","gravatar_id":"","url":"https://api.github.com/users/JornWildt","html_url":"https://github.com/JornWildt","followers_url":"https://api.github.com/users/JornWildt/followers","following_url":"https://api.github.com/users/JornWildt/following{/other_user}","gists_url":"https://api.github.com/users/JornWildt/gists{/gist_id}","starred_url":"https://api.github.com/users/JornWildt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JornWildt/subscriptions","organizations_url":"https://api.github.com/users/JornWildt/orgs","repos_url":"https://api.github.com/users/JornWildt/repos","events_url":"https://api.github.com/users/JornWildt/events{/privacy}","received_events_url":"https://api.github.com/users/JornWildt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2018-11-28T11:37:06Z","updated_at":"2018-11-28T15:55:24Z","closed_at":null,"author_association":"NONE","body":"This is a spin-off from #127 where we touched upon the `/public` folder. That discussion has lead me to think that having a default `/public` folder is misleading.\r\n\r\nTake for instance my hypothetical photo collection in my POD - some of those photos are public, some are not, and some photos become public after a while, while others might get hidden at a later time.\r\n\r\nStoring my photos under `/public` indicates that they are, well, public. Does that mean I should move them from the public container once I want to hide them? That would imply that my photos need to change URL every now and then I choose to change their visibility.\r\n\r\nYou can repeat the same argument for all sorts of thing - leading to the conclusion that you should not provide a default `/public` container for PODs since an \"implementation detail\" like access should not be reflected in the URL.\r\n\r\nFeel free to close this issue immediately if I am completely off track ..."},"comment":{"url":"https://api.github.com/repos/solid/solid-spec/issues/comments/442498153","html_url":"https://github.com/solid/solid-spec/issues/129#issuecomment-442498153","issue_url":"https://api.github.com/repos/solid/solid-spec/issues/129","id":442498153,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjQ5ODE1Mw==","user":{"login":"melvincarvalho","id":65864,"node_id":"MDQ6VXNlcjY1ODY0","avatar_url":"https://avatars2.githubusercontent.com/u/65864?v=4","gravatar_id":"","url":"https://api.github.com/users/melvincarvalho","html_url":"https://github.com/melvincarvalho","followers_url":"https://api.github.com/users/melvincarvalho/followers","following_url":"https://api.github.com/users/melvincarvalho/following{/other_user}","gists_url":"https://api.github.com/users/melvincarvalho/gists{/gist_id}","starred_url":"https://api.github.com/users/melvincarvalho/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/melvincarvalho/subscriptions","organizations_url":"https://api.github.com/users/melvincarvalho/orgs","repos_url":"https://api.github.com/users/melvincarvalho/repos","events_url":"https://api.github.com/users/melvincarvalho/events{/privacy}","received_events_url":"https://api.github.com/users/melvincarvalho/received_events","type":"User","site_admin":false},"created_at":"2018-11-28T15:55:24Z","updated_at":"2018-11-28T15:55:24Z","author_association":"CONTRIBUTOR","body":"I think the language can be changed a bit.\r\n\r\nSo firstly it says recommendation, meaning it's optional, not required.  That's good.  However w3c specs are also RECs, so that's quite strong in terminology.\r\n\r\nWhat is needed is a minimalist Solid web server spec that you can, say, just point as a file system.  There are many web servers out that you can just do.  What it will do is serve files, respect headers, respect .acls, allow globbing and allow the web servers.  All the core stuff.  \r\n\r\nThen we need a spec for those solid servers that will also be a webid provider, and provide space, with default folders -- ie account creation.  That can be a modular spec that is an optional extra.\r\n\r\nYou can have a spec as a social and app provider with default folders and the like.  Sort of like an Ubuntu type layer on top of the bare core.\r\n\r\nThen finally you can have a spec that will be an identity provider too.\r\n\r\nBut having a core solid spec that is minimal and people can implement as a hobby project is a nice way to go.  I worry that the spec itself gets gamed, but if we have a core solid spec that adheres to the read write principles that we worked out over 10 years, we can put more optional stuff in extra spec, and that will keep it as relatively pure hopefully for a long time.\r\n\r\n"}}
{"actor":{"display_login":"melvincarvalho"}}