Daniel Norman

I had a look at `@libp2p/crypto` dependency: https://github.com/ipfs/js-ipfs/blob/7a7e091c5d7110542ca7ab6eca1c0c9abb19e54b/packages/ipfs-core/package.json#L75 Since we use a caret range (`^`) for this dependency making the exact dependency installed by users non-deterministic, I suspect that there...

Couldn't find any changes that may have caused this in the hotfix range and version provided by @manboy-eth. Without a full reproduction, it's really hard determining the root cause here.

Thanks for sharing the proposal. If I'm not mistaken, I'd consider in the example you gave @iheanyi that `@unique` on `authorId` will also create an index, so it may not...

I'm experiencing the same problem with version `3.8.0` using the official helm chart. As @ahume reported, I'm also only seeing worker logs just print `Process exited with status 1` repeatedly.

Thanks for adding this clarification.

> The issue here is that the signature on IPNS records currently expires and random nodes won't be able to re-sign them as they'd need the associated private key. According...

> I think this could be an attack vector as a malicious node could publish a lot of signed records with infinite validity. They will accumulate on the DHT and...

This would remove a lot of artificial barriers to mainstream adoption of the IPLD stack, i.e.the `dag-cbor` and `dag-json` codecs. @bmann My guess is that this is also a challenge...

There's a linter that can do the heavy lifting of checking the health of the links and making sure that the awesome list adheres to the format: https://github.com/sindresorhus/awesome-lint#github-actions

Late to the party. > Fundamentally the behavior is still correct and aligned with the default Prisma naming for auto generated relation fields though. I think it would be sensible...