No.
There are some starts, but... A calendar is absolutely essential for any business adoption.
Plus a standardized nostr-ized contact card like what you use currently but with an npub field.
Discussion
yup
Who is going to make the standard calendar event and contact format for nostr?
(I've always found it weird that calendar events and contact cards are mashed together, so I'd be OK if they were separated, but obviously interoperable.)
Maybe the file type could be .nce (nostr calendar event) and .nns (nostr npub share).
For the calendar event, functions should include time, date, descriptive text of the event, location, repetition suggestion (including all sensible options), public or private, if private which npubs can view/decrypt the event, which npub created the card at what time (and possibly where, physically, it was created) but also able to be created anonymously, etc.
Anyone want to poke at this?
Happen to remember who all has been working on the idea? Would love to pick at their mind to see what solutions they were/are planning towards it