P2dif/mediumgood first issuehelp wantedkind/enhancementneed/community-inputtopic/design-visualtopic/gateway
仓库指标
- Star
- (13,906 star)
- PR 合并指标
- (平均合并 4天 2小时) (30 天内合并 28 个 PR)
描述
We've added a basic social sharing markup in https://github.com/ipfs/dir-index-html/pull/36#issuecomment-647819924 :
@lanzafame pointed me at this nice prior art from Github shows how UX can be improved by showing useful data via image:
In IPFS context, a cool improvement would be to provide image-per-CID with:
- QR code with shareable URL that could be scanned via phone
- prior art: share.ipfs.io has nice IPFS-branded QR codes (https://github.com/ipfs-shipyard/ipfs-share-files/pull/119), we could do something similar
- I like the idea of having a branded QR code, as it looks interesting even when not consumed.
QR code playground: https://zpao.github.io/qrcode.react/
URL of the icon: https://share.ipfs.io/favicon-32x32.png
- I like the idea of having a branded QR code, as it looks interesting even when not consumed.
- prior art: share.ipfs.io has nice IPFS-branded QR codes (https://github.com/ipfs-shipyard/ipfs-share-files/pull/119), we could do something similar
- CID breakdown (codec, hash)
- dag-pb stats (total size, number of blocks)
Hot take:
- If we implement image generation as an alternative response format named
share-img(as in, gateway response changing based on parameter?format=json|cbor|car|block|share-img) then we don't need to inline the data and don't need to deal with relative vs absolute vs cross-origin links (making this work on all gateway types without any additional configuration).