Shoutout to Peakd for instantly removing 'curated' downvotes from UX.
Who knew that complaining like a punk would have such splendid and efficient results!
It's only been a week and Peakd has gotten rid of those super annoying x-downvotes (and all the other bullshit zero-risk troll downvotes used to trigger people and get attention). I was informed on Discord by @ecoinstant. @asgarth does good work.
Now my question becomes:
Did they make sure not to eliminate the downvotes that actually matter?
Indeed they did.
What about https://Hive.Blog ?
It looks like Hive.Blog was always 'curating' downvotes correctly by sprinkling in the downvotes with the upvotes (but I never use Hive.Blog so that's not really relevant to me personally; Peakd and LEOfinance all the way). I don't necessarily agree with this UI because seeing that little minus sign sprinkled in with positive upvotes is a bit tricky, which is probably why Peakd started doing it the other way to begin with.
What about LEOfinance?
Boo!
Still showing nothing downvotes on the frontend, but honestly it's not as big a deal on LEO, because downvotes aren't nearly as triggering on LEO as they are on the main chain. Those of us who've survived a flag war or two (back when they were called flags and not downvotes) know what I'm talking about.
Analysis
It's such a small change, but I think it's going to make a big difference. Whoever was doing that bullshit with the x-downvotes did it for a reason. Super troll move and it triggered a lot of people. Now that trigger troll power has been taken away on the front end.
Frontends are centralized
In fact, every node/server is centralized in nature. The only way something can become decentralized is if there are multiple nodes validating the state of the database and changing/rolling-back the information when it is incorrect. Consensus by definition means multiple servers comes to the same conclusion and making sure to all store that same information as the truth for the rest of eternity.
A lot of people don't understand that a single node (like PEAKD or Hive.Blog or LeoFinance or Ecency or Splinterlands or...) is totally centralized and that node can send you any information they want. They could tell you you have a million dollars in your account very easily. Does that mean you actually have a million dollars in your account? Not according to blockchain consensus, which is the only thing that matters in these cases.
This creates several weird edge cases where trusting the wrong frontend/node could get you into quite a bit of trouble. The frontend could easily trick you into sending money to the wrong place (main attack vector). How many of us actually double check the transactions that Hive Keychain brings up. I know for a fact most of you just blind trust it and click the 'send' button.
Nested points of vulnerability.
It's also very important to note that Hive Keychain itself is a centralized node. In fact it is a centralized node that many many other nodes connect to and is a huge point of vulnerability. We should thank our lucky stars that it has a long history of being trustworthy. That being said it is almost guaranteed that one day one of these nodes will get hacked (or a new blackhat node will pop up that people shouldn't trust but do) and bad things will happen. At the end of the day you only know for sure if you run your own node, and even then it's possible that your own node gets hacked. Don't trust: verify.
I think at the end of the day the only way to make Hive as secure as we need it to be is to create an offline device that can sign transactions through an air-gap and never connects to the Internet. Such a thing would be a huge gain for the network. I've theory crafted such a device in my blog 3 years ago but I'd never be able to create such a thing unless I was a millionaire with a company on Hive like Khal or Theycallmeday or Blocktrades etc. One day!
Conclusion
Again, shoutout to Peakd for fixing this problem immediately.
Pretty cool.
Posted Using LeoFinance Beta
Thanks to both you and @ecoinstant for the suggestion 👍
Same here.
I didn't even noticed these shitty downvotes were removed by Peakd. That much I care about retards like the ones creating such bots...
Posted Using LeoFinance Beta
Whoops who gives a fuck, as long as the echo chamber shills can "edit" whatever they deem, triggering..
btw backlink farmer would downvote everything for strong profiles :) So its smart to remove before SEO people take over.
Definitely a welcome update, even if it's mostly cosmetic. Well done @peakd! And thanks for being one of the squeaky wheels that led to the change...
I guess the thing we all need to remember is that simply being "on the blockchain" doesn't magically exempt us from trollish behaviors and other irritants. Those are part of the human condition and will always be around...
=^..^=
Posted Using LeoFinance Beta
Haha they are actually pretty much annoying. Good job by Peakd.
This really bugs me long term and the bigger this chain gets, the more my paranoia increases
They were misleading for new users. Maybe a new user ignores x and considers that a whale downvoted him only after clicking he will see votes values. I care about that mini heart attack. :)
I didn't even notice the changes. Thanks for letting us know and I do agree that they are a minor inconvenience before when I view things in PeakD.
Posted Using LeoFinance Beta
Seems funny that a free speech advocate would not support free speech, but in fact, want to see it censored?
Those x votes are so folks can follow them and negate the votes of the named accounts.
Nothing wrong with that.
Unpopular, sure, but wrong, no.
@asgarth, put me down as wanting an opt out of that.
I don't need speech filtered by annoyance levels.
I had to click twice to get that.
Too much noise in the room to allow ideas to flourish.
Silencing ideas you don't like doesn't equal having better ideas.
You can still do it. Nothing is censored. It's just that those x accounts will not show up on Peakd UI. Great for UX without hurting free speech at the base level. Win win for all of us!
Posted Using LeoFinance Beta
Nope.
It is silencing those votes.
How about we just ignore certain users' blog posts?
How is that any different than ignoring votes?
In both cases the speech is still there, but no normal user will ever see it.
This is blatant censorship by the premier ui in the hive.
@peakd should not be deciding what can be seen and what can't.
If they want to do such things, they should be opt in.
Why does peakd get to decide what speech is acceptable?
I don't think so. By that logic downvoting someone to zero and making their rep negative would hide them even on hive.blog, is also censorship. Downvotes reduce visibility on Hive frontends. Normal users won't go to hiveblocks and see what's downvoted to dust.
Spam is also hidden for a reason. Good for UX but you can still see those comments on the blockchain level.
Because they own the frontend. Most DApps on Hive are centralized.
Posted Using LeoFinance Beta
So, got it, @peakd is anti-free speech.
Check.
Lol, mate. Maybe!
Still one of the best products built on Hive. :)
Posted Using LeoFinance Beta
Yes, the project I jump to as soon as it is available has a pretty high bar set for it.
I see this decision being amended.
The trending page has been purged of downvotes that don't reach a 1% of the payout threshold.
Individually, irrespective of collective value.
On a 200hbd post, only votes with a value of 2hbd will show.
Any votes of lesser value will not be shown.
That is a very elitist position to take, imo.
That being said it is almost guaranteed that one day one of these nodes will get hacked (or a new blackhat node will pop up that people shouldn't trust but do) and bad things will happen — should we be scared in advance already?!
The downvotes you get sometimes. It appears on a lot of comments. And always the same users !
Peakd FTW! 🔥
Posted Using LeoFinance Beta