Jorropo

I'm surprised people would care about that, it seems like it's a client issue if they aren't using trustless but if someone needs it then fair we can have it.

> Would a git bisect run help to see which commit introduced the issue? Yes certainly, there are two features we suspect to be the culprit but dont know which...

> Would increasing the UID to something like 1099 make more sense to avoid this type of user issue? I think so but it seems like moving the problem away...

Other option: - Rewrite or machine translate the cryptoanalytic fix in pure Go. I guess it's mainly just doing arithmetic on byte buffers, this should be trivial to machine translate...

I think we could propose two options: We could give a webui CID and webui + geoip CID. Obviously, the webui + geoip CID would be a folder linking to...

@ppt93 I'm not sure how that an issue here.

@ppt93 the bitswap register only happen the first time when your node starts, for IPFS to find a node before bitswap register the notify you would need to find that...

This is surprisingly painfull thing to implement because right now this is an option to the DHT factory. We can't just call `dht.StartServer`. It's nothing an API change in `go-libp2p-kad-dht`...

@lidel > wiring up MinDHTServerUptime is most likely blocked until that work is done, and itself may require a bigger refactor of go-libp2p-kad-dht, as https://github.com/ipfs/kubo/issues/9045#issuecomment-1158829676. In reality this is far...

https://discord.com/channels/806902334369824788/847893063841349652/1003259317383868426 > ``` > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x1a37eb8] > > goroutine 576316133 [running]: > github.com/ipfs/go-unixfs/hamt.(Shard).childLinkType(0xc037cfc690?, 0xc00fc1e8f0?)...