[
https://issues.apache.org/jira/browse/ROL-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756568#comment-13756568
]
Glen Mazza commented on ROL-833:
--------------------------------
I don't like this idea, about sending data to the server before the "Save as
Draft" or "Post to Weblog" buttons are pushed. It will be jarring and
unpleasant to many users to see their privacy violated in such a manner.
People might include sensitive or overly candid information that they plan on
removing prior to pressing "Save as Draft", with this feature, everything will
still be sent to the server (over non-secured wire no less) regardless. GMail
can ethically do autosave because you agree to their Privacy Policy and Terms
of Use before signing up for GMail account, plus AFAICT it always uses SSL to
protect inadvertent transfers from outside snoopers, neither is the case with
Roller.
When a user hits "Save as Draft" or "Post to Weblog", he is indicating not just
a desire to save his work in case he should lose it (the target audience of
ROL-833), but rather, he's making a statement that the information he has
written is now ready and safe to be transferred over the wire to the server for
storage, any copy-and-pasted SSN's or sensitive data, for example, has been
removed. So if anything inappropriate gets sent it's the blogger's fault and
not Roller's. For safety for all concerned, Roller needs that latter statement
prior to sending anything to its server.
Other options, as stated in the Matt's weblog, that of using browser plugins to
save what a person types, using an external client, or (as I do) just hitting
the "Save as Draft" at convenient times works perfectly well.
Whom you would be pleasing with this switch, a newbie blog owner who writes
umpteen paragraphs before bothering to hit the "Save as Draft" button and one
whose browser crashes frequently causing him to lose data, would come at a much
higher cost from discerning users about seeing their information sent to the
server without their approval first. Besides, a blog owner still will need to
save his work locally to guard against Roller database crashes, as there's no
guarantee the DB is being backed up properly or is otherwise recoverable.
[I don't even like Gmail's autosave, finding it too Big Brotherish. Sometimes
if I'm unpleased about something I start off quite frank in an email but then
clean it up prior to hitting the send key. What gmail does is collect our
intermediate (i.e., candid) thoughts and send them to Google Corporation for
their knowledge, thoughts which are increasingly subject to collection by the
U.S. Federal Government.]
> Add auto-save feature like Gmail has
> ------------------------------------
>
> Key: ROL-833
> URL: https://issues.apache.org/jira/browse/ROL-833
> Project: Roller
> Issue Type: Improvement
> Components: Web Services
> Affects Versions: 1.2
> Reporter: Matt Raible
> Assignee: Roller Unassigned
>
> http://raibledesigns.com/page/rd?entry=gmail_s_new_auto_save
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
