Agenda

Desktop Vault

Migration to new local vault

No limitation on number of local keys

Go to browser for setting up remote vault

Vault CRDT considerations

Client will detect conflict with version number, refetch and reapply changes

Additive pattern, data is not "lost" on conflict

No syncing for local vault

Key import+export only

Screen when adding a new local vault, confirm local keys will be added to it

Key merging workflow? hm://z6Mki8vmW6Kwmj5Gs8nj3uHW9pUdR1p1zhzVBNRYDarkBzZP brought the user story

We can implement this on the front end. Profile redirect + Agent cap

Main decision point: do we add the "author" field of a comment

We will continue to support this "after the fact change of comments"

A key merge has 3 blobs:

Agent cap from delegate -> "main account"

Agent cap from "main account" -> delegate

Profile redirect from delegate -> "main account"

Moderation code nightmare

Bug with feed not showing content from session keys

Web UI for leaving a site

Web notifs: email pre-validation required

Avoid double email

hm://z6MkgYR76i3w2Xc2fcvgFJWfYjsop6YwUonDhQx3AdLmQ4BQ will help hm://z6MkgisVMELvqnsCo3dYmtVpy8PiqPGMVwfAyBWFn84vebq4?v=bafy2bzaceciguevcgg7lacbo7fgix52zw3ewydimhmvbgyfzepmliapuaepam&l on this

Decision: use regular signing pattern with HM uid

Do not store pre-validation