Architecture sketch for encrypted storage (unlikely to come)

[marcelklehr]

• the server has multiple "hubs" each of which consists of a log which has multiple channels
• example channels are 'bookmarks', 'history', etc.
• the messages in the channels are encrypted CRDT operations
• devices write their changes to the log of the floccus hub on the server using
• A symmetric master key shared by all devices on that hub
  • (New devices could be added using PAKE: Desktop:addDevice -> Desktop:get a password -> Phone:enter password -> DH-like, forward secure, password-blinded key-exchange (PAKE) via 'meta' channel -> Desktop writes master key encrypted with PAKE session key to )

[e-alfred]

I am just curious about the things you would like to implement aside from bookmarks and history sync?

[marcelklehr]

Bookmarks and history are the most pressing ones for me. What would you like to see? I can imagine tab sync being useful, for example.

[e-alfred]

Yes, tab syncing would be nice as well. Maybe this list could help a bit with the features that would be useful: https://en.wikipedia.org/wiki/Comparison_of_browser_synchronizers#Syncable_Items

Form history, search engines, add-ons/extensions, preferences/settings would be really awesome, especially if they could be used across different browsers (probably very difficult for the latter two).

[marcelklehr]

Thanks for the useful list! Not all of that stuff is available through the WebExtension API, yet, though, so I'll see whether I'll get to those.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.