Meetup has removed API key support

[Aupajo]

What's happened?

Meetup has removed API keys in favour of an OAuth flow and removed support for version 2 of the API. To use the Server OAuth flow, you must have a paid Meetup Pro account.

This results in the following error message:

You are not authorized to make that request
API requests must be key-signed, oauth-signed, or accompanied by a key: https://www.meetup.com/meetup_api/docs/#authentication

All existing Almanack calendars with Meetup will have stopped working, as discovered in #35.

Immediate response

A new version of Almanack, 1.1.5, has been released that warns users about this change and points to this issue.

Technical issues

The changes needed to address this issue substantial. The integration will need to be rebuilt with OAuth in mind, with a custom browser-based authorization flow, which also means introducing persistence (to store OAuth tokens) and using the adopting the API version.

User-facing issues

Users would have to pay for a Meetup Pro account. Documentation would to provide instructions on how to set up an OAuth app on Meetup, which also appears to include a manual review process.

[Aupajo]

Support removed in #38 (v 1.2.0)

The current integration no longer works and the changes necessary to support a new integration (adding persistence and adding an OAuth flow with a setup UI) run counter to the intentional simplicity of this design. Coupled with the hostile requirement for a user to have a paid Meetup Pro account, I've decided to remove support for now. I may add it later, but due to the level of change it may surface as a (hypothetical) 2.0 feature.