Comment by @definn • Hey
I totally get where you're coming from! As a fellow SEO (though, I believe there might've been some misunderstanding with Buttrfly because they typically d
Comments
- > rather than prompting a 'choose your app' page, it could directly redirect based on the initiating app.
I hinted at the same approach here: https://share.lens.xyz/p/0x3a-0x29
The issue I see with adopting a scheme `lens://` is that without some kind of processing the link doesn't work per se. The idea with `share.lens.xyz` is that it would always work also when shared on non-Lens powered social app.
Rich previews via OG meta tags would also be impacted. Right now Lens Share links show previews on Discord, Twitter, Slack, TG, Lenster, etc.
- Yep each app should be able to build app specific links so that devs can keep users within their ecosystem.
imho I think the best way that happens while keeping everything fair is with `lens://postId` that way dev pulls link and builds `app.specific/p/postId` no different that `ipfs://` or Arweave’s `ar://`
That keeps the playing field level because devs can keep the users they’ve worked so hard to obtain.
🫡 fellow SEO.
- Good point regarding gated communities on different apps, accessible only via that specific app. The immediate gating vector would be to wrap all your app in a master community and bam, you can tap into the full Lens userbase but keep your contents to yourself.
This would probably still be a loosing strategy in the long run, but could pass as a dirty EV+ move for certain scenarios in medium term. It's best if that possibility is addressed on the protocol level, otherwise it will be used sooner or later.