curseknight / phurl

Automatically exported from code.google.com/p/phurl
0 stars 0 forks source link

ABUSE of PHURL by spammers (like the PARTNERKA spam gang, "Canadian Pharmacy"etc) - No way to advise "provider" of this. #74

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Any
2.
3.

What is the expected output? What do you see instead?
Lack of a way to report abuse of PHURL created URLS by spammers.

What version of the product are you using? On what operating system?
Seen on almost all similar type Open Source URL shorteners

Please provide any additional information below.

*ALL* URL shorteners *WILL* be abused by spammers, it's just a matter of time 
before they find them. 

spammers *WILL* abuse ANY URL shortening service they can find. 

PHURL, as with almost all similar type Open Source URL shorteners, has no 
built-in system to notify the administrator of this. 

Please consider doing something towards this. I'm no coder, but I can think of 
two possible systems (offer both as options?).

Both require a "report abuse" link...
It should contain:
a) Created URL
b) Redirected URL (total end-result if multiple redirectors used)
c) Reason (scroll menu?)
d) Optional contact email for complainant 

OK
1) auto-send a report to an admin email account on each report.
This is OK if the admin ACTIVELY supports their site. Unfortunately, many 
DON'T! 

BETTER (for lazy and/or clues-deprived admins)
2) stack reports of an abused "created" URL up until a (selectable) threshold 
is reached, then auto-suspend it for review... but still send a notification 
email. It should also provide an "immediate override", but require a valid 
email address to do so. (Sending a "Confirm This Action" email to that address 
with a "click to verify" token link and a summary of the complaint, then 
suspending the "created URL" on the link-click seems to be a good idea here..)

Thanks...
Keith Christensen
inbox.fulla.crap@gmail.com

Original issue reported on code.google.com by inbox.fu...@gmail.com on 1 Aug 2010 at 6:58

GoogleCodeExporter commented 9 years ago
Link to this page is at http://sa.feurl.com/PHURLabusereporting
(and that's where this started; with http://sa.feurl.com/x/

Original comment by inbox.fu...@gmail.com on 1 Aug 2010 at 7:24

GoogleCodeExporter commented 9 years ago
Also, we could check the urls against a database of 'bad' urls. We will look 
into something like this into the next major release.

Original comment by jordan%i...@gtempaccount.com on 15 Aug 2010 at 6:59

GoogleCodeExporter commented 9 years ago
This is a planned feature for a future version. As of yet, we have no idea 
which stage we will implement this at. We will probably have a spam url 
database, which will have a good few default entries pulled from an existing 
database. People can then submit spam URLs from the phurl admin panel, where 
they will be sent to a queue for the phurl developers, who will review and add 
them to the database.

Original comment by hcblahb...@gmail.com on 6 Sep 2010 at 1:14

GoogleCodeExporter commented 9 years ago
We only plan on using PHurl for our own purposes and disallow others from 
creating new links.  We added an Auth code field to the form to prevent 
unauthorized creation of new shortened links.

Realize that most won't want to do this, but it was our way of generating short 
urls using our site's domain, allowing them to be used, but restricting who can 
create new links.  ie... not spammers.

Original comment by tnet.ser...@gmail.com on 20 Sep 2010 at 9:45

GoogleCodeExporter commented 9 years ago
This has been added to the "Future Features" Wiki page.

Original comment by hcblahb...@gmail.com on 27 Oct 2010 at 11:08

GoogleCodeExporter commented 9 years ago
I have added google's recaptcha

Register your website here: http://www.google.com/recaptcha/whyrecaptcha
extract these files and override them, then edit index.php to include your 
private and public key

http://www.multiupload.com/TU1M8HBU4J

Original comment by itspa...@gmail.com on 21 May 2011 at 4:25

Attachments: