Author

Topic: Crackdown on obvious Currency exchange scams (Read 77 times)

hero member
Activity: 882
Merit: 544
Newbies should be fine if they are reading properly because there is a red note below the trust rating of the scammer warning all users to trade with the scammer with extreme caution. I think it should be enough to warn newbies to help them avoid that risk. If they still got scammed after that, I think it ain't the administration's fault anymore(since they have been warned). For the first case though, you can just report the post to moderator.
sr. member
Activity: 658
Merit: 282
I was wondering why the administration is tolerating the blatant scam
attempts using "locked topics" that have been going on for months.

E.g. threads like this where a user attempts to sell huge amounts of BTC
through an "International Escrow" that is redirecting to a phishing site.

https://bitcointalksearch.org/topic/sell-bitcoin-by-bank-transfer-worldwide-large-sums-otc-offers-3395124

Another example is this thread by a user with several negative trust
ratings that bumps his locked thread basically every day in an attempt
to scam gullible newbies.

https://bitcointalksearch.org/topic/no-2757782

Of course most users won´t fall for a predictable scheme like this, but there
is still the odd chance that someone loses funds by trading with one of the guys in question.
By locking their topics after every bump they prevent other users from exposing
their blatant scam attempts.
This behavior has been going on for weeks and aside from the obvious risks for
unsuspecting newcomers to Bitcointalk it clutters the currency exchange subforum.

I know that the administrators have a rather libertarian attitude and tend to allow
all kinds of things, but this is an obvious risk for newcomers to Bitcointalk and
in my opinion a ruthless abuse of the ability to lock your own topics.
The fact that the users in question already have been tagged negatively is a good
first step, but newbies might not be as familiar with the trust system as most
long-time users.




Jump to: