André Cruz

@vasa-develop Yes we have bi-weekly progress calls, but we are figuring out the roadmap for the next quarters. They are in standby for now and we hope to resume them...

@vasa-develop in terms of replication provider per identity. This would be really hard to do, since each DID-method is doing it's own thing. Later on, having a data provider per...

@andreforsousa in short, this is what we have from OrbitDB: ``` // { buffered: 0, queued: 0, progress: 2, max: 5 } ``` Particularly, with `buffered`, `queued` and `progress` we...

Related: https://github.com/ipfs-shipyard/pm-idm/issues/222

Lets make a second iteration on this later down the road.

I think it doesn't necessarily requires it to be a class component, but rather a component that supports refs (functional components can forward refs). Neverthless, I agree. I have a...

Also, we should mention best practices, such as preferring `woff2` over `woff` or other any format.

At the moment `translate()(MyComponent)` doesn't work which is quite strange as I use currying as it seems to be what the community is doing (need to do `translate('')(MyComponent)`). Would you...

This would be awesome to have for the dweb summit workshop. At the moment, it takes over 10secs for discover other peers, even on the same LAN, which is unfortunate....

@mkg20001 I mean, it takes 10secs using the regular discovery. Using the rendezvous with a reduced interval would improve the discovery times.