Post by @stani • Hey
Should likes/upvotes be on-chain?
Comments
- No, this should be the frontend's job. At the protocol level, there should be no bias or influence on different posts such as upvotes/likes. This should be up to the frontend which can then determine what should be shown to its users.
- Absolutely! I think things that are "signal boosters" should be on chain. This definitely falls under that.
- what if those are web2 concepts that are best replaced entirely by mirroring and collecting? maybe upvotes/downvotes become frontend specific data associated with communities
- I think so.
- Yes maybe use rollups to reduce gas 🤓
- Let's vote 🗳️
- Yes I think everything on-chain
- yes definitely on chain
- Hmm. My opinion is to upvote
- Certainly
- Yes, Sir.
- Definitely, so other apps could use them.
- Yes... it should be... was actually looking for the options when i first logged in.
- In principle, yes, it is debatable.
- Yes! lfg!
- What are pros and cons? I'm too lazy to think of it myself, so pls do us a favor... )
- Yes.
- Apart from Profile NFT's and Follow NFT's, is there anything else on-chain right now?
- i think so!
- Isn't the collect feature already a like? What would be the benefit of having a collect and a like function?
- As I read through everyone's posts, I find myself constantly reaching for the non-existent "like" button. So it's a big yes from me.
- No. Likes are too noisy and lightweight signals for the core protocol at this stage. Let dApps experiment/implement /validate on-chain likes first.
- Yes, On-Chain is the key of Web3 future
- yes
- Yes!
- yes, please
- that would be great!
- better for search/listing algo's. data can't be faked
- yes, please ^^
- yep