Nikitao (@nikitao) • Hey

Explorer of the crypto world.

Stats

Publications

@lens/etherfi thanks for your rewards!🥹
Hey everyone! Please comment and share! Over the past couple weeks I have written and published 3 different LIPs numbered 26,27, and 28. These LIPs introduce the idea of Lens Owned Algorithms, which allow for users to own, import, and export their preferred algorithm on Lens. They also propose the idea of a Lens Algorithm Marketplace, which is a place where User Owned Algorithms can be bought, rented, or sold by users, clients, or third-parties. Finally, the LIPs also introduce the idea of “feed space” where a percentage of what a user sees in their algorithm can be commoditized for the benefit of all parties. Below are the links and LIPs: LIP-26 https://github.com/lens-protocol/LIPs/pull/56 Enhancing Social Media Interaction through User-Owned Algorithms Abstract: The purpose of this LIP is to introduce the concept of user ownership over their feed algorithm through a User Owned Algorithm Token. This token, attached to a user's profile, would be used to generate the user's preferred algorithm. Motivation: The motivation for this LIP is to give users greater ownership over their social media experience. Currently, users own their profiles, collections, content, and followings. It is clear that users should also own their algorithms, especially given the widespread issues with lack of control over algorithms in traditional social media. Both users and apps face problems with the current methods of feed algorithms, which are either limited by following degree of separation logic or rely on generalized algorithms that are poorly tailored to individual users. A User Owned Algorithm Token would empower users to switch apps and view the content they desire while alleviating the burden of algorithm generation from app developers. Specification: There are several ways to manage ownership over a user's desired feed algorithm, but it should serve two primary functions. First, it should allow a user to design and calibrate their own algorithm and import it into a Lens-compatible app. Practically, this could be as simple as a user interacting with content displayed on an algorithm generation front end or within an app itself. Second, it should enable a user to export an algorithm from an app to an on-chain token, which can then be read by other Lens-compatible apps. This means a user should be able to mint their algorithm or authorize an app to export it on their behalf. These two functions form the core purpose of owning a user's feed algorithm. The token could either contain metadata with a list of desired and undesired profiles to be served, potentially requiring another token standard to mark unwanted profiles, and should be able to aggregate lists in a degrees-of-separation manner. Alternatively, it could simply include the basic functions a user has calibrated to generate their feed. The latter approach may be more effective initially, especially if scaling poses a challenge. (Note: I lack expertise in updating metadata cost-efficiently, which is relevant for this last part.)  Rationale The main rationale behind this design is to give users more options in how they interact with social media and more power in app selection, preventing them from being restricted to a closed-off algorithm generation. Additionally, it should allow users to utilize an app even if there is a high propensity for bots. A user-focused approach might also prove to curate algorithms more effectively than a generalized algorithm approach. Backwards Compatibility For apps that service multiple protocols and uses Lens' graphs as subgraphs to a super-graph, exporting would not only be difficult, but also worthless in most cases, and imports might require workarounds depending on their input system for their super-graph. Copyright Copyright and related rights waived via CC0. LIP-27 https://github.com/lens-protocol/LIPs/pull/57 The Lens Algorithm Marketplace description: A marketplace where algorithms can be rented and bought by Lens Users author: <@ZKJew (citing @lens/ethwarrior “0x05-0x263d-DA-2d8c260b”)> Draft type: \<Protocol/Lens Open Algorithm Standard> category: Contracts created: <(2024-06-28)> requires: LIP-26 Abstract The Lens Algorithm Marketplace enables users to monetize their feeds and allows third parties to sell curated feeds to users. LIP-26 proposes a primitive where users can bring their own algorithms to a client and switch between them. This primitive introduces a new category of marketable assets. Instead of clients extracting value from users with their own algorithms, users can now create and sell access to their own algorithms. The marketplace fosters competition among users, clients, and third-party organizations in curating content for mutual benefit rather than exploiting users. 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 The Lens Algorithm Marketplace aims to support the sale or rental of algorithms while keeping their contents confidential utilizing encryption and zero-knowledge cryptography where necessary. It should enable users, clients, third parties, and AI agents mining data to buy, rent, or sell their User-Owned Algorithms (UOAs) on the blockchain. Transactions should be settled via smart contracts, eliminating the need for intermediaries. Essentially, it should serve as an open marketplace where any entity can engage in various forms of trade and curation. Rationale Simply put, the Lens Algorithm Marketplace aims to commoditize User-Owned Algorithm (UOA) feeds, akin to how blockchains have commoditized cryptocurrencies like BTC and ETH. Security Considerations Needs Discussion Copyright Copyright and related rights waived via CC0. LIP-28 https://github.com/lens-protocol/LIPs/pull/58 Introducing User Owned Algorithm Feed Space description: Feed space is the commoditization of an algorithms feed author: <@ZKJew> discussions-to: Lens status: Draft type: Lens Metadata Standard/Lens Open Algorithm Standard created: <(2024-06-29)> requires: LIP-26, LIP-27 Abstract Every User-Owned Algorithm (UOA) will generate specific content for a user based on the specifications outlined in its metadata. This means that the content viewed by the user is determined by what is defined in the UOA's metadata. The Lens Algorithm Marketplace enables the trading of algorithms among various entities. However, it also introduces an opportunity to commoditize the content within the UOA itself, known as "feed space". This refers to the ability for users to profit from the inclusion of metadata in their UOAs. For instance, an emerging creator could benefit by paying for third-party algorithms to incorporate their content into their UOAs for a specified number of posts or a certain duration. This arrangement could mutually benefit both parties involved. Motivation User-Owned Algorithms (UOAs) have the potential to be a decisive factor distinguishing Web3 platforms from traditional social media. By commoditizing the metadata within UOAs, we can level the playing field for creators who lack the network effects needed to compete in today's algorithm-driven environments. Instead of optimizing content purely to appease algorithms, creators can concentrate on producing high-quality content to foster growth, leveraging the ability to purchase feed space within UOAs. This shift allows for a more equitable opportunity for all creators to thrive based on content quality rather than algorithmic manipulation. Specification The availability of feed space should be determined by the owner of the User-Owned Algorithm (UOA). For instance, in a scenario involving a third-party-managed UOA system, the third party should have the ability to offer a percentage of a user's feed, specify the number of users it reaches, the frequency of queries, or the duration content remains visible in the user's UOA metadata. Consider this other example: an advertiser wishes to include ads in 1% of the feed space and offers to pay the user 5 USDC per year. These implementations of feed space enable users to exert greater control and derive benefits from their attention on social media platforms. Rationale The purpose of this LIP is to enhance users' ownership of their social media experience. User-Owned Algorithms (UOAs) empower users to control the content they see in their feeds. The Lens Algorithm Marketplace facilitates the trading of these UOAs in a competitive market, aiming to generate advantages for users. Additionally, the concept of feed space enables users and creators to gain financial or social benefits through the inclusion of curated content in users' feeds. Backwards Compatibility No backward compatibility issues found. Security Considerations Needs discussion. Copyright Copyright and related rights waived via CC0.
I regret that I found out about Phaver too late, but I'm glad that I found out at all😂 #phaver #phairdrop @phaver
👋 to everyone from Morty 🐶
🙏
😂
Not what I expected from ZKSynk, not eligible)
😂🔥🚀
Even if you haven't used Rabby before, you can get points now! Rabby Points Season 2 is here with bigger rewards – 1 Billion points in total! 🎉 @Rabby_io Check your points before you claim! Use my referral code NIKITAO for an extra bonus! https://rabby.io/points?code=NIKITAO https://rabby.io/points?code=NIKITAO
Even if you haven't used Rabby before, you can get points now! Rabby Points Season 2 is here with bigger rewards – 1 Billion points in total! 🎉 @Rabby_io Check your points before you claim! Use my referral code NIKITAO for an extra bonus! https://rabby.io/points?code=NIKITAO https://rabby.io/points?code=NIKITAO
Are you ready for this summer?🚀🚀
🎉🥳