Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

I must agree here. Automated crash reports have kind of a bad
reputation, mainly because of Windows XP.
* you don't know what is being sent, and even when its listed you
can't be sure there's no personal data
* you don't know what is being done with the data
* there's nothing done about that, at least that's what I feel

* ask the user once at the beginning if he wants to report crashes and
list the information THERE
* NEVER include things like the current program's memory page dump or
something alike
* then DO NOT ask again but just send it

* pop-up which sais that a crash report can be sent if the user wishes, but:
* it only has a input field where the user can say for himself what
happened and when
* checkbox saying something like: "include relevant data", where
"data" really leads to ALL the data being sent

The current problem is that hardly anyone trusts these crash reports -
that's what I experience when talking to friends about that issue. So
we first have to make the user think that something is being done.
I've repeatedly used the "Firefox made me sad"-thing but I've never
used the crash report before.


I don't know about others, but I, for one, NEVER send those automated
crash reports. It feels a bit like big brother watching over my shoulder.

You are kidding right?

Unsubscribe instructions: Email to
Posting guidelines:
*** All posts to this list are publicly archived ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.