Such "likes" already exist, it's just matter of sorting trending by amount of upvotes not the weight of upvotes, but that's just a bad idea.
Yes, you can create 1000 accounts on Tik Tok, but Tik Tok can remove those accounts if they will find that you are abusing system for your gain. On Hive created accounts are forever.
Everything that can be abused will be abused.
Those likes would give you visibility and visibility has value.
Even if you check how currently trending page looks like with "one user = one vote" rule, it's not how it will look like when you apply such algorithm because people will adapt. And trust me, those won't be people with most awesome content around.
You are viewing a single comment's thread from:
That's only partly true; from the responses I have been getting so far I think most still don't understand that this is not an either/or but a both/and system: "upvotes" and "likes" would both add to trending. It is a matter of implementation how these two systems would work together (i.e., how much "weight" they have and this could be worked out by adapting to user behavior).
The other objection I have is that this is more speculation on your part: We simply don't know how users would respond. Similarly to how we weren't sure how the EIP would be adopted we had to test it in order to see the results. I think it's not very productive if we dismiss some ideas on Hive too quickly without seeing them in action first (is there a public testnet for something like this?).
It should also be relatively simple to add abusers/spammers to blacklists as is already being done so that their "likes" would't count. As @markkujantunen already pointed out there could also be "dislikes".
No :-) It's not partly true. It's just true. :-)
Vote from user means vote from user. There can't be two votes from single users so simple count of votes exists.
Hive gives you everything you need to build your own trending according to your own algorithm.
No. It's not speculation on my part it's knowledge about how such systems works.
There's no need to see something in action to know how what will happen. Knowledge, experience, that kind of stuff. There's not even a requirement for testnet because that's just a matter of front end (Well, a little bit complicated to compute stuff, but definitely 2nd layer thing on backend to compute such trending page and display it as trending in condenser). That also means that it doesn't have to be anything platform wide. And because of that, if you don't think it's a waste of time and resources, you can invest your own to try it out running your own frontend that implemented you own algorithm.
PS
Different weights for votes (with different or no relation to HP but with relation to other account metrics like rep 2.0) could of work but has nothing to do with your one user = one vote idea.
I think this is exactly my point: couldn't there be some? I guess this is more of a frontend issue (but it could therefore also be easy to implement?)
I wish I could...Unfortunately I am not a developer, so I am just trying to get my idea out there :) This kind of discussion is exactly what I had hoped for. But I think I haven't quite explained my idea too well (or at least I think it is still misunderstood or I don't understand the fundamentals enough to see that this can't work 😅)
We need something like this on Hive as PoB clearly doesn't work as intended currently. As long as we don't solve this, I don't see Hive thriving (at least as a social media site).
That was my idea.
Then there would be no pressure to be fast or check who else upvoted a post.
yes, we should get rid of the curation window! :)
Right, and a linear curation (not author) rewards curve, otherwise it would be profitable for bots to vote as fast as possible without curation window.
👍 so how do we make it happen?