personas #63

Open
opened 2025-07-05 11:19:32 +12:00 by mikedilger · 3 comments
mikedilger commented 2025-07-05 11:19:32 +12:00 (Migrated from github.com)

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.

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.
dpc commented 2025-07-06 12:31:04 +12:00 (Migrated from github.com)

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.

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.
mikedilger commented 2025-07-06 12:37:09 +12:00 (Migrated from github.com)

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.

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.
dpc commented 2025-07-06 12:58:39 +12:00 (Migrated from github.com)

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.

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 kind and possible "auxiliary key", so things get indexed by kind, key.

> 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. If I understand right, something similar is done in Rostra: https://github.com/dpc/rostra/blob/cf0a383603cbe7d879da27fae74200ca6a02bbad/crates/rostra-core/src/event.rs#L142 The event header has both `kind` and possible "auxiliary key", so things get indexed by `kind, key`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mosaic/nostr-next#63
No description provided.