Contact Birthdays calendar?

[sprnza]

Is it me not able to find, or there is no an option to have contacts birthdays to be aggregated in a separate or already existed calendar?

[Unrud]

This is not supported on the server-side by Radicale. Some clients support it. (e.g. Evolution or Birthday Adapter)

[dirdi]

I understand that Radicale does not support this, yet. However, it would be convenient to have such a feature on the server-side, since many clients do only support the creation of birthday events through a plugin, resulting in one to install a ton of plugins on different clients.

Maybe this bug report could be reopened, as a feature request?

Btw. sabredav for example supports this since late 2015.

[kerbless]

Quoting @dirdi, is it hard to implement?

[reitzig]

FWIW, Birthday Adapter doesn't seem to work on Android 14 (no updates since 2016) and Google Calendar does not show birthdays from contacts other than from Google accounts (doesn't work with DAVx5 contact accounts, anyway). So, an a current Android phone I'm sort of stuck short of installing a different calendar app (aCalender might work, as per davx5/faq).

Somehow, it seems neater to have radicale expose a CalDAV calender based on a(ny) contacts store.

@Unrud, would you be open to discussing this as a feature request? And/or reviewing a PR?

[jlbribeiro]

@reitzig Regarding Android calendar apps, Fossify Calendar has "Add contact birthdays" and "Add contact anniversaries" options; this only "displays them" in the app, it does not generate calendars available to other Android apps.

(Personally I coded something to auto-generate a birthday and anniversaries calendar based on my address book contacts, by leveraging the storage.hook mechanism, inspired by this comment; this allows using those calendars both system-wide and across devices (which feels like a more "consistent" experience). Don't think it's worth sharing since it makes some assumptions on deployment/environment + it's coded in Go (and not Python), but I might consider it.)

Would rather have this as part of Radicale itself.