Lenstube - is a decentralised social media video sharing platform created using the Lens protocol

Lens Protocol is a composable and decentralized social graph, ready for you to build on so you can focus on creating a great experience, not scaling your users.

The Lens Protocol is a Web3 social graph on the Polygon Proof-of-Stake blockchain. It is designed to empower creators to own the links between themselves and their community, forming a fully composable, user-owned social graph. The protocol is built from the ground up with modularity in mind, allowing new features and fixes to be added while ensuring immutable user-owned content and social relationships.

Lens Protocol seeks to solve major issues in existing social media networks. Namely, Web2 networks all read from their unique, centralized database. There is no portability. Your profile, friends, and content are locked to a specific network and owned by the network operator. This causes each network to fight a zero-sum game for your attention.

Lens Protocol corrects this by being a user-owned, open social graph that any application can plug into. Since users own their data, they can bring it to any application built on top of Lens Protocol. As the true owners of their content, creators no longer need to worry about losing their content, audience, and livelihood based on the whims of an individual platform's algorithms and policies. Additionally, each application using Lens Protocol benefits the whole ecosystem, turning the zero-sum game into a collaborative one. Developers can design meaningful social experiences without needing to turn to feedback mechanisms to lock in a user's attention.

The purpose of the Lens Protocol is to empower creators to own the links between themselves and their community, forming a fully composable, decentralized social graph. This is achieved by allowing users to create profiles and interact with each other via these profiles. "Profile" (as used here) refers specifically to Lens profiles; "user" refers to standard crypto-wallets.

The protocol is built from the ground up with modularity in mind. Lens Protocol is currently overseen by a multisig, which will be expanded to a broader DAO, which can develop and vote on new modules and expanded functionality.

Architecture

Let's first dig into profile creation and publishing. Users must create a profile on the hub, for which they will receive a sequentially ID'd profile NFT. This NFT controls the profile, and thus, its owner becomes the de facto controller of the given profile.

Profile owners can:

1. Publish to the profile. Publication types are:
   1. Post: A standard piece of content.
   2. Comment: A standard piece of content with a pointer to another publication.
      1. Since comments include a pointer, this executes the pointed publication's "reference module" logic, if any.
   3. Mirror: The equivalent of a "share" in a traditional sense, having no content but a pointer to another publication.
      1. Since mirrors only include a pointer, this executes the pointed publication's "reference module" logic, if any.
2. Set the profile's "follow module":
   1. This whitelisted logic contract determines the logic that must be executed when a wallet attempts to follow the given profile; for example, some followers may incur a fee to the profile owner via the fee follow module contract.
3. Set the profile's image URI
4. Set the profile's "dispatcher":
   1. This is an address that can act on behalf of a profile's owner; it can:
      1. Publish to the given profile.
      2. Set the given profile's URI.

Regular wallets can:

1. Follow profiles:
   1. This executes the profile's "follow module" logic, if any.
   2. This mints the following wallet a "follow NFT" unique to that profile and sequentially ID'd.
      1. Follow NFTs have a custom URI set by profile owners.