Comment by @defispartan • Hey

These are really valuable insights @lens/eduardmsmr @lens/jamesfinnerty @lens/punkess shared this concern as well in an LIP (https://github.com/lens-prot

Stats

Comments

@lens/defispartan Amazing points ser! I absolutely agree that it’s important to have these discussions openly so that devs can understand the needs of creators and users of the protocol. That’s my main focus when I go on some of my long rants! I’m not looking to criticize, but to improve! Wondering if it might be useful for the Lens team to look into creating a “best practices for publishing your collectible” guide with the resources currently available to us. For instance, is there something we could be doing better as creators to prepare our files? Is there a better app for posting image files compared to say audio files? Does embedded metadata in files help when publishing? Etc, etc. I’m going to dig into the GitHib links you posted to see if I can learn some new things! Thanks for the informative response! 💯🫶🏻
I am wondering if the lack of collection-level metadata could be the cause of this wallets behaviour. @lens/paulburke I know you expressed an opinion on this in the past. WDYT?
ok, I hated work today and it's past 2am here, so I might be a bit unstable. but what are you talking about? this topic is a concern for ages here. 1.) according to (former?) Lens devs (can't remember who said it. Jouni?), metadata is fine. it's frontend devs who mostly don't care. how difficult is it to prompt users to provide a title, a description, and give an artist name when they activate the collect module? Buttrfly is doing this to a certain extent. lack of support for collections is another topic. that's definitely on the protocol level. ok, I'm not a dev. I don't have a clue. 2.) what does this mean? I thought this web3 stuff was composable, permissionless, and some other buzzwords. no one needs to create new tools to integrate the rest of crypto on Lens. Lens has to play with the rest of crypto as well. I mean, there are two NFT standards, right? does it need more tooling? ok, I'm not a dev. clueless. you want everything on Lens while the real problem is that Lens is not working outside of it. 3.) what? once again, Buttrfly does this to a certain extent: mint NFTs on Zora and Sound (OP, Base, Zora), showcasing NFTs from Highlight. this is working already. @lens/paulburke is probably right that most wallets,... use the OpenSea API -> hidden on OpenSea, hidden everywhere else. and he's also right that in the beginning Lens NFTs were displayed on OS. oddly, when this topic was raised previously (one year ago or so), Bradley wrote that he (or whoever) had to talk to OS about it. did anyone actually talk to them? deleted various forms of the fine English word fuck in order to appear more stable than I probably am. good night!
These are also important questions for us. We distribute music in Lens and on other platforms. We are exposing our exclusivity a little bit, but it is still too early to lock ourselves into one platform. In WEB3 it's not like in WEB2 that if someone is on IG you can probably easily find them on FB. Just because we're on Lens doesn't mean someone from Farcaster will see here, we're on spozz.club and sound and we're preparing NFT for zora. It would be cool if your brand could be found in different worlds! Try different things :)