Re: [translate-pootle] Privacy issues in Pootle: Profile page
Dwayne Bailey wrote: > I think we're making this way too complicated for an issue that I think > can be got around by the user themselves. If they want to work in > secret, register on Pootle as a secret user. If we're going to make assumptions about what users want, we should make those assumptions based on similar situations that a user might find himself in. I can't think of any system where registration is required, in which the registration details (especially the mail address) is shared willy-nilly with everyone else (except perhaps mailing lists). The usual expectation of a user would therefore be that his details are safe. I don't mind if Pootle works differently, but the user must know. And leaving it up to the user is actually what this suggestion will do -- it would be entirely up to the user to decide how and if he wants to be identified. The Pootle server needn't determine what kind of user the user is. All users have the same options. > I'm in favour of munging email addresses for people who fear spam. And > I think we can simply do that automatically without making many > confusing options. Munging only fools automated bots... it doesn't stop spam. I should know, because I have harvested e-mail addresses from PO files myself and I know how easy it is to build a highly targeted spam address list, munging or no munging. My original idea was quite complex, but my latest comment has much simplified it. Pootle doesn't have to do anything with the information yet, as long as it stores it. The idea is that the private and public display names are written to a text file (along with the user's name and/or username), where a server admin or project manager can access it. Samuel -- Samuel Murray [EMAIL PROTECTED] Decathlon, for volunteer opensource translations http://translate.sourceforge.net/wiki/decathlon/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Privacy issues in Pootle: Profile page
On Tue, 2008-09-16 at 10:39 +0200, Samuel Murray (Groenkloof) wrote: > G'day everyone > > I wish to address the following three issues from my previous mail: > > > The assumption is that the e-mail address a user uses for contact with > > Pootle will be the same e-mail address he wants to use for attribution > > in the PO file (assuming he is aware of the attribution). > > > What's more, many people munge their addresses in PO headers... > > > Another somewhat related problem I have, is that there is no mechanism > > for users to contact each other. > > Currently, the registration page and the profile page (options.html) > contain fields for the Name, Email, Password and Confirm password. I > propose that two extra fields be added to it: > > * Display Name (used for attribution purposes): > [] > > * Address where other users may contact me: > [] > > When a user registers, the above two fields are filled in automatically > (using JavaScript, I think) after the user has typed in his name and > e-mail address (although users can change/delete them). > > The autogenerated display name should contain the user's name and munged > mail address. So if his name is Joe Soap and his mail address is > [EMAIL PROTECTED], the autogenerated Display Name would be: > > Joe Soap > > The autogenerated name where a user wants to be contacted, should be the > same as his display name, but not munged (so that it can easily be > imported into a mail program): > > Joe Soap <[EMAIL PROTECTED]> > > Of course, the user can remove and/or change these entries if he wants > to, but by default they are entered, and if the user clicks "Register", > he automatically gives permission that the information be used as stated. > > I don't know what is the best way to store this information, but at > least the name/address where a user can be contacted should be stored in > a separate file that can easily be downloaded as-is by anyone with read > access to the server-side, so that project administrators can use the > information (eg to introduce translators to each other, or to send a > newsletter to translators). > > Your thoughts? I think we're making this way too complicated for an issue that I think can be got around by the user themselves. If they want to work in secret, register on Pootle as a secret user. I'm in favour of munging email addresses for people who fear spam. And I think we can simply do that automatically without making many confusing options. The last item of a list of email addresses, that should become simpler as we move to a database. I'd rather look at that after 1.2 but it can be done with a simple script that can read the users.prefs file if someone wants to give it a go. -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * The birth of the GNU generation http://www.translate.org.za/blogs/dwayne/en/content/birth-gnu-generation * Firefox users experience discrimination * RPM packages for py lib 0.9.2 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Privacy issues in Pootle: Profile page
Samuel Murray (Groenkloof) wrote: Currently, the registration page and the profile page (options.html) contain fields for the Name, Email, Password and Confirm password. I propose that two extra fields be added to it: * Display Name (used for attribution purposes): [] * Address where other users may contact me: [] When a user registers, the above two fields are filled in automatically (using JavaScript, I think) after the user has typed in his name and e-mail address (although users can change/delete them). I asked a question about this on comp.lang.javascript, and a kind user there wrote me the necessary script. I made come changes, and here it is (hopefully the attachment works). I don't know how to add this to Pootle's source code, though. Samuel -- Samuel Murray [EMAIL PROTECTED] Decathlon, for volunteer opensource translations http://translate.sourceforge.net/wiki/decathlon/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Privacy issues in Pootle: Profile page
G'day everyone I wish to address the following three issues from my previous mail: > The assumption is that the e-mail address a user uses for contact with > Pootle will be the same e-mail address he wants to use for attribution > in the PO file (assuming he is aware of the attribution). > What's more, many people munge their addresses in PO headers... > Another somewhat related problem I have, is that there is no mechanism > for users to contact each other. Currently, the registration page and the profile page (options.html) contain fields for the Name, Email, Password and Confirm password. I propose that two extra fields be added to it: * Display Name (used for attribution purposes): [] * Address where other users may contact me: [] When a user registers, the above two fields are filled in automatically (using JavaScript, I think) after the user has typed in his name and e-mail address (although users can change/delete them). The autogenerated display name should contain the user's name and munged mail address. So if his name is Joe Soap and his mail address is [EMAIL PROTECTED], the autogenerated Display Name would be: Joe Soap The autogenerated name where a user wants to be contacted, should be the same as his display name, but not munged (so that it can easily be imported into a mail program): Joe Soap <[EMAIL PROTECTED]> Of course, the user can remove and/or change these entries if he wants to, but by default they are entered, and if the user clicks "Register", he automatically gives permission that the information be used as stated. I don't know what is the best way to store this information, but at least the name/address where a user can be contacted should be stored in a separate file that can easily be downloaded as-is by anyone with read access to the server-side, so that project administrators can use the information (eg to introduce translators to each other, or to send a newsletter to translators). Your thoughts? Samuel -- Samuel Murray [EMAIL PROTECTED] Decathlon, for volunteer opensource translations http://translate.sourceforge.net/wiki/decathlon/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
