From bb36b8674ad3f91487ac07f5ccfcb8af46485dd3 Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Sat, 29 Jun 2024 00:44:41 -0400
Subject: [PATCH 1/5] [LIP-28].md

---
 LIPs/lip-template.md | 57 +++++++++++---------------------------------
 1 file changed, 14 insertions(+), 43 deletions(-)

diff --git a/LIPs/lip-template.md b/LIPs/lip-template.md
index 37e0748..8e1d0a0 100644
--- a/LIPs/lip-template.md
+++ b/LIPs/lip-template.md
@@ -1,79 +1,50 @@
 ---
-title: <The LIP title is a few words, not a complete sentence>
-description: <Description is one full (short) sentence>
-author: <a comma separated list of the author's or authors' name + GitHub username (in parenthesis), or name and email (in angle brackets).  Example, FirstName LastName (@GitHubUsername), FirstName LastName <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
-discussions-to: <URL>
+title: <Introducing User Owned Algorithm Feed Space>
+description: <Feedspace is the commoditization of an algorithms feed>
+author: <@zkjew>
+discussions-to: <Lens>
 status: Draft
-type: <Protocol, Lens Metadata Standard, or Lens Open Algorithm Standard>
-category: <Contracts, API, SDK> # Only required for Protocol. Otherwise, remove this field.
-created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
-requires: <LIP number(s)> # Only required when you reference an LIP which is also dependent on this to work. Otherwise, remove this field.
+type: <Lens Metadata Standard/Lens Open Algorithm Standard>
+created: <(2024-06-29)>
+requires: <LIP-26, LIP-27>
 ---
 
 ## Abstract
 
 <!--
-  The Abstract is a multi-sentence (short paragraph) technical summary. This should be a very terse and human-readable version of the specification section. Someone should be able to read only the abstract to get the gist of what this specification does.
+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 "feedspace". This refers to the ability for users to profit from the inclusion of metadata in their UOAs.
 
-  TODO: Remove this comment before submitting
+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
 
 <!--
-  This section is optional.
-
-  The motivation section should include a description of any nontrivial problems the LIP solves. It should not describe how the LIP solves those problems, unless it is not immediately obvious. It should not describe why the LIP should be made into a standard, unless it is not immediately obvious.
-
-  With a few exceptions, external links are not allowed. If you feel that a particular resource would demonstrate a compelling case for your LIP, then save it as a printer-friendly PDF, put it in the assets folder, and link to that copy.
-
-  TODO: Remove this comment before submitting
+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 Specification section should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Lens platforms
-  TODO: Remove this comment before submitting
+The availability of feedspace 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 feedspace enable users to exert greater control and derive benefits from their attention on social media platforms.
+
 -->
 
 ## Rationale
 
 <!--
-  The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages.
-
-  The current placeholder is acceptable for a draft.
-
-  TODO: Remove this comment before submitting
+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.
 -->
 
 TBD
 
 ## Backwards Compatibility
 
-<!--
-
-  This section is optional.
-
-  All LIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The LIP must explain how the author proposes to deal with these incompatibilities. LIP submissions without a sufficient backwards compatibility treatise may be rejected outright.
-
-  The current placeholder is acceptable for a draft.
-
-  TODO: Remove this comment before submitting
--->
-
 No backward compatibility issues found.
 
 ## 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.
-
-  The current placeholder is acceptable for a draft.
-
-  TODO: Remove this comment before submitting
--->
-
 Needs discussion.
 
 ## Copyright

From e6903bdb7dce65752c3bf1749e55737202f080b4 Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Sat, 29 Jun 2024 00:48:12 -0400
Subject: [PATCH 2/5] [LIP-28].md

---
 LIPs/lip-template.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/LIPs/lip-template.md b/LIPs/lip-template.md
index 8e1d0a0..38a4ea6 100644
--- a/LIPs/lip-template.md
+++ b/LIPs/lip-template.md
@@ -1,6 +1,6 @@
 ---
 title: <Introducing User Owned Algorithm Feed Space>
-description: <Feedspace is the commoditization of an algorithms feed>
+description: <Feed space is the commoditization of an algorithms feed>
 author: <@zkjew>
 discussions-to: <Lens>
 status: Draft
@@ -26,8 +26,8 @@ User-Owned Algorithms (UOAs) have the potential to be a decisive factor distingu
 ## Specification
 
 <!--
-The availability of feedspace 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 feedspace enable users to exert greater control and derive benefits from their attention on social media platforms.
+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.
 
 -->
 
@@ -37,7 +37,6 @@ Consider this other example: an advertiser wishes to include ads in 1% of the fe
 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.
 -->
 
-TBD
 
 ## Backwards Compatibility
 

From d2ed558e32ea166634500ecd0b47c3b6c1686f15 Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Mon, 19 Aug 2024 22:18:20 -0400
Subject: [PATCH 3/5] [LIP-28].md

