Radicale vs. Nextcloud: Self-Hosting Wars Erupt Over Calendar Control
The focus is exclusively on ditching major cloud providers for self-managed calendar systems, primarily using open standards like CalDAV/CardDAV.
People are sharply divided between polish and control. Some users, like cecilkorik, push Nextcloud and Thunderbird as viable escape routes. Others push for the technical deep end, citing Radicale and Baikal for reliable, non-Google setups. There is audible frustration, exemplified by mehappening, who questions Nextcloud's maintenance overhead, favoring Radicale's perceived simplicity. Even radical thinkers, like those citing calcurse, suggest reverting to plaintext files when digital complexity overwhelms.
The weight of opinion points toward technical self-sufficiency. While commercial polish attracts some, the concrete support lies with open-source, self-hosted protocols. The fault line is clear: the willingness to endure high initial setup complexity versus the perceived security risk of convenience.
Key Points
Prioritizing vendor independence via CalDAV/CardDAV.
The overarching goal is maintaining data sovereignty, citing protocols as the core requirement.
Nextcloud maintenance burden is a point of failure.
mehappening explicitly expressed frustration with Nextcloud's maintenance demands, suggesting alternatives.
Radicale is favored for its balance of privacy and deployability.
Multiple mentions support Radicale, with Opisek noting its utility for personal hosting.
Low-tech/scripting solutions offer an escape from digital complexity.
An outlier user suggested plaintext files or TUI calendars (calcurse) when digital systems prove too complex.
Specific reliable stacks include Baikal and DAVx5 on Android.
airikr called the Baikal/DAVx5 combination 'very reliable, long-term'.
Source Discussions (4)
This report was synthesized from the following Lemmy discussions, ranked by community score.