nostr:nprofile1qqsqddupn4l3cl65wggcyehd009g0pwuatsfudh28f90vewx68vrylqprfmhxue69uhhyetvv9ujuem9w3skccne9e3k7mf0wccszenhwden5te0ve5kcar9wghxummnw3ezuamfdejj7mnsw43rzufkd43hywr5d3erxmp5va6hxvmnveh8wd3hxue8xdm6v9jnv6r3de3k6ae4wa4rydm9df6kgdthvduxvdm3xph8sdmyx5lkyun0v9jxxctnws7hgun4v5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7nznd8h

This is kinda similar to what you're doing. Can your tech stack adapt to calendar events? It obviously does credentials.

Reply to this note

Please Login to reply.

Discussion

Technically, easily done. It’s the actual domain I know nothing about. I’ll keep this requirement in my thinking cap. My approach would be to store private calendar events that could be rendered in the wallet. Could be useful for health appointments. Once I get all the generic infrastructure stuff nailed down, I will be focusing on health.

Yup. Any business NEEDS calendar compatibility. Most humans online need, too.

A private calendar is certainly a primary motivation, but being able to share Calendar events publicly or with specific people is also going to be necessary.