Live data from Hacker News

Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

baak6.com

21–30 of 63 posts

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#22
post #16

Any experience interoping something like this with google calendar? I'd love to use something like this, but I can't fall back to having separate calendar apps for work and personal stuff.

I created Callibella for this: https://github.com/bjesus/callibella

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#23
post #16

Any experience interoping something like this with google calendar? I'd love to use something like this, but I can't fall back to having separate calendar apps for work and personal stuff.

The solution is vdirsync

Perhaps you mean vdirsyncer[1]?

[1]: https://github.com/pimutils/vdirsyncer

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#24
post #19

The challenge with self-hosting is maintenance. The more complexity and more dependencies, the more maintenance. I believe that’s why the author was avoiding NextCloud.

Yeah but are calendars and contacts that complex? Or rather, do they have to be complex? Never worked on such things myself, though I'd think the hardest part would be interoperability with the big boys

Nextcloud is pretty low maintenance in my experience, at least for a few users doing fairly normal things. I've been running it for about 1.5 years (calendar, tasks, documents) and haven't needed to do anything except bump versions.

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#25
post #19

The challenge with self-hosting is maintenance. The more complexity and more dependencies, the more maintenance. I believe that’s why the author was avoiding NextCloud.

Yeah but are calendars and contacts that complex? Or rather, do they have to be complex? Never worked on such things myself, though I'd think the hardest part would be interoperability with the big boys

It's no somuch that, as what's in the stack: OS+PHP+MySQL+Nginx+Other Dependencies.

How often do they need security patches or major version upgrades that might have breaking changes? How often will you need to replace the current stack with the Next Big Thing?

I've been self-hosting a blog for a while. At first, I used custom software, because blogging software didn't exist (I'm that old). I switched to Movable Type, but that project withered. I moved to Wordpress, but found I was spending more time running upgrades of the core and plugins then actually blogging.

I migrated to a static site generator, Jekyll, which seemed popular would solve the problem of security updates with dynamic code. My install broke multiple times as I changed laptops and Jekyll's dependency stack went through major version upgrades. Still, I was spending more time maintaining the stack then I wanted.

Now, there have been rumblings about the future of Jekyll as well. Maybe I should switch to a single-binary app like Zola to solve the dependency hell I've sometimes gotten into with Jekyll upgrades.

This is only the history of trying to self-host a personal blog from someone whose professional career has been web hosting in some form or another. Imagine also trying to self-host email, contacts, calendars a mastodon instance and other services as well.

We can still support a more diverse ecosystem of tech by not using the dominant providers and supporting companies which use open source software which people can self-host if they want to.

I support self-hosting, but the marriage to your own tech stack involves some significant work once the honeymoon is over.

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#28
post #7

An interesting alternative is Radicale [1]. Both are very lightweight. I mainly chose Radicale over Baïkal because it is written in Python. On the client side DAVx⁵ [2] do a good job. [1] https://radicale.org/v3.html [2] https://www.davx5.com/

How do you host your email? I figured it would be a pain to not have my contacts and email very tightly integrated, so I just keep it all with Fastmail.

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#29
post #9

Or use DecSync [0] and eliminate the need for any central server. [0]: https://github.com/39aldo39/DecSync

How I use DecSync for my calendar without any central server: Thunderbird (Linux) - Radicale+Radicale DecSync plugin (Linux/Systemd) - 'DecSync' Folder (Linux) - Syncthing (Linux) - Syncthing-fork (Android/F-droid) - 'DecSync' Folder (Android) - Decsync CC (Android/F-droid) - Simple Calendar Pro (Android/F-droid) Radicale runs only on localhost. Syncthing runs only on the local network. The synchronization only happe…

I would be super interested to read a more detailed how-to on this. I use the crap out of Syncthing (although on iOS -- my daily mobile driver-- it is fairly limited what you can do with it).

Re: Own your calendar and contacts with OpenBSD, Baïkal, and FOSS Android

#30

Earlier quoted context omitted.

How I use DecSync for my calendar without any central server: Thunderbird (Linux) - Radicale+Radicale DecSync plugin (Linux/Systemd) - 'DecSync' Folder (Linux) - Syncthing (Linux) - Syncthing-fork (Android/F-droid) - 'DecSync' Folder (Android) - Decsync CC (Android/F-droid) - Simple Calendar Pro (Android/F-droid) Radicale runs only on localhost. Syncthing runs only on the local network. The synchronization only happe…

I would be super interested to read a more detailed how-to on this. I use the crap out of Syncthing (although on iOS -- my daily mobile driver-- it is fairly limited what you can do with it).

I used syncthing until I switched to iOS and found it unworkable due to how bad the clients were for iOS.

Nextcloud is what I ended up using; you get file sync and contact/calendaring in one, and you can also use it to share files "externally" if need be, even flip on the chat module and use it to video-conference instead of zoom if you want.

I'm using sqlite as the backing database mostly because I'm a single user and don't put a ton of files into it. I also disabled every single module I didn't need. It was dog slow until I connected it to redis, which was a real game changer - near instant page loads and file sync. It is running on an ancient SATA SSD in a second-gen i5 laptop.

Post reply on HN