hi,
I was updating the description of one of my extensions ,
and I was a bit annoyed by the new requirement to give my mail.
I have three remarks:
1) why type after all the email for each extension ? as soon as I register an account, the extension website already have my mail isn't it ?
Added to that , why retype the same mail for each extension ?
2) hey , I'm providing giving away an extension for free. Does it mean I must "give away" my time too for "free support" ?
I've already spent enough time for developing the extension, and although I would not necessarily refuse to help if someone is experimenting a problem with the extension , I give no warranty for this.
3) my mail is outputted "as is" in the extension website. Please protect me from spambots ! Instead of a direct mail link,
there should be the option for a contact form or at least the mail should be "obfuscated" and revealed by javascript only.
Even joomla have a mambot to protect mails from spambots, so please take care of this.
cheers
annoying email requirement , 3 remarks
Moderators: tydust, LorenzoG, timothy.stiffler
-
ot2sen
- Joomla! Ace
- Posts: 1384
- Joined: Thu Aug 18, 2005 9:58 am
- Location: Hillerød - Denmark
- Contact:
Re: annoying email requirement , 3 remarks
Hi mehdi,
Yes, 'developer mail' is one of the required fields, as well as 'developer homepage' and 'download URL'.
1. Could be automatic, but by letting developers enter their preferred email contact for each extension you give them an option to choose another mail than the one used for thier JED account.
2. No
3. The joomla mambot is in use already.
Yes, 'developer mail' is one of the required fields, as well as 'developer homepage' and 'download URL'.
1. Could be automatic, but by letting developers enter their preferred email contact for each extension you give them an option to choose another mail than the one used for thier JED account.
2. No
3. The joomla mambot is in use already.
Re: annoying email requirement , 3 remarks
hi ot2sen,
I realize that the protection offered by joomla mambot might be ineffective.
Yes , you have to enable javascript in order to see the mail in your browser,
but the fact is the mail is fully outputed in the page source, and I really doubt that spambots see
pages, as the browsers. My assumption is that they parse the full page code , looking for a pattern that looks like an email.
In this case , the protection offered is really ineffective.
I would have expected a minimal obfuscation of the mail address.
I hope, I'll won't observe a unexpected augmentation of spam in my mail box.
If things go wrong, I'll change the mail ... A mail box I almost not visit.
I realize that the protection offered by joomla mambot might be ineffective.
Yes , you have to enable javascript in order to see the mail in your browser,
but the fact is the mail is fully outputed in the page source, and I really doubt that spambots see
pages, as the browsers. My assumption is that they parse the full page code , looking for a pattern that looks like an email.
In this case , the protection offered is really ineffective.
I would have expected a minimal obfuscation of the mail address.
I hope, I'll won't observe a unexpected augmentation of spam in my mail box.
If things go wrong, I'll change the mail ... A mail box I almost not visit.
