Seems Amethyst shows both users (this one and the one above) NIP05 as valid.
Discussion
Interesting….
I didn’t think it would be Amethyst’s job to verify the NIP-05, but the actual issuer of the NIP-05.
Shouldn’t the issuer prevent this from happening?
It shouldn't be possible, to be fair. The JSON object contains a dictionary (or "map" in Java slang) from username to npub. I just entered two entries with the same key, which is not valid JSON. Anyhow, Amethyst seems to have a buggy implementation here 😅
For me it looks like this though:
