Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LIP-29] A Framework Detailing LIPs 26, 27, and 28 #59

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ZKJew
Copy link
Contributor

@ZKJew ZKJew commented Jul 4, 2024

[LIP-29]
A Framework detailing the Lens Algorithm Ecosystem

https://hey.xyz/posts/0xdd33-0x088d-DA-70721a96

Abstract

LIPs-26, 27, and 28 propose a plethora of new ways a user can retain ownership over their algorithm and feed. They propose a standard of User Owned Feeds (UOFs) that can be created by agents, imported to apps, and exported on-chain by apps. They also recommend a Lens Algorithm Marketplace, which fosters the buying, renting, and selling of curated content; on top of that, it also creates the auctioning of “feed space” or a part of a user’s feed in their UOF’s metadata. To carry these ideas out LIP-29 lays out a framework detailing roles of entities in this ecosystem, which consist of users, agents, apps, and 3rd party algorithm generators.

Motivation

This LIP aims to create a marketplace for User-Owned Feed Tokens (UOFs) in order to expand their capabilities. In this marketplace, users' agents can purchase or rent curated content for UOFs, earn from their own content, or utilize curation by third parties. By introducing a free-market approach to content curation, users can potentially benefit from algorithms that currently exploit them in today's social media landscape.

Specification/Rationale

The main promise of this LIP and its components is to provide the proper incentives for the cheapest and best feeds for users, as well as decreasing the switching costs between apps. This is done by the separation of power in the insertion of the metadata to the users’ feed. In the system, the user provides basic data and preferences to an agent. The agent is paid in some form (ex. Collect fee or time spent on app from apps, or payment from third parties) to fill the user’s feed with desirable content. The agent then brokers feed space in the UOF on the user’s behalf to provide the best content from 3rd parties and maximize revenue for the user. In one scenario, the agent might sell a user’s premium content to 3rd parties. In another, it might hold a bidding contest between two competing 3rd parties. There are a lot of plausible applications of this framework creating a whole economy, as well as more avenues of ownership for users and creators. It allows creators to target likely new followers by allowing agents to purchase feed space precisely. And, it reduces the overall opportunity cost that every web2 user has of being monetized by an entity other than themselves.

Security Considerations

Needs discussion.

Copyright

Copyright and related rights waived via CC0.

[LIP-29]
A Framework detailing the Lens Algorithm Ecosystem

Abstract

  LIPs-26, 27, and 28 propose a plethora of new ways a user can retain ownership over their algorithm and feed. They propose a standard of User Owned Algorithms (UOA) that can be created, imported to apps, and exported on-chain by apps. They also recommend a Lens Algorithm Marketplace, which fosters the buying, renting, and selling of algorithms; on top of that, it also creates the transactability of “feed space” or a part of a user’s feed in their UOA’s metadata. To carry these ideas out LIP-29 lays out a framework detailing roles of entities in this ecosystem, which consist of users, agents, apps, and 3rd party algorithm generators.

Motivation

  This LIP aims to create a marketplace for User-Owned Algorithm Tokens (UOAs) in order to expand their distribution. In this marketplace, users can purchase or rent UOAs, earn from their own UOAs, or utilize UOAs curated by third parties. By introducing a free-market approach to content curation, users can potentially benefit from algorithms that currently exploit them in today's social media landscape.

Specification/Rationale

    The main promise of this LIP and its components is to provide the proper incentives for the cheapest and best algorithms for users, as well as decreasing the switching costs between apps. This is done by the separation of power in the insertion of the metadata to the users’ UOA. In the system, the user provides basic instructions, mostly in the form of feedback to an agent. The agent is paid in some form (ex. Collect fee or time spent on app from apps, or payment from third parties) to fill the user’s feed with desirable content. The agent then brokers feed space in the UOA on the user’s behalf to provide the best content from 3rd parties and maximize revenue for the user. In one scenario, the agent might sell a user’s premium content to 3rd parties. In another, it might hold a bidding contest between two competing 3rd parties. There are a lot of plausible applications of this framework creating a whole economy, as well as more avenues of ownership for users and creators. It allows creators to target likely new followers by allowing agents to purchase feed space precisely. And, it reduces the overall opportunity cost that every web2 user has of being monetized by an entity other than themselves.

Security Considerations

  All LIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. For example, include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. LIP submissions missing the "Security Considerations" section will be rejected. An LIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.

Needs discussion.

Copyright

Copyright and related rights waived via CC0.
Copy link

height bot commented Jul 4, 2024

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

@ZKJew ZKJew changed the title [LIP-29] A Framework Detailing How LIPs 26, 27, and 28 could be achieved [LIP-29] A Framework Detailing LIPs 26, 27, and 28 Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant