When I get the time I want to port my timeblocking calendar (viscal) to egui + nostr (nip52). The standard calendar sync protocol CalDAV is a truly awful.

Syncing calendar events to nostr would be much more pleasant and easier to work with. Can't wait to see more nostr calendar software.

Reply to this note

Please Login to reply.

Discussion

Are you sure the calendar's days are numbered

I want all of the text-based application data of all the apps i use in nostr. just imagine the possibilties.

Will, put the laptop down, it was a dad joke 🤣🤦

I want to learn more about this. Can you share resources?

on what in particular ?

How can I do this too

Are you following the discussion of relays getting too big and too costly and thus shutting down?

It seems inevitable to me that relays will eventually only keep 30 days of events per user (even that would be 12TB per day if Nostr had Twitter scale, so even that is not feasible for anyone but industrial relay operators).

So it would seem that Nostr is not suitable for apps where events should be stored reliably for a long time.

i think you’re conflating nostr with public relays. You can just pay a relay to store your notes long term, run your own local relay for backup. Not to mention any damus client has a copy of all your data, which could be backed up to the cloud or synced to other damus clients between your devices

At least CalDAV supports recurring events, and timezones

I don’t see why this couldn’t be supported on nostr

NIP 52 has timezones

Do nostr calendars still use the iCalendar format?

no

it seems that will kill all network effects with existing calendar software 😕

You could easily convert between formats. Generate ical from notes, and vice versa

Definitely. I guess what I'm wondering is what advantages a nostr-specific cal format gives us. e.g. starting from scratch has meant we don't get recurring events right away (something iCalendar already supports): https://github.com/nostr-protocol/nips/blob/master/52.md#recurring-calendar-events

Easier to read and write calendar data. It’s extremely painful to run a calendar server and get it to work between apple and google devices. Also having data in nostr so i can easily sync and display my timeblocks and calendar events between all my nostr apps

cal.com

sorry if this seems pedantic, but caldav server != icalendar

i don’t have any particular issues with the ical format, you could imagine just stuffing ical events into notes or something