You are viewing a single comment's thread from:

RE: Can Steemit Get Rid of Spam and Abuse?

in #steemit6 years ago (edited)

TBH (to be honest)...

Steemit can "hide" spam and abuse from being viewed. It cannot stop it from occurring or polluting the blockchain.

No more than Microsoft Hotmail or Outlook 365 can stop spam or abuse. It can only try to hide it from appearing in people's inboxes.

Spam and abuse will be prevalent on the blockchain because there is no way to code human ingenuity and greed from abusing things.

each user can select who they want to block and create their own blacklist. It's that simple

Unfortunately, not that simple. Let's say you have 100,000 users. Each user has 1,000 people on their blacklist. (which is quite small considering the number of spammy new accounts that can exist)

Now that becomes 1 million blacklisted user accounts for 100,000 users. At some point, the lag and resources needed to handle all the blacklists start to become a bottleneck for the 3 second blockchain timing to show new posts.

It's not scalable to create blacklists for each user, miles long.

You have the right idea. It's just not feasible.

Sort:  

Major free email providers will allow all incoming junk mail and sort them in the spam folder for you. However, there are many approaches to keep emails free from spam, such as IP block lists, grey listing, firewall rules, that prevent spam from reaching the users, therefore tackling the issue at the source. It's a riskier approach because there's a slim chance for false positives if the sending email server is misconfigured (e.g. lack of SPF, DKIM or DMARC records).

P.S. Indeed, concerning the scalability, that's easily circumvented by setting a limit on the blacklist size (say, max 50), just like voting for 30 witnesses. You can select the most spammy accounts you want to block.

Close, but not quite.

Spammers are hacking legitimate accounts behind SPF, DKIM, and DMARC just so their spam can get through from a legitimate email account with those semi-verified features infront of the domain name.

I'm quite skilled at mail servers and the way they operate, much like yourself, to fully understand SPF, DKIM, and DMARC

In your own words:

many approaches

They are all approaches. None of them are 100% spam-proof. If they were, then the inventor of an 100% anti-spam internet would win a nobel prize.

However, that is not the case. Spam on the internet is more than a disease, it's a worldwide plague that eats bandwidth and traffic everyday and it is neverending.

Who pays for spam, the bandwidth it uses, and the resources it requires to try different "approaches" to block it?

The paying users do. Not the ones abusing the system.

This is a big problem, and having blacklists may mitigate the issue a bit.. but it is no where near solving it.

P.S. Indeed, concerning the scalability, that's easily circumvented by setting a limit on the blacklist size (say, max 50)

50 could be filled in a day, by each user on the system. No where near enough. :(

I'm skilled with mail servers too, I've been running my own for years 🤓

Luckily the majority of spammers are amateurs and never bother to configure and run their own servers; when they do, it's poorly configured. Often they use sendgrid or other big services. Indeed, we can't solve the spam problem at 100%, but if we can minimize it then it's a step forward.

Nice to meet a fellow postmaster. :)

A majority of the let's say 100.000 users will rather agree on who the spammers are. Not all those users will have different spammers on their blacklists.
They might agree roughly on the number of real spammers, and that's what the blockchain has to handle.
In the end it is quite a democratic process.

Coin Marketplace

STEEM 0.19
TRX 0.15
JST 0.029
BTC 63931.73
ETH 2663.43
USDT 1.00
SBD 2.84