Post by @zkjew • Hey
https://github.com/lens-protocol/LIPs/pull/56
Hey everyone! I just wrote a comment on users ability to own their own feed algorithm. I would love to hear s
Comments
- Who would design the algorithm? Honestly, I think there could be a market for algorithms. If there is a token that represents it let’s add a market into it, because it would incentive developers to create and maintain competitive algorithms.
Overall I support this especially if it can be standardized across multiple clients.
- I like the idea to store preferences somewhere, apps can use to improve the UX.
this should work for sth like notifications and blocking profiles “easily”.
Amazing would be another layer based on semantics / content. “Show me cat, coffee and L2 related content“. But I think it must be as easy as this to be used at scale.
- OK, first of all, I think this is a very important issue, especially because I feel that the initial "Hey + Karmalabs custom feed algorithms" approach has been somewhat sidelined, and we are forced to use the algorithms created directly by the apps.
At the same time, I feel that the implementation is quite difficult. The use of Open Actions at the protocol level is a good example of this - although the Swap Open Action has been available for a long time, no one has integrated this very useful feature except for one app. So, applications built on Lens would need to fully commit to this solution - which, of course, could mean that their own algorithms might take a back seat.
My second concern is how exactly do you envision this?
Are you only thinking of a pure list of wanted/unwanted profiles stored/connected to each ser Owned Algorithm Token, to which profiles can be added "manually", and the wanted profiles would appear more frequently than neutral profiles in the user's feed through some simple weighting, and unwanted profiles would appear less frequently (or be completely excluded)? In addition should "wantedness" and "unwantedness" be totally new Lens primitives or can we express this by upvotes and downvotes/blocks? If they are new options to do, do we need a new Lens-based dapp where we can customize our token?
What would be the basis for creating the feed algorithm? Even if it's just a simple weighting of the Wanted - Unwanted options, 1, I think we need to handle every profile included nor in Wanted or Unwanted lists as Neutral profiles (because do not want to exclude them from our feeds totally, right?) - so this is a 3rd category 2, We need to build up customizable algorithms for weighting the 3 categories. But who will create the algorithm itself? The average user doesn't have enough knowledge for this. I can imagine creating a basic algorithm library that users can access and, with the necessary technical knowledge, fork/modify. However, this exceeds the capabilities and perhaps even the needs of the average user. So, this must be solved mainly from the Lens side.
In summary, I have a lot of "hows" but I find it a very interesting LIP, and I think it's worth dealing with something like this to get back to our Lens roots.
Sorry for not responding directly on Github, I only have my personal profile, which I didn't want to reveal. 😄