Earlier quoted context omitted.
Would be nice if you use your experience and financial stability of a Google job in order to build a better open-source protocol. Just like when ZX2C4 decided he's fed up with OpenVPN and went to create Wireguard this might be your moment to shine. IMO the quality of software is only pushed forward by motivated individuals with the right skillset.
The JMAP for Calendars RFC [1] is soon to get published by IETF. Disclaimer: I work for Fastmail and am the co-author of RFC 8984 [2] which defines the calendar event data model used in JMAP. [1] https://www.ietf.org/archive/id/draft-ietf-jmap-calendars-22... [2] https://www.rfc-editor.org/rfc/rfc8984.html
Owning my own data, part 1: Integrating a self-hosted calendar solution
111–120 of 157 posts
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#112Earlier quoted context omitted.
I worked on the CalDAV client that’s in every Apple product. I agree, the protocol sucks. But we also had a ton of trouble handling Exchange and Google’s non-compliant CalDAV server, which all the users blamed us for. Now that I work at Google I can see that gCal apps use an entirely different protocol.
Would be nice if you use your experience and financial stability of a Google job in order to build a better open-source protocol. Just like when ZX2C4 decided he's fed up with OpenVPN and went to create Wireguard this might be your moment to shine. IMO the quality of software is only pushed forward by motivated individuals with the right skillset.
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#113I know this is not what people want to hear, but your data will never be safer than it is in the cloud. No setup you can dream up at home with in a reasonable budget will ever come close to the resilience and redundancy you have in the cloud. Ownership is not about storing everything at home (or well, it's part of it), but having control over your data, which you can easily have while at the same time using the conve…
I can't help but feel on-device storage is still safer than cloud storage. Sure, can use cryptomator or similar to encrypt on cloud, but that's same with local. Only with cloud you're opening up a much bigger attack vector space than having it on-device/"at home". Cloud definitely gives better resiliency and redundancy, but data replication is also something to be cautious with if privacy is a concern.
The moment you start opening ports you're no longer remotely safe. Cloud providers have dedicated staff monitoring services (or monitoring systems monitoring services) for anomalies, as well as people monitoring their networks. These same people will also know in advance when a new patch is coming for some 0-day exploit that might leave them vulnerable.
Compared to your setup at home, where you will patch it "eventually" (at the earliest when you get home from work), and you won't know if you're the target of an attack until your server gives up.
Not to mention the risk of losing other data. The LastPass leak a couple of years ago was made possible by attackers gaining access to an unpatched Plex server on a developers home network, from which they could gain access to his work laptop. LastPass had questionable security practices sure, but the validity of the attack still stands.
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#114I know this is not what people want to hear, but your data will never be safer than it is in the cloud. No setup you can dream up at home with in a reasonable budget will ever come close to the resilience and redundancy you have in the cloud. Ownership is not about storing everything at home (or well, it's part of it), but having control over your data, which you can easily have while at the same time using the conve…
> Ownership is not about storing everything at home (or well, it's part of it), but having control over your data, which you can easily have while at the same time using the convenience that the cloud offers. Ownership is not just about r/w control of your data but also over what software gets access to it and what that software does. Not just about privacy, but knowing the process and being able to alter it to your…
If it does, I assume you also roll your own network equipment. If you're worried about surveillance, know that you're far more likely to be targeted at the network port than at your data.
As for the process, the cloud (for storing data) is nothing more than a remote fileshare that someone else keeps running. If you have an up to date copy of your data you can change the process any way you like.
Servers are not free, nor are they fire and forget. Once you setup a server and decide to open it to the internet, you become a target, and you will be found. There are bots scouring the entire ip range of every residential IP network looking for juicy targets, and when they find something they record it for later use. Then when some new 0-day is found for service X that you're running, they don't need to scan, they can just lookup in their database an exploit right away.
I'm not against self hosting, and god knows I've been doing it for decades, but it is very rarely worth the hassle compared to the gains. The power cost alone of running a server is more than the equivalent cost of storing it in the cloud (assuming we're not talking media servers, but regular user created data).
The worst argument I usually see is people self hosting mail for private, completely oblivious to the fact that there are usually 2+ people in a mail thread, and something 68% of the worlds population runs on Google/Microsoft/Apple/whatever, so while you may keep your emails private, if they're targeted for being scanned they have already been so.
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#115I know I will probably get pushback over this, but CalDAV sucks . People say that it's great and that it's easy; yet if that were true there would be way more self-hosted CalDAV solutions out there and they would be far more ergonomic than what's available. I was not impressed with Radicale. Because there's really only one calendar file I wanted to serve to myself, I tried implementing my own CalDAV server just for t…
It’s also a good story about the conflict between startups and open source, building products, and software development in general.
[1] http://www.dreamingincode.com/ ; https://en.m.wikipedia.org/wiki/Dreaming_in_Code
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#116Another CalDav server I can recommend is Radicale. It's written in python and designed in a pretty modular way, enabling authentication and authorization (and more) plugins. Data is saved in plain text files and I track/backup it using git. Over the time I've accumulated some interesting modifications: - Authentication runs with pam on the host system. - To enable sharing of calendars I run a periodic script symlinki…
Let us know when that blog post goes live… ;)
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#117Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#118Been thinking about this too. Citizenship application is asking for my travel for the past couple years. And I have no idea. Especially since in Europe a weekend getaway to another country is feasible. Some sort of long term tracking would have been really useful
Just write what you know: they won't be able to know where were you... ... but they will be able to know if you're lying to them because they are trained to read people.
Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#119Re: Owning my own data, part 1: Integrating a self-hosted calendar solution
#120I don't have the requirement of owning my data and I've solved this in a simpler way. 1. Create a shared family calendar 2. For things that need to block work calendar, invite my work email to the event.
Why would you expect anyone to be interested in this solution given the whole discussion is about self-hosting?