Calendars
Calendars kept on Parahub and synced with the calendar app your phone or computer already has — iPhone and Mac, Android, Thunderbird. Share them with family, helpers and your bots, in full or as busy only. Nothing is ever public.
Connect a device
- 1Open Profile → Calendars and press «Connect a device». Calendars
- 2Name the device and copy its password. It is shown only once and Parahub keeps no copy. Each phone or computer gets its own, and you can revoke it at any time.
- 3Add the account in your calendar app, with your handle as the user name and that password. Your calendars and the ones shared with you appear by themselves.
Sharing
Open a calendar, press Share, choose the person and how much they see: read, read and write, or busy only.
Reminders are shared
The «Parahub» calendar
Once you connect a first device, a calendar named «Parahub» appears next to yours: the events you organize or said you will attend («maybe» shows as tentative) and your bookings — as the renter, or for the things you rent out. Parahub keeps it in step when times change or something is cancelled. Devices can read it but not change it, and you can share it — busy only to a bot, for example.
Every published event also has an «Add to calendar» button: a file for any calendar app, no account needed. If you have both, the event shows once, not twice.
In your webmail
The calendar page of your mailbox shows the calendars of your main profile by itself — your own, the ones shared with you and the «Parahub» calendar, which appears there with your first event or booking even if no device is connected. It is for looking: events are added and changed on your devices, and a change shows up within a minute.
The webmail reads each calendar with a password that can only read, and your calendars do not tell other mailboxes when you are busy. One switch under Profile → Calendars → Webmail turns it off. Calendars of a pseudonym are never shown there.
Private, but not end-to-end encrypted
There are no public calendar links, and a calendar nobody shared with you looks exactly like one that does not exist. The events themselves are stored on this node's server, as with any calendar server, so the node's operator could technically read them. Busy only is cut on the server: the person it is shared with never receives the details.