#sandstorm

/

      • samba_ joined the channel
      • samba_ has quit
      • ecloud joined the channel
      • jadewang joined the channel
      • efishta joined the channel
      • jadewang has quit
      • KooBaa has quit
      • samba_ joined the channel
      • IRCFrEAK joined the channel
      • IRCFrEAK has left the channel
      • efishta has quit
      • jemc joined the channel
      • KooBaa joined the channel
      • KooBaa has quit
      • prettyvanilla_ joined the channel
      • madgoat joined the channel
      • madgoat has left the channel
      • neynah joined the channel
      • prettyvanilla_ joined the channel
      • jemc has quit
      • efishta joined the channel
      • jemc joined the channel
      • efishta has quit
      • Zertrin_ has quit
      • Zertrin_ joined the channel
      • neynah has quit
      • efishta joined the channel
      • samba_ has quit
      • KooBaa joined the channel
      • KooBaa has quit
      • ecloud joined the channel
      • ShalokShalom_ joined the channel
      • KooBaa joined the channel
      • KooBaa has quit
      • KooBaa joined the channel
      • foxmask has left the channel
      • FredFredFred joined the channel
      • FredFredFred_ has quit
      • FredFredFred_ joined the channel
      • FredFredFred has quit
      • tobald joined the channel
      • afuentes joined the channel
      • elensil joined the channel
      • efishta has quit
      • lounge-user84 joined the channel
      • lounge-user84 is now known as efishta
      • efishta
        I created a collection, added a couple of grains, created a VIEW ONLY link to the collection, and I'm finding that whoever has access to that link has editing rights to each grain. In other words, the "VIEW ONLY" limitation is for the collection, not the actual rights within the grains themselves. I'd expect rights to carry through.
      • kentonv
        efishta, yes, unfortunately, the collections app does not have any understanding of the permissions that apply to other apps, so the links within it give exactly the same permissions to everyone.
      • efishta
        I see. So the assumption is that collections are for a set group of trusted, EDIT RIGHTS users
      • kentonv
        one way we could maybe solve this is to let apps specify which permissions are appropriate in a "read-only" setting, for the specific purpose of the collections app (and similar) being able to restrict read-only viewers of the collection to those permissions on the contained grains
      • but it's weird because "read-only" doesn't necessarily make sense for all apps
      • efishta, no, if you are creating a collection that you intend to share in a context where you want the contents to be read-only, you can make sure to add each grain with read-only access
      • e.g. when you add an etherpad to a collection, you are asked if you want to grant the collection "editor", "commeter", or "viewer" access. That applies to everyone who gets access through the collection.
      • efishta
        that makes sense
      • kentonv
        the problem is this requires that you decide in advance whether the collection is mean for read-write collaboration or for read-only, and be sure to apply this decision uniformly for all grains you add, which is tedious
      • but that's where we are today
      • efishta
        I see. I wasn't thinking about the individual setting when you add the grain to a collection. That covers the functionality I thought was lacking when I asked the question initially.
      • Sure it'd be nice to have it automated, but this works well enough to be useful.
      • FredFredFred joined the channel
      • FredFredFred_ has quit
      • jason_nstar[m] has left the channel
      • FredFredFred_ joined the channel
      • FredFredFred has quit
      • ShalokShalom joined the channel
      • elensil has left the channel
      • elensil joined the channel
      • jemc has quit
      • ShalokShalom joined the channel
      • FredFredFred joined the channel
      • FredFredFred_ has quit
      • nwf has quit
      • leeola joined the channel
      • bodisiw joined the channel
      • elensil has quit
      • elensil joined the channel
      • tobald has quit
      • ecloud has quit
      • ecloud joined the channel
      • jemc joined the channel
      • networkfail joined the channel
      • networkfail
        hi. has anyone here experimented with running nextcloud on sandstorm?
      • nwf joined the channel
      • jemc has quit
      • jemc joined the channel
      • jemc has quit
      • jemc joined the channel
      • liam has quit
      • efishta has quit
      • chilts has quit
      • liam joined the channel
      • chilts joined the channel
      • mrdomino_ is now known as mrdomino
      • jemc has quit
      • elensil has left the channel
      • mrdomino
        kentonv: so, new capnproto release with the openbsd fixes? :-p
      • strugee
        hey kentonv, any other former company folks in this channel:
      • I'm curious how you guys handled copyright assignment internally in the company? i.e. did the company own copyright of code written by employees or did they retain copyright?
      • if you're free to talk about it obviously :)
      • mrdomino has quit
      • mrdomino joined the channel
      • Telesight joined the channel
      • mrdomino has quit
      • mrdomino joined the channel
      • ShalokShalom_ joined the channel
      • networkfail has left the channel
      • jemc joined the channel
      • Isla_de_Muerte joined the channel
      • efishta joined the channel
      • efishta has quit
      • KooBaa has quit
      • efishta joined the channel
      • Telesight has quit
      • efishta has quit