personas #63
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mosaic/nostr-next#63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I like what dpc did with having personas.
It seems to me once you have a single offline masterkey and many device keys, you can have separate cryptosystem keys, encryption keys, and persona keys. Dunno what @dpc did, this just comes to my mind as an elegant way to do it.
Personas are a high-level, product/application feature. In social media people just have different aspects to their life, e.g. they might have a political cause, but also personal or professional, or hobby aspects of them, and other people are often interested only in one (few), not all of them.
Multiple keys etc. are a deep low level feature/aspect.
Thanks for explaining that.
There are lots of ways to skin a cat.
I may introduce an indexable scoping tag instead of using subkeys, especially as when trying that it required a deeper tree of keys which I really didn't want.
At this layer (mosaic) I'm interested in being as un-opinionated as possible about how social media should work... social media apps ride on top and are opaque to me. But the idea of personas or scopes seems like a feature that multiple social media apps could share.
If I understand right, something similar is done in Rostra:
github.com/dpc/rostra@cf0a383603/crates/rostra-core/src/event.rs (L142)The event header has both
kindand possible "auxiliary key", so things get indexed bykind, key.