E-mail confirmation to be necessary for the creation of usernames #59

Open
opened 2015-04-04 16:12:22 +00:00 by GoogleCodeExporter · 10 comments
GoogleCodeExporter commented 2015-04-04 16:12:22 +00:00 (Migrated from github.com)
Now that it isn't checked if the e-mail-address entered when creating a new
username is really used by the prospective user, spammers and trolls have a
walk-over. Over at blogger.de, once in a while botnets are used to create
hundreds of usernames and blogs in an hour, forcing the administrators to
shut down the creation of new users and delete hundreds of sites. (A few
months ago, 6000 blogs have been created within a few hours.)

I suggest sending an e-mail with a confirmation link plus -code to the
address entered and - in case the username isn't "activated" within time,
deleting the usernames not activated the next day automatically. 

Additionally, a blacklist featuring services like mailinator.com and the
domain names/email addresses of unwanted spammers, seos and the like,
editable from within the sysadmin interface, would be highly desirable. 

By the way, people nowadays are so used to receiving confirmation mails
they think something went wrong when they receive no mail, I got a few
complaints about that... and who knows, maybe that's the reason for the
mysteriously huge amount of usernames created and never used? ;-)

Original issue reported on code.google.com by kinomu.w...@gmail.com on 17 Nov 2009 at 3:08

``` Now that it isn't checked if the e-mail-address entered when creating a new username is really used by the prospective user, spammers and trolls have a walk-over. Over at blogger.de, once in a while botnets are used to create hundreds of usernames and blogs in an hour, forcing the administrators to shut down the creation of new users and delete hundreds of sites. (A few months ago, 6000 blogs have been created within a few hours.) I suggest sending an e-mail with a confirmation link plus -code to the address entered and - in case the username isn't "activated" within time, deleting the usernames not activated the next day automatically. Additionally, a blacklist featuring services like mailinator.com and the domain names/email addresses of unwanted spammers, seos and the like, editable from within the sysadmin interface, would be highly desirable. By the way, people nowadays are so used to receiving confirmation mails they think something went wrong when they receive no mail, I got a few complaints about that... and who knows, maybe that's the reason for the mysteriously huge amount of usernames created and never used? ;-) ``` Original issue reported on code.google.com by `kinomu.w...@gmail.com` on 17 Nov 2009 at 3:08
GoogleCodeExporter commented 2015-04-04 16:12:23 +00:00 (Migrated from github.com)
[deleted comment]
``` [deleted comment] ```
GoogleCodeExporter commented 2015-04-04 16:12:23 +00:00 (Migrated from github.com)
[deleted comment]
``` [deleted comment] ```
GoogleCodeExporter commented 2015-04-04 16:12:23 +00:00 (Migrated from github.com)
The confirmation mail should be sent just because many people indeed are 
waiting for 
it!

For the mass generation of user accounts and/or comments I am waiting for the 
potential solution mentioned by kris in this thread: 
http://tobi.antville.org/stories/1959191/#1959280

Original comment by interf...@p3k.org on 18 Jan 2010 at 11:23

``` The confirmation mail should be sent just because many people indeed are waiting for it! For the mass generation of user accounts and/or comments I am waiting for the potential solution mentioned by kris in this thread: http://tobi.antville.org/stories/1959191/#1959280 ``` Original comment by `interf...@p3k.org` on 18 Jan 2010 at 11:23
GoogleCodeExporter commented 2015-04-04 16:12:23 +00:00 (Migrated from github.com)
Do you mean just sending a mail like "Congrats foo, everything went fine, have 
a lot
of fun at antville.org" without any effect on the creation of the username? 
Sure, a
lot of people would love to receive a mail like that, but I wonder how Kris' 
solution
could compensate the effect the described feature should have. 

Original comment by kinomu.w...@gmail.com on 18 Jan 2010 at 8:13

``` Do you mean just sending a mail like "Congrats foo, everything went fine, have a lot of fun at antville.org" without any effect on the creation of the username? Sure, a lot of people would love to receive a mail like that, but I wonder how Kris' solution could compensate the effect the described feature should have. ``` Original comment by `kinomu.w...@gmail.com` on 18 Jan 2010 at 8:13
GoogleCodeExporter commented 2015-04-04 16:12:23 +00:00 (Migrated from github.com)
I cannot tell if any of the measures will solve or significantly reduce the 
spam problem.

But I rather would try everything else than get rid of that very charming and 
easy 
register-and-go! feature we have in Antville...

Original comment by interf...@p3k.org on 19 Jan 2010 at 1:16

``` I cannot tell if any of the measures will solve or significantly reduce the spam problem. But I rather would try everything else than get rid of that very charming and easy register-and-go! feature we have in Antville... ``` Original comment by `interf...@p3k.org` on 19 Jan 2010 at 1:16
GoogleCodeExporter commented 2015-04-04 16:12:23 +00:00 (Migrated from github.com)
Postponed to 1.3.

Original comment by interf...@p3k.org on 23 Apr 2010 at 8:10

  • Added labels: Milestone-Release-1.3
  • Removed labels: Milestone-Release-1.2
``` Postponed to 1.3. ``` Original comment by `interf...@p3k.org` on 23 Apr 2010 at 8:10 - Added labels: **Milestone-Release-1.3** - Removed labels: **Milestone-Release-1.2**
GoogleCodeExporter commented 2015-04-04 16:12:24 +00:00 (Migrated from github.com)

Original comment by kinomu.w...@gmail.com on 23 Feb 2011 at 6:39

  • Added labels: Priority-Low
  • Removed labels: Priority-Critical
Original comment by `kinomu.w...@gmail.com` on 23 Feb 2011 at 6:39 - Added labels: **Priority-Low** - Removed labels: **Priority-Critical**
GoogleCodeExporter commented 2015-04-04 16:12:24 +00:00 (Migrated from github.com)

Original comment by interf...@p3k.org on 29 May 2011 at 9:08

  • Added labels: Milestone-Release-1.4
Original comment by `interf...@p3k.org` on 29 May 2011 at 9:08 - Added labels: **Milestone-Release-1.4**
GoogleCodeExporter commented 2015-04-04 16:12:24 +00:00 (Migrated from github.com)

Original comment by m...@tobischaefer.com on 28 Jul 2013 at 8:50

  • Added labels: Milestone-Release-1.5
  • Removed labels: Milestone-Release-1.4
Original comment by `m...@tobischaefer.com` on 28 Jul 2013 at 8:50 - Added labels: **Milestone-Release-1.5** - Removed labels: **Milestone-Release-1.4**
github-actions[bot] commented 2021-05-17 02:38:41 +00:00 (Migrated from github.com)

Stale issue message

Stale issue message
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: antville/antville#59
No description provided.