[xyst]

It’s a nice toy, and appreciate the simple interface and not storing PII (ie, requiring name, address, …). But this seems like yet another calendar to me that I need to manage with _every_ relationship. Maybe I want to share a calendar with my SO, but what about my friend on the other side of town?

N+1 calendars I have to manage.

I would like to use my preferred calendar app and sync events I share to other people via CalDAV protocol.

It’s a standard protocol that’s existed for a long time now. [1,2]

Scheduling can be a bit janky especially with remote servers (ie, outlook…). But for the most part it works. Enter e-mail of person I want to share event with and person can see it in their preferred calendar.

Even updates work pretty well. It’s a shame we have all of these protocols but nobody bothers to use them and prefer their proprietary shit (ie, discord, telegram, signal, fb, ig, …)

Why must we continue to write “solutions” for already solved problems?

[1] https://en.m.wikipedia.org/wiki/CalDAV

[2] https://datatracker.ietf.org/doc/html/rfc4791

[martin_dd]

Hi, thanks for checking it out :)

Exactly like you said KittyCal started as a “toy” so I designed it as a private space for couples didn’t think much about integrating existing calendars. Also KittyCal intentionally gives up hourly scheduling so any event created would automatically become a full-day event if synced to external calendars.

CalDAV does seem interesting, will definitely look into it.

[pjerem]

CalDAV is cool but will be hard to integrate. It basically needs its own server.

However, if you want to continue in the « toy » direction, supporting ics format is a good option.

.ics files are calendar files : they may contain one or multiple events (like the whole calendar) and they are easy to generate in most programming languages.

What becomes interesting is that from any calendar app you can import this ics file (which is pretty unpractical in your case) but you can also subscribe to a calendar. For this you just have to provide an url to an .ics file that your backend may generate when requested (it’s just a text file).

Of course with this solution, you get a one way sync only, for classical two way sync you need CalDAV.

[martin_dd]

That's a good idea, thank you. I used to receive .ics files in email attachments all the time and the format seems easy to work with.