Obviously it makes sense for you to hold 1 version of your calendar. Multiple versions of a live document is bad.
Therefore… Ideally this calendar information would be hosted by a native client app. Ie it’s my information and it lives on my phone.
It lives in an app that can receive pull/push requests.
Having Google own your calendar, and data mine you is not great.
Not my entire calendar should be visible across nostr, but I should be able to create calendar timeslots and sell them over nostr through my bio.
This is the kind of new functionality that can be built into this kind of many-to-many social media. With hard money integration.
Real world services could be booked this way too. 🌎
eg a plumber could sell their time slots via a function like this.
Go to the pubkey profile of Mikey the East London Plumber, book his time for Tuesday morning. Pay the deposit in sats, give your address. Get the calendar reminder with location, time, description, etc.
All done in nostr using LN.
⚡️ ⚡️
Thread collapsed
Good thinking but this calendar to be available at all times needs to be hosted either by relays or in another server. Hence you don’t really need Nostr to do this.
Best thing I can think of atm is a special note that turns into a widget that you can pin on top of your profile. But we would need to develop a NIP and an API standard for that.
Maybe a bio URL field is the way to go?
The URL should point at a bunch of invoices that represent time slots, the invoices have some kind of API that allows them to drive actions if the invoice is fulfilled; eg create calendar session, initiate order fulfilment?
That’s much more versatile and is essentially a merchant feature for every pubkey!
Thread collapsed
Thread collapsed
