hodlbod on Nostr: Drafted a quick NIP, I think a separate "aliases" kind might be a better way to ...

Drafted a quick NIP, I think a separate "aliases" kind might be a better way to handle this, since overloading profiles would result in overwriting all aliases with your global profile. Aliases being separate also allows us to avoid having to synchronize the entire profile across all versions.

https://github.com/nostr-protocol/nips/pull/1880

quoting nevent1q…v3h0

I am attempting to add "protected" profiles to flotilla, so that people can create an account, but only share their name with the groups they're a member of.

I implemented this today by adding a`-` tag to profiles and sending them to group relays (as well as fetching profiles from group relays and keeping track of which relay a given profile event came from). This allows for different profiles on different relays, but it breaks the "profile" page because without the context of which relay you're on, you don't know which profile to show if they diverge.

I suppose you could show your "global" profile, with some "aliases" below it. But then you're in the business of managing multiple profiles, which seems really annoying. Maybe an "alias" event kind would be an improvement? You could specify just a subset of profile data, and merge it into your global profile in particular contexts. This could be good for privacy, but also would just be a fun feature to have in groups.

I'm curious if anyone else has worked on this problem and come up with a good solution.