Kind3 has “petname” field for all followers. Petname’s “specd use case” has been replaced by NIP05.
> [petnames] alleviates the need for global human-readable names.
BUT there is another use case for petnames that NIP05 (and kind0) have not addressed, that of “persistent” human-readable names.
The solution is simple.
IF petname field is empty (which is usually the case) when client loads a Kind3 follow list THEN petname SHOULD be populated with the current “name” field from Kind0 profile data.
If petnames had an actual (not deprecated) use case then clients would be motivated to display it alongside profile name.
And there you have it.
Problem solved. 😂