Bitcoin Forum
October 21, 2018, 04:08:26 PM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: Unique way to cheat the forum- Paid bumping  (Read 382 times)
MagicSmoker
Full Member
***
Offline Offline

Activity: 322
Merit: 159



View Profile
June 22, 2018, 02:04:08 PM
 #21

That should merit a ban for the AAN OP no? Other company accounts too?
How do you know anyone related to the project is behind this?

You are right, this would make a great setup to damage your competition..

What if the ANN thread is self-moderated by the OP? If the OP is not actively pruning shitposts after, say, 24 hours, then it seems reasonable to conclude this is not a case of a competitor attempting to tar the competition.

EDIT - for example, here is a rather egregious violator: the Roomdao ANN thread.

This is a self-moderated thread that is seeing a new post every 2-3 minutes on average, and virtually none of those 3400+ posts is worth a crap. Thus, we can safely conclude that this is not a competitor trying to frame Roomdao for incentivizing posting to its ANN.

I get that nuking the thread absent any solid proof might still be seen as drastic, so how about temporarily locking it for, say, 7 days, or until the OP cleans up all the spammy posts? If the goal of paid bumping is to keep a thread on the first page then locking the thread, even temporarily, will ensure it falls far, far behind. I mean, just a 6 hour delay takes you back 5-6 pages!

1540138106
Hero Member
*
Offline Offline

Posts: 1540138106

View Profile Personal Message (Offline)

Ignore
1540138106
Reply with quote  #2

1540138106
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1540138106
Hero Member
*
Offline Offline

Posts: 1540138106

View Profile Personal Message (Offline)

Ignore
1540138106
Reply with quote  #2

1540138106
Report to moderator
1540138106
Hero Member
*
Offline Offline

Posts: 1540138106

View Profile Personal Message (Offline)

Ignore
1540138106
Reply with quote  #2

1540138106
Report to moderator
LoyceV
Legendary
*
Offline Offline

Activity: 1274
Merit: 2138


Self-made Legendary!


View Profile WWW
June 22, 2018, 06:38:21 PM
 #22

I get that nuking the thread absent any solid proof might still be seen as drastic, so how about temporarily locking it for, say, 7 days, or until the OP cleans up all the spammy posts?
Even if he deletes all the spam from bump bots, the goal is still accomplished: the thread stays on top thanks to the spam.

MagicSmoker
Full Member
***
Offline Offline

Activity: 322
Merit: 159



View Profile
June 22, 2018, 09:06:11 PM
 #23

I get that nuking the thread absent any solid proof might still be seen as drastic, so how about temporarily locking it for, say, 7 days, or until the OP cleans up all the spammy posts?
Even if he deletes all the spam from bump bots, the goal is still accomplished: the thread stays on top thanks to the spam.


Yes, I imagine the bump bots will continue posting even as the OP is deleting. I'm not really seeing any downsides to temporarily locking the thread, then. There has to be a smarter way of dealing with this rather than individually deleting posts or banning users (however much both may be deserved). I mean, a mod could literally spend all day on that Roomdao thread and only tread water, so to speak; the spammy shitposts begin on page 1 and continue, unrelenting, for the next 170+ pages...

shilova
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
June 24, 2018, 06:07:17 AM
 #24

A bigger problem with this issue is that now if no action is taken on this, it will encourage more spammers to use same techniques. There are enough excuses already given by members here to justify this.
LoyceV
Legendary
*
Offline Offline

Activity: 1274
Merit: 2138


Self-made Legendary!


View Profile WWW
June 24, 2018, 08:03:29 AM
 #25

I get that nuking the thread absent any solid proof might still be seen as drastic, so how about temporarily locking it for, say, 7 days, or until the OP cleans up all the spammy posts?
Even if he deletes all the spam from bump bots, the goal is still accomplished: the thread stays on top thanks to the spam.
A follow up after reading this:
We ask our community to leave a comment and their opinion about ROOMDAO.
We ask our community to say something about us
That's incentivizing posting, and against the rules. The thread should be nuked. Let me just report it and see what happens.

loggin
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
July 06, 2018, 07:33:55 AM
 #26

Why don't you waste your time doing that and see how helpful it is. I doubt they'll even reply and the info probably wouldn't be relevant or helpful. All they'll be able to give you at most is the email address or IP they signed up with and I dount they'll have used one that can be tied directly back to their ICO.

Because i do not have any authority to do so. Do you think that it would have same impact if a nobody asks them for details as compared to someone involved with the forum like the staff.

Also, if you have seen the way micro tasks websites operate, there are websites which contact them and get tasks related to their web property removed. Some websites are thus excluded on these micro jobs sites forever.
aksen
Jr. Member
*
Offline Offline

Activity: 49
Merit: 2


View Profile
August 04, 2018, 07:59:30 AM
 #27

A bigger problem with this issue is that now if no action is taken on this, it will encourage more spammers to use same techniques. There are enough excuses already given by members here to justify this.

Actually, I have seen more such tasks on the same site after I posted this. This seems something out of the control of the forum staff now.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!