We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At https://ethfollow.xyz/ the social graph widget fire multiple requests for avatar
https://ethfollow.xyz/
I realize one request reached 4.9MB https://metadata.ens.domains/mainnet/avatar/anett.eth
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:
No branches or pull requests
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.ethAs 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: