I read it and I am more confused.
My name, display name and nip05 all start with "pip", so I should reach 2 points. My WoT is definitely higher then the other Pip, yet he has the name
Discussion
your kind 0 metadata shows as this, and I just re-ran it against your listed relays
"profile": {
"name": "pippellia",
"nip05": null,
"lud16": "whitebat1",
partial match only applies to the name field, and demarcated by spaces... we wouldn't want "pip" to also occupy "pi" for example... but would want someones first name to hit if they used name as First Last
Partial matches do not count in the lud16/nip05's prefixes since those wouldn't have spaces... but neither your nip05 or lud16 are populated with "pip"
Since your name field is "pippellia" that's what you occupy
I had an issue with my profile being nuked. I've now restored it.
I had pip@vertexlab.io and Pip in the displayName. Do you use the displayName or just the name?
https://relay.orly.dev/ check out the "recovery" tab. ORLY does not delete replaceable or addressable events, and that UI lets you reinstate old versions if this happens.
this is a great feature.
it's even mentioned in NIP-01 but nobody seems to consider it a mandatory feature for NIP-01 compliance. IMO, it SHOULD be an OPTIONAL one and there should be a feature flag to signal it.
I agree it should be optional, but I don't like the flag thing because I might want to offer a paid service (like primal), so I store older versions only for my paying customers.
So a flag per relay doesn't make sense in this and many other case.
It should just be optional.
i think rugging users profile events should not be a chargeable offense.
er, what i mean is, i don't think it should be optional. can we trust nostr clients more now than before everyone started vibe coding? no, it should be MUST not SHOULD. or you are not NIP-01 compliant and that should be avoided.