Change method to PATCH for events not organized by yourself

[eivindt]

This avoids 403 forbidden messages when dismissing notifications on events that you are not the organizer for.

Fixes #3

[eivindt]

This probably also fixes #572 and #554.

[kewisch]

Does this also work for non-primary calendars, i.e. use normal http methods for regular changes on those calendars? They have a slightly different organizer format.

[eivindt]

I'm not sure. It definitely does not fix all problems, at least I still have problems if I have a reminder for an event that's been deleted on the server as I haven't been able to find a way to force a full resync.

The existing sync mechanism seems insufficient as you won't get refreshed info for the deleted events, so they remain out of sync.

[Rohaq]

Another alternative would be to make the module return false for the ACL check in Thunderbird if we're not the event organiser - if that's possible, of course. Looking at the Thunderbird code, that should skip over any further checks that would throw errors, and just dismiss the item.

[EugenMayer]

Also fixes #673

Any way we move this forward? 6 months for this critical patch seems to be a lot. What can be done to support this effort?

[wt]

Does this have any relation to #224?

[MoralCode]

Does this have any relation to #224?

upon quick glance, i doubt it. that seems to be about the general architecture of the extension w.r.t the various available Thunderbird APIs

[wt]

I am asking because #781 also refers to #224 as a path to fix the problem. Apparently, using patch is also the key for that one. I am wondering if #224 is still progressing, and if that architecture change is needed to fix this issue.

[MoralCode]

patch is just an HTTP method. I don't think this would require any major architectural changes. The part of the code that sends the updated event to google may just be using the wrong method so it could easily be a pretty quick fix for someone who knows the codebase really well and has time.

Disclaimer: i dont know the codebase in detail. I also am no longer a gdata provider user since switching to proton calendar