---
 LIPs/lip-template.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/LIPs/lip-template.md b/LIPs/lip-template.md
index 38a4ea6..9373b35 100644
--- a/LIPs/lip-template.md
+++ b/LIPs/lip-template.md
@@ -12,7 +12,7 @@ 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 "feedspace". This refers to the ability for users to profit from the inclusion of metadata in their UOAs.
+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 inclusion of posts in a users feed. However, it also introduces an opportunity to commoditize the content within the UOA itself, known as "feedspace". 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.
 -->

From d949a501f4a550b8442755970c023dbf3f6d4237 Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Fri, 23 Aug 2024 20:27:46 -0400
Subject: [PATCH 4/5] [LIP-28].md

Updated vision
---
 LIPs/LIP-28.md       | 48 +++++++++++++++++++++++++++++++++++++++++
 LIPs/lip-template.md | 51 --------------------------------------------
 2 files changed, 48 insertions(+), 51 deletions(-)
 create mode 100644 LIPs/LIP-28.md
 delete mode 100644 LIPs/lip-template.md

diff --git a/LIPs/LIP-28.md b/LIPs/LIP-28.md
new file mode 100644
index 0000000..763124d
--- /dev/null
+++ b/LIPs/LIP-28.md
@@ -0,0 +1,48 @@
+---
+title: <Introducing User Owned Feed Space>
+description: <Feed space is the commoditization of an user's 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 Feed (UOF) will generate specific content for a user based on the posts and preferences inscribed in its metadata. This means that the content viewed by the user is determined by what is defined in the UOF's metadata on all apps that use a particular UOF (note: a user might have multiple UOF's for differenct types of apps). The Lens Algorithm Marketplace enables the trading of inclusion of posts in a users feed. However, it also introduces an opportunity to commoditize the content within the UOF itself, known as "feedspace". This refers to the ability for users to profit from the inclusion of posts in their UOFs.
+>
+
+## Motivation
+
+<!--
+User-Owned Feeds (UOFs) have the potential to be a decisive factor distinguishing Web3 platforms from traditional social media. By commoditizing the metadata within UOFs, we can level the playing field for apps who lack the resources needed to compete in today's sophisticated algorithm-driven environment. 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 UOFs and for algorithm generators to reward content in a less clear way. 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 Feeds' (UOF) agent, or actor that is generating the inscriptions of the users feed though an algorithm with the users delegation. An agent can determine what can or cannot be included in a users feed based on a users preferences and market conditions. A user should have the ability to override an agent through forced inclusion or exclusion on their app. An agent filling a users feedspace must workwithin the metadata standards of a UOF and can be undelegated by a user that wishes to switch agents (even if this is to themselves).
+
+-->
+
+## Rationale
+
+<!--
+The purpose of this LIP is to enhance users' ownership of their social media experience. User-Owned Feeds (UOFs) 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.
diff --git a/LIPs/lip-template.md b/LIPs/lip-template.md
deleted file mode 100644
index 9373b35..0000000
--- a/LIPs/lip-template.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: <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 inclusion of posts in a users feed. However, it also introduces an opportunity to commoditize the content within the UOA itself, known as "feedspace". 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.

From 79e0f10ac17a9c9fc06cfc4852df335f28744faa Mon Sep 17 00:00:00 2001
From: ZKJew <106914330+ZKJew@users.noreply.github.com>
Date: Fri, 23 Aug 2024 20:36:30 -0400
Subject: [PATCH 5/5] [LIP-28].md

---
 LIPs/LIP-28.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/LIPs/LIP-28.md b/LIPs/LIP-28.md
index 763124d..595b300 100644
--- a/LIPs/LIP-28.md
+++ b/LIPs/LIP-28.md
@@ -17,22 +17,22 @@ Every User-Owned Feed (UOF) will generate specific content for a user based on t
 
 ## Motivation
 
-<!--
+<
 User-Owned Feeds (UOFs) have the potential to be a decisive factor distinguishing Web3 platforms from traditional social media. By commoditizing the metadata within UOFs, we can level the playing field for apps who lack the resources needed to compete in today's sophisticated algorithm-driven environment. 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 UOFs and for algorithm generators to reward content in a less clear way. 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 Feeds' (UOF) agent, or actor that is generating the inscriptions of the users feed though an algorithm with the users delegation. An agent can determine what can or cannot be included in a users feed based on a users preferences and market conditions. A user should have the ability to override an agent through forced inclusion or exclusion on their app. An agent filling a users feedspace must workwithin the metadata standards of a UOF and can be undelegated by a user that wishes to switch agents (even if this is to themselves).
 
--->
+>
 
 ## Rationale
 
-<!--
+<
 The purpose of this LIP is to enhance users' ownership of their social media experience. User-Owned Feeds (UOFs) 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