Marcin Rataj

We've met yesterday and came up with next steps to always resolve CIDs over DNS and _have no TLS errors when current defaults/ED25519 keys are used_: (1) solve TLS problem...

@MichaelMure see https://github.com/ipfs/team-mgmt/pull/1159#discussion_r429208550 **Note:** it won't be needed for defaults, but will make it possible to load custom CIDs if someone has to use longer hashes for some reason.

I started working on the splitting logic in subdomains, expect PR soon. **Update:** https://github.com/ipfs/go-ipfs/pull/7358

Leveraging RFC4343 is a no-go – no browser support afaik.. FYSA I've talked with @Stebalien last week, and we are re-evaluating. None of us is happy with ramifications of splitting...

No, we need to solve this in a way that enables people to load all CIDs, no matter what gateway type is used. Right now, subdomains are limited to subset...

- we did solve ED25519 in this issue (see first comment) – keeping the label for discoverability - query parameter does not provide Origin isolation, and we already have [path...

@Winterhuman how you can fit sha512 in proposed CIDv2 and have no more than 63 characters? Are you suggesting using a different (weaker) hash like sha256 to point at the...

Sprite for filetype sounds very good, cuts down the number of requests/blocks. However obligatory sidenote: be very careful with reliance on "retrieve from CDN or third-party gateway". Mind that people...

@achingbrain FYSA to make this bit more formal, generated IPIP-0476 documenting why we need this: it includes the motivation from the PR (browser nodes needing lightweight peer discovery), the specification,...

Smells like something related to `Content-Type` and/or `Content-Disposition` header in HTTP response. They inform browser how to render content and what filename is used in "Save As". - https://specs.ipfs.tech/http-gateways/path-gateway/#cache-control-response-header -...