OpenWetWare:Software/Private Pages: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
There seem to be 2 major methods of implementation: | There seem to be 2 major methods of implementation: | ||
# Groups + access control (rumors MediaWiki may be working on this). | # Groups + access control (rumors MediaWiki may be working on this). | ||
# Encryption. [[User:Austin|I]] have implemented an extension which does this. It's available [ http://dev.openwetware.org/wiki/Encryption_Test here] on the dev dot openwetware site for anyone who wants to play around with it. | # Encryption. [[User:Austin|I]] have implemented an extension which does this. It's available [http://dev.openwetware.org/wiki/Encryption_Test here] on the dev dot openwetware site for anyone who wants to play around with it. | ||
Discussion Questions: | Discussion Questions: | ||
Revision as of 14:16, 20 April 2006
There have been requests and questions about having content on OWW that is not public, not indexed by Google, not editable by everyone on OWW, etc. This page aims to discuss this policy.
There seem to be 2 major methods of implementation:
- Groups + access control (rumors MediaWiki may be working on this).
- Encryption. I have implemented an extension which does this. It's available here on the dev dot openwetware site for anyone who wants to play around with it.
Discussion Questions:
- Is it in OWW's "open" or "wiki" nature to have pages that are private in any form?
- Sri Kosuri 17:15, 20 April 2006 (EDT): I think that this could be a useful excercize. I think one of the problems is that once people start using it, there is no turning back... we have to continue to support it.
- What's the "right" way to do encryption?
- Austin 16:38, 20 April 2006 (EDT): The current implementation allows users to put <encrypt> tags around any text they wish to encrypt. Keys are stored via users' preferences. Text is automatically encrypted/decrypted on views/edits if a proper key is found. File uploads (images) are not encrypted. This could be another issue.
- Sri Kosuri 17:15, 20 April 2006 (EDT):Can you store multiple keys?
- Austin 16:38, 20 April 2006 (EDT): The current implementation allows users to put <encrypt> tags around any text they wish to encrypt. Keys are stored via users' preferences. Text is automatically encrypted/decrypted on views/edits if a proper key is found. File uploads (images) are not encrypted. This could be another issue.
- How would people likely use such features? Would the majority of their content be public or not?
- Austin 16:38, 20 April 2006 (EDT): My belief is that anything to get people on to OWW is good even if some of the content is private.
- Sri Kosuri 17:15, 20 April 2006 (EDT): I think if we use the encryption extension that Austin made, most of the content will remain open, if only it is much more cumbersome to close it. I am probably for this option.
- Encryption vs. Access control
- Encryption can provide greater comfort of security (even administrators may not be able to access page content)
- Encryption doesn't technically provide more than what users can do currently (i.e. in theory, anyone can put any encrypted text on a page, it's just not particularly easy).
- Encryption does not provide anything other than secrecy (i.e. cannot control someone else from messing up with your page, even if that someone else has no idea what they are messing with).
