Request for comments on my pull request for NIP-52: Calendar Events. It’ll enable developers to build calendar apps, meetup apps, and conference apps upon the same primitives. It’s my first NIP — welcoming any and all feedback. Thanks in advance! nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p nostr:npub1ejxswthae3nkljavznmv66p9ahp4wmj4adux525htmsrff4qym9sz2t3tv nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1nxy56ame2gfnfj6fjylzxwq7r94phvgwt037mmvwr60qsqlaseksswlnxl
Left a bunch of comments
Looks good in general, I do wonder if there isn’t a more nostr-specific flow that we’re not seeing it; the current data model feels very much like porting the known calendar UX to nostr
That might be fine, but perhaps there’s something we are missing; have you implemented this already? I find that when I write the app I usually discover the nostr-enabled use cases more easily
Thanks! Yeah, I very much so used Google Calendar and the iCalendar spec as inspiration, so it’s possible there’s Nostr flows that I haven’t optimized for. I’m in the process of implementing against this proposal for the nostr:npub1c0nfstrlj0jy8kvl953v84hudwnpgad0zx709z0ey7nmjp0llegslzg243 web app via NDK, so we’ll see how this plays out.
