Steven Allen

Ah, nevermind. The issue is browsers. localhost -> 127.0.0.1 and "localhost" is treated as a secure origin, even without TLS. If we used a non-localhost address, HTTPS websites wouldn't be...

> Well, no browser show localhost websites as secure: It's a little more complicated. * Firefox: * `localhost:*` * UI: Not marked as secure but not marked as insecure either....

We also need to do this for our: * caching blockstores. * Our datastores. * etc...

This is just internal; go-ipfs is internally comparing CIDs when it should be comparing multihashes. That is, when we receive a wantlist, we shouldn't take the CID into account when...

The only external part is "providing" blocks. The backwards-compatable fix would be for DHT nodes to ignore CID codecs when checking if they have any matching provider records but that's...

Note. CIDs on the network is totally fine and kind of useful (it means one always knows how to interpret a block as IPLD); we'll even need them for DAGSwap....

Ah. And that's where the backwards compat issue comes in. I wonder if we should fix this issue, have a short upgrade period, and then switch to base32 by default....

I have no idea where that might be; I'm just basing this off of what @diasdavid has been saying.

Unfortunately, this isn't entirely fixed. If I _add_ a new block, we check existing wantlists by CID, not multihash. Worse, fixing this is a bit tricky unless/until we change the...

So, an alternative is enable the "use-libc" feature by default in this crate: ```toml [features] default = ["use-libc"] use-libc = ["rustix/use-libc"] ``` However, this could potentially cause even more trouble...