You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The metadata service does not alter the images other than sanitization if / when needed. The images can vary from vector to bitmap, with different sizes and ratios. One way to deal with maybe caching and resizing the image on your end, with an intermediate service instead of consuming as a direct source.
At
https://ethfollow.xyz/
the social graph widget fire multiple requests for avatarI realize one request reached 4.9MB
https://metadata.ens.domains/mainnet/avatar/anett.eth
As there is already implementation for [NFT image] (https://metadata.ens.domains/docs#/paths/~1%7BnetworkName%7D~1%7BcontractAddress(0x%5Ba-fA-F0-9%5D%7B40%7D)%7D~1%7BtokenId%7D~1rasterize/get) to handle low resolution, should that be extended to avatar image endpoint too? (If we do not want to point to a ipfs gateway with such feature)
The text was updated successfully, but these errors were encountered: