nicholas 🧨
@nicholas
was going to post a mint mania but @zora and @warpcast are both bad at handling open graph tags zora fetches metadata too slowly and warpcast won’t update cached embeds it’s decided are Image Not Found. today for the first time the image fetched successfully before i posted, and then upon cast refresh warpcast decided to surface Image Not Found a lot of headache for a bunch of decentralization theater — two companies paying for all this to happen, but with high latency “decentralization”tech adding enough complexity to make simple open graph images not work 🤡 so i give up for now and will try again in the morning
3 replies
22 recasts
53 reactions
Garrett
@garrett
what’s the solution?
1 reply
0 recast
0 reaction
nicholas 🧨
@nicholas
without knowing the details of how these systems are built: zora should cache ipfs metadata and serve it on web2 infra at web2 speed. ipfs content addresses are no excuse for slow image serving. if the delays are introduced in the process that overlays usernames on the nft images, then that should be optimized warpcast should allow embed cache refresh on extant posts, unless there is a legitimate security concern — that website owners will maliciously mutate og tags AFTER unsuspecting users share their content. seems weird to take snapshot of rich media embeds at post time instead of fetching (or serving cached rich media) at view time
1 reply
0 recast
1 reaction
Garrett
@garrett
would love to hear more about this from @jacob or @v
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
> a lot of headache for a bunch of decentralization theater — two companies paying for all this to happen, but with high latency “decentralization”tech adding enough complexity to make simple open graph images not work 🤡 @nicholas what does this even mean? there is nothing decentralized about opengraph processing, possibly an edge case you're running into with scraping. if you can provide a repro example, we'll fix it
1 reply
0 recast
2 reactions
