28_08_2028 (@28_08_2028) • Hey
28_08_2028 (@28_08_2028) • Hey
Publications
- I can’t stop finding new utilities for my mac, loving it 🤩
- Summer summer summer 🍦
❣️Israel
GM! Enjoy ur Sunday!
Xx
- I can pretend not to see or secretly miss
Until I touch your warm face
Cicada also slept peacefully
The peaceful summer in my heart
Cicada also slept peacefully
- cool video
👍cool
- gm gm ☀️ what where your #lens highlights this week?
favourite posts, new exciting projects or features, amazing music, awesome images/videos, fun experiments, lens birthday ;-) ...
(hard to imagine but some, a few, people aren't on lens 24x7 🤷♀️. I think it would be awesome to create a weekly community summary feed - for those and everyone else :-). What do you think?)
inspired by https://lenster.xyz/posts/0x019807-0x0481-DA-1a29d38c :-)
- Always in solitude
Give you my best love again
Unconsciously and unwillingly
Arriving at the entrance of the alley again
I didn't cry or laugh
Because this is a dream
No omen, no reason
- % Arabica
My favorite coffee brand in the world! ☕️
- ᴄᴏsʏ / sᴛᴏʀᴍʏ
Have a good day frens 🌿 ✨
- Who's an artist on Lens? Leave a comment
- Good morning 🌻🌻
- Who’s diving into & @orbapp.lens & @lenster.lens first these days - and starting to fade away from Instagram & Twitter ? #socialmedia #faded
- Warm in the heart
I don't know how sad
Smile
Let my dreams fill my eyes
If you can reach out and touch it
- My life goal in web3.0 is to wish everyone a gm
- Does the world still praise silence? It's not enough to explode
- RELEASE - 1.6.0 - August 11th, 2022, 15:00
Features
- feat: metadata v2 support - https://docs.lens.xyz/docs/metadata-standards
- feat: ability to filter on metadata v2 on publication queries
- feat: create a cron for migration so we can execute them in code on box without ssh
- feat: map dedicated lens infura to help with infura public gateway issue
- feat: add notification id in the notification response to help client side caching
- feat: expose endpoint to bring back all the tags filtered by popular and app
- feat: profile and publications syncer now have different crons and x3 load allowance
feat: Integration with ENS to enable the offchain resolve.
back dated feature log:
- feat: ens on-chain identity now in the database
- feat: sybil.org linking for on-chain data https://github.com/Uniswap/sybil-list/blob/master/verified.json
- feat: `onChainIdentity` now exists on `Profile`
- feat: publication stats > `totalAmountOfComments` is a global stat of the amount of comments, if your filtering on sources some comments may not be included in what your trying to show. This means the count number would be wrong. We now have have a field resolver on the `PublicationStats` type which will return the total amount of comments for the sources you specified:
1) commentsTotal(forSources: ["app1", "app2”])
2)postsTotal(forSources: ["app8"])
3) mirrorsTotal(forSources: ["app8"])
4) publicationsTotal(forSources: ["app9"])
- # 1.15.0 and 1.16.0 - 22nd September 2022, 13:30
## Features
- feat: degree of seperation reference module
- feat: add field resolvers for `canComment` and `canMirror`
## Bug fixes
- fix: resolve tagging snapshots
- fix: expose alt tag and cover when snapshotting
- fix: invalidating cache for collects!
- RELEASE - 1.9.1 - August 22nd, 2022, 16:00
Features
- feat: all dApps on testnet can use gasless + dispatcher within the API freely! Happy building!
- # 1.12.0 - 2st September 2020, 14:30
## Features
- feat: big query base generic package lays out the interface to query
- feat: write the machine-learning base package and add the first wtf-rec logic in
- feat: `recommendedProfiles` now uses ML to predict who to follow
## Bug fixes
- fix: explore fix on publications
- fix: profile metadata snapshot
- fix: tagging searching
- fix: metadata filtering and paging
- Your heart is under my control. Do you understand
- Yesterday Lens Protocol announced the CultivatorDAO (👩🌾,👨🌾) to establish community driven content curation for Trust & Safety. Going to share our vision below on how we see the web3 social stack evolve 🧵
First, Lens Protocol is a decentralized social media protocol that acts as a registry to point content and followers. Users can link to any content which can be stored on-chain & off-chain. Most of the content is off-chain (stored in IPFS or Arweave etc).
The Protocol is flexible enough to link the content even to a private cloud or to a self-hosted environment. This is an interesting use case for follower and token gated content. It's up to the applications and users to choose how they use Lens Protocol.
Lens Protocol design guarantees users the access to their own social network. You don't need to trust centralized or off-chain platforms with your followers. Meaning every user has their own social network.
Not only you own your own network, but you also have the ability to broadcast content in a permissionless and censorship resistant way. Anyone you grant the access to your content has the ability to explore your creativity and self expression. This is decentralization by design.
While decentralization is groundbreaking for web3 social, the amount of information and finding relevant peers and content for you to discover would be a time consuming mission. This reason is why we would see another stack evolve - the middleware - where curation lives.
The middleware layer already exists on Lens Protocol, there are tools such as Graph Protocol, RSS3, Sepana and the Lens API. The middleware layer consists from widely decentralized appoaches to being progressively decentralized depending on the use cases they serve.
The latest addition to the middleware are communities such as the CultivatorDAO, focusing on curation with Trust & Safety in mind. Where code cannot solve everything, we need communities to reflect their values and govern.
The DAOs of the Lensverse will serve the application layer for various tasks ranging from building discovery algorithms, content moderation and solving various challenges that social media faces today.
The key difference between the web2 and web3 social stack is that in web3, the stack is completely open. When you don't like a policy or an experience, as a user you should be able to find a new experience without leaving behind your accumulated social capital.
Hopefully we will see small communities evolve across the web3 social ecosystem, being utilized for tasks that would benefit from community governance.
I would even imagine that every social media application built on top of Lens Protocol would have its own DAO consisting of its community members voted by the community that reflects the their own values.
Most importantly, these DAOs can operate transparently and since the measures taken by these DAOs are public, there should not be any shadow banning (see here: https://lenster.xyz/posts/0x05-0x0417).
By ensuring human assessment and the design that leads to decentralization, we are able to ensure that web3 social doesn't become a closed platform and users are able to access to open social networks that are driven by community engagement & stewardship.
Building a decentralized stack is a harder exercise than starting from a centralized approach, but brings the benefit of fully verified content linking on-chain wherever you store your content, ownership to your social graph, ability to use timestamps and create programmability.
And most importantly: decentralized and on-chain content and follower registries opens up the programmability and composability to another level. Imagine pairing Lens with tools like Simo, Lit Protocol, DeFi, NFTs, ReFi and DAO governance.
Besides reachitecturing the social stack, part of the mission for the Lens team is to make the social stack more accessible. Now with all interactions across the Lens Protocol, users do not need to sign or pay any gas. Blockchain on the backend, party on the frontend 🥳
Next Monday, you will be able to vote for CultivatorDAO with your Lens Profile to signal your support for community driven stewardship https://snapshot.org/#/cultivatordao.eth/proposal/0xd512345eb6c9b7bbf57b28a8b4f7dc46d31ab6c19ac8ad5de4605fa52fcb9e98
If you love our vision and what we are building, collect and mirror this post to retain your early user flexing rights 🌿
- RELEASE - 1.7.0 + 1.8.0 - August 19th, 2022, 10:00
Features
- feat: dispatcher public API! (whitelisted apps)
- feat: upgrade relay npm package
- feat: extra info for claiming
- feat: worldcoin integration https://human.withlens.app/
- feat: worldcoin on chain identity is now on the profile
- feat: improve graceful shutdown of pods
Posted using the dispatcher!
- # 1.10.0 - August 24th 2022, 11:00
## Features
- feat: allow unknown collect modules (sandbox incoming)
- feat: allow unknown follow modules (sandbox incoming)
- feat: allow unknown reference modules (sandbox incoming)
- feat: improve error tracing
- feat: whitelist orbs and social3 for relay
- feat: bake in retries of the relay on proxyActions
- feat: add `getWhoReactedPublication` so you can fetch who reacted to a publication
- feat: enable `fastest` in relay mode to avoid going into secondary nodes
- feat: prod API dashboard deployment
## Bug fixes
- fix: issue sometimes getting back reactions
- fix: extra checks if only followers can collect the free collect
- # 1.12.1 - 5th September 2022, 13:00
## Features
- feat: make explore default time 24 hours not 1 week to try to explore more publications and make it more fun for UIs
- feat: add new explore filter which is `CURATED_PROFILES` to allow discovery on known good content profiles
- feat: order collects by default profiles first then collected times to make profiles be top
- feat: order followers by default profiles first then follow time to make discovery better and wallet fall at the bottom
- feat: make random on explore a bit better instead of random everything use only its context it got back
- Away from the hustle and bustle of the world
- WTF is the Merge? Kyla Scanlon explains 👇