tyiu on Nostr: That would be cool. I think it could be pulled off with what exists in NIP-52. 1. ...
That would be cool. I think it could be pulled off with what exists in NIP-52.
1. Alex blocks off his unavailable times using kind 31923 time-based calendar events and/or kind 31925 RSVPs with the fb tag set to busy.
2. I query for Alex’s busy times to extrapolate his available times, and create a kind 31923 time-based calendar event for the appointment I want to schedule. Use the p tag to invite Alex.
3. Alex accepts the appointment request with a kind 31925 RSVP, with an additional e tag of the specific appointment.
4. If Alex doesn’t agree to the appointment request or wants to alter it (e.g. wants to limit the appointment to a specific duration), he could refrain from RSVPing to the calendar event sent his way, but rather create his own calendar event and tag the original requester.
We don’t have any kinds yet that allow someone to specify how long their desired appointment openings should go for or when their desired appointment openings should take place. But I’m sure we can make that happen.
peer (npub18zx…30pr) Does cal.com have any plans to integrate with Nostr? I know you weren’t in love with the NIP-52 spec.
Published at
2024-08-28 12:05:02Event JSON
{
"id": "4fb2d89cb92d18accd587a83d679872b8406a82f90a414d4059757d5e88cd5d4",
"pubkey": "2779f3d9f42c7dee17f0e6bcdcf89a8f9d592d19e3b1bbd27ef1cffd1a7f98d1",
"created_at": 1724846702,
"kind": 1,
"tags": [
[
"e",
"c2f3e199e8272dbf024bcb9a396089ba7214ad339b6a1436d43d42a88d43dc6d",
"",
"root"
],
[
"p",
"0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd"
],
[
"p",
"388c7fba25af828bc1020314b798e1cfb5e8431d451b244a9d48fd4a1ac0697c"
]
],
"content": "That would be cool. I think it could be pulled off with what exists in NIP-52.\n\n1. Alex blocks off his unavailable times using kind 31923 time-based calendar events and/or kind 31925 RSVPs with the fb tag set to busy.\n2. I query for Alex’s busy times to extrapolate his available times, and create a kind 31923 time-based calendar event for the appointment I want to schedule. Use the p tag to invite Alex.\n3. Alex accepts the appointment request with a kind 31925 RSVP, with an additional e tag of the specific appointment.\n4. If Alex doesn’t agree to the appointment request or wants to alter it (e.g. wants to limit the appointment to a specific duration), he could refrain from RSVPing to the calendar event sent his way, but rather create his own calendar event and tag the original requester.\n\nWe don’t have any kinds yet that allow someone to specify how long their desired appointment openings should go for or when their desired appointment openings should take place. But I’m sure we can make that happen.\n\nnostr:npub18zx8lw3947pghsgzqv2t0x8pe767sscag5djgj5afr755xkqd97qt530pr Does cal.com have any plans to integrate with Nostr? I know you weren’t in love with the NIP-52 spec.",
"sig": "e89a071f8a2262a000b8f927a05438fbbe5adcaa1e7dadb36afeaf590d04d045820e72a970b3f48b38ccee6303ad518e856dafaf61a8a2f4973d2715505c3fff"
}