Hi guys! So, I have Proton Mail, and this also gives me the Calendar. I love that I have a encrypted private calendar, but it bothers me that it doesn’t play well with any other app, as it’s not officially a “calendar” to Android. This bothers me, because I use GrapheneOS, with mostly no Google services, and I’d like my Gadgetbridge-connected smartwatch to be able to display calendar events, since they’re not being shared with anyone else. But I can’t, because Proton Calendar isn’t really an Android Calendar. There’s a way in Proton to permanently share a link to your private calendar. In effect, it’s an up-to-date .ics file, that I believe needs to be checked/downloaded every time there’s an update. Is there a way to update this in Proton? Alternatively, I wouldn’t mind creating some caldav system that imported this, but not sure if there’s already any guide for it?

Thanks so much!

@iturnedintoanewt@lemm.ee
creator
link
fedilink
English
15M

Sure. But you should be able to decrypt it, so you can use your favored application, if so you choose. Or your favored OS. Which in my case is GrapheneOS. So I’m already in a kinda private environment. I can trust the internal OS not to talk to GOS. And I can trust my watch to do the same, because it’s locked completely thanks to Gadgetbridge. The official companion app only saw the watch in the initial pairing/key exchange, in a garbage separate profile that doesn’t hold any useful data, and it was removed immediately after. As you can see, my scenario is full data lockdown, and yet I can’t choose my favored app to use in my trusted zone.

@starlord@lemm.ee
link
fedilink
English
25M

You’re not wrong, it’s just about how Proton is built right now. It’s still a pretty young ecosystem.

I will menton that all of their apps (both from GP and F-Droid) work great on my OOTB Galaxy 21 and send all notifications (emails, calendar events, etc.) to my Samsung Gear 3 watch no issues.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 191 users / day
  • 419 users / week
  • 1.14K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.71K Posts
  • 74.6K Comments
  • Modlog