Conversation

Also, and I'm not assuming bad faith, but did you not respect MM timeline because you just launched a token and wanting to create a lot of noise? I understand fully the privacy concerns, but MM did tell you they are actively working on it and gave you a timeline
Image
Image
2
12
What timeline ? 6+ months to fix an issue that can be solved with an explicit user prompt ? I can fix that that within one day. Also have a look at industry best practices for vulnerability disclosure, you won't find anything near that timeline.
1
8
Yeah, I think this issue has been widely known for a long time, so I don't think a disclosure period applies. Alex is right to call us out for not addressing it sooner. Starting work on it now. Thanks for the kick in the pants, and sorry we needed it.
Quote Tweet
Great reason for NFT viewers to not render centralized metadata by default (http tokenURI links). Only render content-addressable storage links like IPFS, or on-chain base64 embeds. Also creates a valuable forcing function for NFT creators to Do It Properly™. twitter.com/kurtybot/statu…
We're currently also taking some time to improve our team organization to ensure we maintain more ongoing effort to security related issues. We have lots of ways we want to improve user safety and privacy, and we need to be able to improve much more, much faster.
1
15
Show replies
This has been addressed, by the way. MetaMask no longer auto detects NFTs. I understand this tweet is being circulated by some people as proof of an outstanding issue. It is not.
1