Continuing from xxB-2024-003: Haven Browser Extension Implementation - #16 by m.f since it’s more appropriate to ask in this topic: I’ve never understood (since the first xxDK) why demos cannot load a Haven identity file and join a channel.
How is this Related to the browser extension? Well, I haven’t used it but I’ve seen a video demo and was thinking it might be possible to:
a) Have an ID store (could be independent from Haven cache)
b) Then, if an API is exposed, one could auth to the extension which would handle “load & login”. Maybe there’s a version of that already, but in the video a new Haven identity was created so I don’t know.
c) Similarly to Web wallets, one could even store a dict of identities and channels, to have everything in one place. Then, finally, apps like this simpler chat app (not necessarily Haven) could use the extension as a kind of Web wallet, where Haven identity is like wallet address, and channels are like fungible assets… In cases like this, convenience is required, so the ability to load 1 identity and 1 channel would be sufficient. Load, message, unload.
With this approach it would be possible to use cMixx for comms and notification from apps (automation) which is a big pain point with Haven.