3 ms·
> Once again, it doesn't seem like a complete breakdown of security if your collaborators can view earlier versions of a document or a diagram within a document
by tomsaffell 18y ago
> Once again, it doesn't seem like a complete breakdown of security if your collaborators can view earlier versions of a document or a diagram within a document
I think the real issue is whether the systems operates as people expect it to. I would not have expected it to operate in the way described, and I suspect a lot of other people wouldn't either. There is a precedent here in tools like MS Office (ok, it isn't cloud based, but it is where some users are coming from as they adopt GDocs). If you told the average PowerPoint user that when they send a deck to their customer/partner that person will be able to see all the previous 'versions' of the document that you went through prior to giving it to them, then I think that PowerPoint user would be shocked, and worried.
I realize that cloud sharing and emailing aren't the same thing, and that GDoc's versioning system isn't the same as making changes and hitting save in PowerPoint from a technical point of view, but for the average user they probably feel like the same thing, so they will expect the same rules to apply. Bottom line: if it's going to operate like this then GDocs needs to make sure that users totally understand that.
- briansmith 18y agoI agree with you, except that good software conforms to the user's expectations, instead of forcing the user to conform to its limitations. If your application lets users restrict access to documents, it needs to restrict access to all parts of that document uniformly, regardless of how those parts are stored (embedded in the same file or spread out in multiple files).