How come this hasn't been worked on in three years?

I'm finding the lack of integration of the use of aliases with the calendar is ridiculous! Does this need to have thousands of upvotes to be added onto the roadmap?

When I subscribe to my external calendar like Office 365, I run into a ton of timezone issues when viewing that calendar in Proton Calendar. This wouldn't matter nearly as much if I could forward the original event invitation to my Proton account... I wouldn't have to bother subscribing to external calendars at all.

since one genius user pointed out "this is like 5 lines of code removal", and since proton is opensource, i decided to poke around and see for myself.
spoiler alert: its not 5 lines of code removal.
this is what i find in ExtraEvents.test.tsx in the ProtonMail WebClients repo:
it('should not be possible to accept party crasher events when the mail is coming from SimpleLogin')
this means that the above functionality is as designed, but whats strange is that
it('should be possible to accept the event when the attendee is a party crasher and the organizer is external')
so as long as your event is not fwd through SimpleLogin and is not a ProtonCalendar event, you should usually have the ability to RSVP and thus add this to your proton calendar.
my question is why is this distinction drawn? @ProtonMail can you elaborate on the business logic that made this seemingly arbitrary rule?

I have been using Proton Mail for a while and am slowly moving out of the Google ecosystem. The calendar is the last piece, but I use a shared calendar with my wife so we need to be on the same platform. She's tentatively open to getting a Proton email, but if she can't use the calendar smoothly then she won't deal with it. This confusing and apparently pointless restriction adds a lot of friction to one of the most basic features of a calendar app, and while I am willing to put up with some inconvenience for better privacy, it will drive the rest of my family crazy. I hope this gets fixed so I can start using the calendar as my primary and get more of my family on the platform.

If you receive calendar invites through a randomly generated alias such as Apple's HideMyEmail of Apple One or SimpleLogin, you can send a response from that alias.

The current behavior is to accept the meeting invite sends a response from your default calendar, which reveals your private email address.

If this isn't possible, a good compromise might be to be able to add an an option to "Accept invite with no response." This would allow you to add the appointment to the Proton Calendar, but not reveal your private email address. If a response is desired, the user can go into the account and accept it from within the alias.

Calendar invites to an alias email (passmail) can't be accepted as Proton Calendar says that the email is not part of the recipients.

Feature: Allow to add calendar invites from the passmail aliases emails

This is a deal breaker if not implemented in the IOS app... I have people who continue to send invites to an old email address and it is really inconvenient that I can't just accept these invites.

Truly absurd that this isn't a feature. How does this possibly compromise privacy? Why would you possibly build in this restriction?

Hi guys it's uhmm 2023 please fix this already, it takes like 5 line of code removal.
Also google calendar allow this so why shouldn't you guys do the same?

Thank you kindly.

This is critical for interaction with my peers using aliases.

I don't understand why this restriction exists in the first place. It would make sense from the perspective of the invite-sender (not to let different people sign-up) but this is from the perspective of the calendar owner (who should be able to put whatever they want in their calendar).

If this is about sending attendance confirmations then perhaps it's enough to show a warning "Your email address is not in the participants list so we can't confirm your participation to the creator". The event ought to be added to your calendar without the need for confirmation.

It's obvious that there are in any case plenty of valid reasons for receiving invites with a different address to the one used for the calendar.

Very important to me.

Whenever I run into this I feel like the app is no longer my User Agent but is instead someone else's User Agent... let me add the events, please. I have the .ics, clearly this isn't any sort of information leak.

While I would love to have one email app where I could channel all my email, and one calendar app with all my events, the former would be nice to have, the latter is absolutely critical in order to be able to use Proton Calendar meaningfully in an environment when cooperating with people across multiple domains...

For public events, calendar invites will have been sent with participants' email addresses in BCC, so of course my email will not appear in the participants list (otherwise I would be able to see everyone else's emails, which is an obvious privacy issue).

There's really no reason to restrict accepting invites to only events where you're in the participants list like this.

for the love of all that is good FIX THIS! many times I will get invites for meetings I am not directly invited to and have to manually input them for no F'ing reason PROTON WTF!