coyotespike

Thought I might chime in here. I found this library very helpful, and I'm a huge of re-frame. If you look at the source here, reagent.cljs, line 32 reads: `:on-select...

@bganglia Can you share the tool? As @ieee8023 mentions a discovery tool would also be helpful.

One worry with (2) is that IPFS documents sometimes take a long time to retrieve, and doing so for every entry could add significant overhead. For (3): Is this previous...

One approach is to change the [line here](https://github.com/orbitdb/ipfs-log/blob/d45fbc92d755ae12a18125b3cfd0e1bbeeda9120/src/entry.js#L56) (working off the `acl-refactor` branch): ``` const signature = await acl.sign(entry) entry.sig = signature entry.key = acl.getPublicSigningKey('hex') return entry ``` to ```...

@thiagodelgado111 pointed out [this XML signature format](https://www.w3.org/TR/xmldsig-core1/#sec-Overview), and the [JWT format](https://jwt.io/introduction/) seems relevant as well. Also, a signature is a hash, no? Hence perhaps we could use the [multihash format](https://multiformats.io/multihash/),...

I believe you need to call `load()` on the database before you try to `get` something. In other words you need to tell it to replicate all the data, before...

@adrprado You may need to more directly connect the nodejs databases to the browser database. You can do this by putting the nodejs machines' IPFS multiaddress into the browser's IPFS...

See also orbitdb/orbit-db#314, an excellent blogpost. Because orbitDB is built on `js-ipfs`, and `js-ipfs` has problems swarming, you may need to hardcode the node.js IPFS id into the browser's IPFS...

This is a very cool idea. It sounds like you need a cluster that will coordinate to handle incoming and outgoing messages from the cloud, so similar to orbitdb/field-manual#83 in...

I think that's right! You just have to give your bootstrapper the database address to replicate, or a list of them. Hopefully we will open-source a pinning service soon.