Plan to refactor peerpad to use peer-crdt.

[fritzy]

Starting a goal of a new peerpad by mid-June, using peer-crdt. There are some challenges.

https://github.com/ipfs/dynamic-data-and-capabilities/issues?q=is%3Aissue+is%3Aopen+label%3ACRDT

The challenges are:

peer-crdt performance

There's been some work on specific bugfixes for performance, but going forward, here is how we're tackling optimizations:
ipfs-shipyard/peer-crdt#7

Identity

There's been a lot discussion and research on identity. This is the approach we're going to take on it in the short term.
#3 (comment)

Past discussion and research

• Identity: Research ipfs-inactive/dynamic-data-and-capabilities#7 (of particular note https://hackmd.io/s/H17TwVqsz#)
• CRDT: identify authorship ipfs-inactive/dynamic-data-and-capabilities#12
  A custom signed type that respects ACL and identity for y.js ipfs-inactive/dynamic-data-and-capabilities#15

Current Development

• https://github.com/ipfs-shipyard/dapp-identity-api (needs to be converted to use DID format and verbs as of this writing)
• DID client for generating key-pairs, DIDs, and interacting with the service (if available) or working without, if offline.

ACL

ACL relies on getting identity right, and then have a main admin give permissions for other users or sessions to perform actions.

Disccusions

#6

RichText Type

Due to the ACL discussion, we may want to have a richtext variation with embedded ACL as well.

Rewriting/Refactoring peerpad-core

Once we have all of the pieces in place, it'll be time to start rebuilding peerpad-core. We can do this before all of the necessary optimizations are in place, and it'll simply improve with time.

Design

Design efforts have been underway to improve branding and UX.

Hardening

The idea is to have a new peerpad ready for the big conference this summer, so we'll want to start using it and abusing it in earnest once the first version is deployed. We should have time to make a very solid product!

[one000mph]

@fritzy sounds like DID and several other efforts mentioned here have been solved. Can you provide an update on this effort on monday?

[fritzy]

Identity management is done, although we need to finish the identity service. Eventually everything can be moved to the identity RFC using what we've done as the basis. https://github.com/ipfs-shipyard/peer-star/blob/rfc-identity/docs/rfc-identity.md

Permissions will be implemented using the current encryption key url sharing, since the document needs to be encrypted anyway.

Performance is much better than it used to be, although it is still an issue for peer-crdt. There are more optimizations in the works, but it is unclear how performant it will be by the end of July.

A new textarea binding is in the works for peer-crdt, and we should be finishing that in the next day or two, at which point we'll start rewriting peer-pad-core with these new components.

[one000mph]

@diasdavid here is the update about the status of the peer-pad refactor