Marin Kirkov

Hello and thanks for the fantastic boilerplate. I am using it for a starter point for my own project and currently testing with minikube locally. I will try to summarize...

Bump that's certainly an issue and seems related to: #8 Being able to store and retrieve the state from a persistence layer seems like the logical way to solve the...

@mszoek @DavidChisnall Speaking of Etoile there is something very visually appealing that makes it look different and sleek even nowadays. It just screams enterprise beauty in my eyes. Do you...

It's absolutely stunning stuff. I wish it could at least be ported as is in modern world. The same way I miss the good old Keramik theme from KDE 3....

Thank you @LucaPanofsky. Let's keep the discussion open in hope of some official position by Berty as well since they already have their TOS and Privacy policy in place. I...

https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/PUBSUB.md#ipfspubsubsubscribetopic-handler-options Strings are supported. Sticking to default CID v1 encoding also seems sane.

@tabcat I tried using it with a previously created database(not in js ipfs instance) and it never gets open. Noticed that the multihashes are different as well: When created from...

Thanks, I have inspected it with the CID inspector: https://cid.ipfs.io/#zdpuAsm8HoFigBNechuWaUGDgcVR3LyPbZ24BbFYsojd5TvuP But when I try to open the content via the IPFS-desktop it doesn't show up. It's weird indeed will need...

> You bring up an excellent point about opening addresses that use different encoding! I believe how our discovery system works currently they will never find each other! We need...

https://docs.ipfs.io/concepts/content-addressing/#cid-inspector > The default for CIDv1 is the case-insensitive base32 > not quite, its that only peers using the same base encoding for the address will find each other. Is...