Are NIP01, NIP65 messages to be seen as global or relay specific.

[dukeh3]

Imagine a user Alice, posting a NIP01 profile to a set of well known, "public" relays. And then she post a different profile to a set of more private relays. How shall Bob that has access to both the public relays and hence get the first event and the more private relays and also get the 2:nd event treat these to events? Should he store both profiles and use them in a contextual capacity, or should he discard the older event based on created_at value?

[mikedilger]

He should discard the older event based on the created_at value, because kind=0 user metadata is a replaceable event.

Which relay an event comes from is not material in almost all respects, unless you are operating a relay-centric application on top of nostr such as NIP-29 or anything that specifies a relay.

NIP-65 kind 10002 messages are definitely global and not relay-specific.

[dukeh3]

I am aware of the fact that kind=0 is a replaceable event. And yes NIP-29 is very much in scope for this question, so what you are saying is the all profiles, and events should be treated as if they where sent from the same place. So Alice can only have a separate profile for the private relay if she create a separate key for it?

[mikedilger]

That is my understanding. We can always invent new things if they are useful, but we should not reinterpret existing things in incompatible ways.

[vitorpamplona]

I agree with @mikedilger. There is no point on sustaining distinct kind 0s in separate relays. It will only create confusion.

[fiatjaf]

I think it would be very good to have different profiles in different relays. Not in the current world with the current microblogging clients, of course, these should probably not care and won't care. But a different type of client with a different use case might. NIP-29, for example, could make use of such niceties without hurting anyone.

[vitorpamplona]

Sure, but I assume at some point the outside kind 0 will leak to the nip 29 relay and vice versa. And then it will all be a mess and super confusing for the user.

If you want a different user profile per relay, we need to change the way we do profiles.

I frankly see no hope on reusing pubkeys between the "free" world and each of the nip 29 worlds.

We will have multiple keys per user. And that will be better for everyone. Things will never mix.

[dukeh3]

I have been thinking quite a lot about it, and after a few chats this is my current position. The ID:s should be seen as global, and hence the profile should be treated as global, if you want to have different profiles then I suggest that you have different keys (for now). In the future we might want to have community profiles, but then this has to be described in a NIP, so that the clients have a sporting chance to handle it. Also note, its fully possible to forward an KIND 0 event from one relay to another without the signers consent, and this is (for now) by design.

Separate profiles can be done by tagging them in a special way so that you can distinguish then from the "default" global profile.