Protecting content in an open grid
Discussion on the mailing list
Unfortunately the archive messed up and the permission thread is all over the place, but here are some link from which you might want to follow downwards the stream: (probably also happens due to keyword juggling in the subject)
- https://lists.secondlife.com/pipermail/sldev/2007-September/004637.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/004652.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/005065.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/005086.html
- https://lists.secondlife.com/pipermail/sldev/2007-September/005104.html (a content creator's view)
- https://lists.secondlife.com/pipermail/sldev/2007-September/005128.html (cont'd)
- https://lists.secondlife.com/pipermail/sldev/2007-September/005144.html (cont'd)
Basically it's the September archive.
Summary
- I think all participants are more or less agreeing on the fact that a strong(er) DRM is not possible to be implemented
- Permissions are here to stay, but current access lists can hold only within the walls of specific managed grids
- New permissions might be needed such as
- allow an asset only to be used inside one region domain
- allow an asset only to be used inside one grid (= list of trusted region domains)
- allow an asset only to be used inside a set of region domains
- For example, using signed certificates and revocation lists (possible implementation)
- It should also possible to create full-perm assets that stay full perm (such as a GPL-style license).
- It should be possible to make your intent more clear.
- Additional specific flags indicating certain permissions, even if they can't be enforced to serve as notice.
- An additional license field for license and copyright text, similar to land covenants (for e.g. CC licenses)