yeshiqi (@yeshiqi) • Hey
yeshiqi (@yeshiqi) • Hey
Publications
- When Lily met Poppy at @lens/ethglobal İstanbul
Find the team on the ground to mint your exclusive @lens/fini
- Crypto 🥹🥹🥹🥹
- 有谁能告诉我，这个应用怎么玩起来的？
- Hey anon, hey!
Hey @lensprotocol family! We are excited to announce our brand new home, https://hey.xyz!
**Why the change?**
Because we wanted to re-introduce ourselves as the one-stop shop for all things Lens. we will be continuing to showcase the latest features from the protocol while listening to our community for what they want to see next.
We will be exploring communities, open actions, and whole new ways you, your NFTs, and the DAOs you’re a part of can benefit from web3 social powered by Lens. This is just the beginning, so thanks for stopping by, and saying hey!
Collect this first ever post by Hey (24 hours!)
- go gogo crypto!!!😀dd
- 🔗 I’ve spoken about this “link” issue before. 🔗
☢️TLDR: competing front ends making decisions for the betterment or detriment of their users.
I’m not sure anyone understands how important the `postId` is, it’s literally the interconnection between all Lens content. If we break the links we now have a fragmented network.
📜LIP3 (share.lens.xyz) was a good temporary solution or so I thought…
👩🏫 Let’s start with some background for those who may be new.
With Lens you can publish once on any front end and the content will display across the entire protocol regardless of the front end you posted from. 🚀🪴
That’s awesome but what happens if you share a link from Lenster.xyz/p/0xhskf-7485857 but I view it in Orb?
1 of 2 things occur:
1️⃣. I click the Lenster link in Orb and I’m taken to my browser to view the content. (Poor ux)
2️⃣. Orb devs transmute the “postId” to be Orb friendly and I can view the content in-app browser or better yet natively (Buttrfly - an ideal ux flow)
So to address this issue LIP3 was created and implemented.
https://github.com/lens-protocol/LIPs/pull/6
However and no disrespect to the team who created LIP3, the share.lens.xyz UX is clunky because it takes you away from whatever app your using to your phones mobile browser (or a new desktop tab? Idk I don’t really use desktop that often), leading to a disrupted experience.
Which brings me to the entire point of this post. 😌
I used share.lens.xyz for the first time in awhile because I was trying to point someone new to @punkess earth shattering “Getting Started” guide and I wasn’t sure which client they would be using, so the perfect opportunity to use share.lens.
I posted from Buttrfly and expected to see the share.lens.xyz link in my post but @0xmoe.lens figured out how to transform the postId into a buttrfly specific link.
So I post the link, everything looks good on my end, but then I have to check other front ends just to make sure it worked like I thought it would.
I check Lenster and I don’t see any link (which now I’m like “shoot they may get lost if the link isn’t there”) 🤔 that’s weird did I do something wrong?
I go to check Lenspeer and the link is there, but not as share.lens but as a Buttrfly link.
⏸️ Look I get it it’s a land grab for users in the early days, which will only grow as the doors are opened to the public, devs have to seize the early opportunity. ⏯️
So a couple things to wrap up….
1️⃣. That tells me the front end wars are about to be epic (this is uncharted territory) and I welcome it, healthy competition leads to great user experiences.
2️⃣. The literal “connections” of the protocol should NOT be left up to developer interpretation. This needs to be standardized at the protocol level.
Otherwise we end up with a broken and fragmented network, not a good way to start a social graph.
cc: @stani.lens @wagmi.lens @nader.lens
ps. my 9-5 is as a Sr. SEO specialist I fundamentally understand the power of links and interconnection, so this is personal for me 😂
- Hello
- Hello