Can someone tell me the downside of blocking on all public RPC nodes the known spammers of Hive? I mean, said spammers could spin up their own node, and continue to spam the blockchain.
What would be the issue? No pearl clutching please.
Can someone tell me the downside of blocking on all public RPC nodes the known spammers of Hive? I mean, said spammers could spin up their own node, and continue to spam the blockchain.
What would be the issue? No pearl clutching please.
The bpcvoter accounts, kgakakillerg, maybe a few others. Folks who have a narcissistic belief their rants need to be posted in hundreds of pointless replies to other posts, and who believe they are victims of persecution once downvoted for their spam.
there's a few accounts that post the same garbage thousands of times a day... spammers of the worse caliber. I've blocked them from visibility on snapie, but if you go to other frontends you will see them bpcvoter is one of them. Anyways... the idea is to stop that bloat from happening.
Well as soon as you block one the spammer just creates a new account and then you will need to block that one too and this cycle will just go on forever.
I find them annoying as well. But why not simply mute them? Should be pretty quick for you and their comments will disappear.
Why put the burden on the user to mute obvious spam like bpcvoter. Anyway this was an issue @meno brought up but it was just an observation i made that if the fronttends won’t even block known spammers then how is anyone ever going to get nodes to do it either lol
Why put the burden on the user to mute obvious spam like bpcvoter.
I agree, it's a burden. But also something nobody should decide on your behalf.
We could create a script that could detect a style of post like spam and automatically block them on all levels so that even if they tried to play the cat and mouse game it would be detected but would cost money and need to be done with ai
For now the best thing to do is get them blocked on all front ends. Not sure why peakd won’t even block bpcvoter on their frontend, hive.blog either?
Who is in charge of this decision? The ones you mentioned are very very obvious, but as soon as we create a central authority to assign the label "spammer" this will get out of hand quickly.
What if the guy in charge of that authority decides the account meno is a spammer?
valid point....
What if its tied to reputation?
I know its a slippery slope.... im shooting from the hip, i guess.
Those who are not fans of censorship allow the individual users choose who to mute, which is exactly how a censorship resistant platform should work and this is probably what Peakd will say as well @meno
there’s real content then there is spam content. that’s why we need ai with a harness to make that determination, as long as rules decide and not humans it’s ok
yes that’s just my subjective opinion, we could do without the repetitive spam junk
I believe that if it is truly repetitive & strains resources causing monetary loss or strain, then it's justified to mute an account from the frontend entirely. If it is simply annoying and no more wasteful of resources than other users, then let the individuals choose who 2 mute
i do have those accounts muted, i guess my idea was more about the unnecessary bloat being added every single day.
Most of the blogs/microblogs could be considered unnecessary bloat IMO, lol
It's absurd, yes, but unfortunately, for these things you can't simply block or delete those accounts because they would just end up coming back with new ones.
Aggggghhhh... If only there was a mechanism or function to make those SPAM accounts invisible to the public (Front-end) without having to block or mute them manually. Just by giving them a massive automatic downvote, like a blacklist or something like that... 🤔 Wait... Of course such a thing exists! The Reputation!
But it seems some people don't even consider this important. Even I wouldn't know how this could be useful to us. 🤔