Comment by @thefaketomato • Hey
I'm a little uneasy with the approach you're taking here of keeping the algorithm closed in the interest of preventing it from being gamed. I'm already see
Comments
- Every algorithm can be enabled or disabled at the API level, allowing users to toggle them as needed. Our goal is to maintain openness and transparency, but as we've noticed, bot-generated noise can sometimes detract from the overall experience. Our priority is to enhance user experience first and foremost, while remaining strong supporters of open algorithms and continuing to adopt this approach as we go.
We've also provided an explanation of how high-value notifications function (admittedly, it's not very sophisticated at the moment) in our API documentation, which can be found here: https://docs.lens.xyz/docs/users-notifications
- The idea of a closed algorithm does raise some concerns, especially when it comes to false positives and genuine accounts getting caught in the crossfire. I still believe that allowing us to block fake accounts as we spot them, aligns better with the ethos of web3 and offers greater control over our digital experiences. After all, steering clear of centralized "algorithms" is one of the reasons we're drawn to this new digital frontier. But of course, I would also like to see if this could really improve the overall experience.
- I reckon this is a kind of dilemma situation. I have great faith in lens team working out the best possible solution.