[gumby]

I think you have it slightly backwards (or should).

There's an open standard, icalendar (https://icalendar.org/) which represents calendar entries. Invitations you get in the mail come this format too. The easiest way for your map, address book, reminders etc to integrate is just to talk to your calendar server. The apps need not know about each other at all.

Google and microsoft of course may do some non-standard futzing around within their proprietary stacks: you can often see these problems when you try to connect to something outside their silos, though in my experience the standards integration in google calendaring is pretty good (especially when compared to their mail system). It's been a few years since I had to interface with Exchange calendaring but back then it...wasn't good.

So in any case there's no reason you couldn't write a small service that spoke ical over the network and this plain text calendar's format locally. Then it would appear normally in your partner's iphone, handle your kids' schools' calendars etc.

Whether it would be worth doing that is literally an exercise for the reader...but you'd get the same level of integration as you would with, say, Apple's icloud calendar services.

[hnlmorg]

That's fine in theory but honestly I have bigger fish to fry than rolling my own networked calendar. Much as I'm a big advocate for open source and open specs (even being an author and contributor to a few open source projects too), I have to use these proprietory systems for authentication and email at work anyway. So the convenience of using them for my calendar too far outweighs the cost of rolling my own solution.

This is one of those situations were worse is better.

[tedmiston]

> There's an open standard, icalendar (https://icalendar.org/) which represents calendar entries. Invitations you get in the mail come this format too. The easiest way for your map, address book, reminders etc to integrate is just to talk to your calendar server. The apps need not know about each other at all.

> Google and microsoft of course may do some non-standard futzing around within their proprietary stacks: you can often see these problems when you try to connect to something outside their silos, though in my experience the standards integration in google calendaring is pretty good (especially when compared to their mail system).

Yes, crossing the two is often still a hot mess.

The first paragraph sounds great in theory. The second paragraph sounds more like what happens in practice...

[gumby]

Well, the real problem is letting big companies get away with shitty implementations.

[tedmiston]

In any case... here we are, in a world where 95%+ of the people I share / use calendars with are via orgs owned by one of two big tech companies.

[kristiandupont]

>Google and microsoft of course may do some non-standard futzing around

Sadly, in this particular case, I can forgive them. The fact that iCalendar is the best we have is sad. There is a lot of room for improvement.

[link redacted]