Pedro Teixeira

multiple tabs

3

When you have multiple tabs open, multiple IPFS nodes with the same id are opened, which causes havoc. Agreed steps (with @diasdavid) to solve this: * don't automatically start IPFS...

make peer-pad offline-first

3

In order to make peer-pad the blueprint for a offline-first application, we would need to: - [ ] use a service-worker to allow the peer-pad application to load when offline...

allow peer-pad to boot offline without an error

6

... and later on be able to find and connect to peers once the network allows.

support stream through IPFS daemon

6

One of the reasons why we were not able to use an IPFS daemon instead of an embedded js-ipfs node was because go-ipfs didn't allow for p2p streams. But go-ipfs...

use MFS instead of local store

3

Use MFS as storage for document state instead of local storage. This will allow us to decouple from local store and use, for instance, the IPFS daemon. (/cc @whyrusleeping)

offline app access

1

Leverage Service Workers to cache the app and make it load when you're offline. (/cc @whyrusleeping )

CI is failing

4

CI is failing on the tests for [this PR](https://github.com/ipfs-shipyard/peer-pad/pull/223): https://ci.ipfs.team/blue/organizations/jenkins/IPFS%20Shipyard%2Fpeer-pad/detail/PR-223/9/pipeline 

use peer-pad on the next DDC WG meeting

3

I'd like very much that we try to use peer-pad at [the next Dynamic Data and Capabilities Working group meeting](https://github.com/ipfs/dynamic-data-and-capabilities/issues/52). For that, I believe that we need to - [x]...

event loop lag

2

Experience when we tried using PeerPad today for the working group session. For some users, the browser event loop froze now and then, making the app irresponsive. Hint 1: crypto...

improve e2e load tests (continued)

1

Load tests need to be improved: - [ ] make configuration accessible and documented - [ ] run this on CI - [ ] minimize test run time (resort to...