Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silo request: Meetup.com #873

Closed
jamietanna opened this issue May 30, 2019 · 1 comment
Closed

Silo request: Meetup.com #873

jamietanna opened this issue May 30, 2019 · 1 comment
Labels

Comments

@jamietanna
Copy link
Contributor

@jamietanna jamietanna commented May 30, 2019

It'd be really helpful to be able to POSSE to Meetup.com without needing to manually RSVP.

Meetup seems to have a really good API, we'd just need to hook it in (famous last words!)

@jamietanna
Copy link
Contributor Author

@jamietanna jamietanna commented Sep 29, 2019

FYI I'm playing around with this at IndieWebCamp Amsterdam today

Loading

jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 26, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 26, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 26, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 27, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 27, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 27, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 28, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
snarfed added a commit to snarfed/oauth-dropins that referenced this issue Dec 28, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to oauth-dropins.

We can do this by largely duplicating the code from github.py and
dropbox.py, amending a couple of things for the Meetup-specific flow.
jamietanna added a commit to jamietanna/granary that referenced this issue Dec 30, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to granary.

For now, all were adding is RSVP support, so we can't add that in the
Granary webapp, just the library.

Unfortunately we don't get a permalink / ID back from the RSVP endpoint,
so similar to the way that Granary's Facebook likes work, we create our
own "permalink".
jamietanna added a commit to jamietanna/granary that referenced this issue Dec 30, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to granary.

For now, all were adding is RSVP support, so we can't add that in the
Granary webapp, just the library.

Unfortunately we don't get a permalink / ID back from the RSVP endpoint,
so similar to the way that Granary's Facebook likes work, we create our
own "permalink".
snarfed added a commit to snarfed/granary that referenced this issue Dec 30, 2019
As part of snarfed/bridgy/issues/873 we want to add Meetup.com support
to Brid.gy.

Before we can do this, we need to onboard it to granary.

For now, all were adding is RSVP support, so we can't add that in the
Granary webapp, just the library.

Unfortunately we don't get a permalink / ID back from the RSVP endpoint,
so similar to the way that Granary's Facebook likes work, we create our
own "permalink".
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 8, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 8, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 8, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
snarfed added a commit to snarfed/granary that referenced this issue Jan 8, 2020
As part of snarfed/bridgy/issues/873, we need to implement a couple of
missing methods for Brid.gy to correctly determine the actor in use.
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 15, 2020
As part of snarfed#873, we want to add support for RSVPing to events on
Meetup.com via Bridgy.

Meetup.com is the first silo that doesn't support Listen, so we need to
handle it a little differently to other silos, ignoring anything Listen
related, and when performing the initial Authorization flow from the
home page, we use the Publish OAuth2 scopes, not Listen.

As noted in [0], we can only have one `redirect_uri` for Meetup.com's
OAuth2 clients, so we can use `https://brid.gy/meetup/` as the prefix,
and then it will allow any matches under that path.

Closes snarfed#873.

[0]: https://www.jvt.me/posts/2020/02/15/meetup-api-multiple-redirect-uris/
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 15, 2020
As part of snarfed#873, we want to add support for RSVPing to events on
Meetup.com via Bridgy.

Meetup.com is the first silo that doesn't support Listen, so we need to
handle it a little differently to other silos, ignoring anything Listen
related, and when performing the initial Authorization flow from the
home page, we use the Publish OAuth2 scopes, not Listen.

As noted in [0], we can only have one `redirect_uri` for Meetup.com's
OAuth2 clients, so we can use `https://brid.gy/meetup/` as the prefix,
and then it will allow any matches under that path.

Closes snarfed#873.

[0]: https://www.jvt.me/posts/2020/02/15/meetup-api-multiple-redirect-uris/
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 16, 2020
As part of snarfed#873, we want to add support for RSVPing to events on
Meetup.com via Bridgy.

Meetup.com is the first silo that doesn't support Listen, so we need to
handle it a little differently to other silos, ignoring anything Listen
related, and when performing the initial Authorization flow from the
home page, we use the Publish OAuth2 scopes, not Listen.

As noted in [0], we can only have one `redirect_uri` for Meetup.com's
OAuth2 clients, so we can use `https://brid.gy/meetup/` as the prefix,
and then it will allow any matches under that path.

Note that we need to mangle the rendering of the CSS for the Meetup user
page, as we don't support Listen, so want to full-screen the rendering
of the Publish UI.

Closes snarfed#873.

[0]: https://www.jvt.me/posts/2020/02/15/meetup-api-multiple-redirect-uris/
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 16, 2020
As part of snarfed#873, we want to add support for RSVPing to events on
Meetup.com via Bridgy.

Meetup.com is the first silo that doesn't support Listen, so we need to
handle it a little differently to other silos, ignoring anything Listen
related, and when performing the initial Authorization flow from the
home page, we use the Publish OAuth2 scopes, not Listen.

As noted in [0], we can only have one `redirect_uri` for Meetup.com's
OAuth2 clients, so we can use `https://brid.gy/meetup/` as the prefix,
and then it will allow any matches under that path.

As we don't support listen on Meetup, we need to make sure that
`CAN_LISTEN` is advertised as such.

Closes snarfed#873.

[0]: https://www.jvt.me/posts/2020/02/15/meetup-api-multiple-redirect-uris/
@snarfed snarfed closed this in #906 Feb 16, 2020
snarfed added a commit that referenced this issue Feb 16, 2020
As part of #873, we want to add support for RSVPing to events on
Meetup.com via Bridgy.

Meetup.com is the first silo that doesn't support Listen, so we need to
handle it a little differently to other silos, ignoring anything Listen
related, and when performing the initial Authorization flow from the
home page, we use the Publish OAuth2 scopes, not Listen.

As noted in [0], we can only have one `redirect_uri` for Meetup.com's
OAuth2 clients, so we can use `https://brid.gy/meetup/` as the prefix,
and then it will allow any matches under that path.

As we don't support listen on Meetup, we need to make sure that
`CAN_LISTEN` is advertised as such.

Closes #873.

[0]: https://www.jvt.me/posts/2020/02/15/meetup-api-multiple-redirect-uris/
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 17, 2020
If we don't request `PUBLISH_SCOPES` on the initial login, you then have
to go through the Publish authorization flow before RSVPing to an event,
otherwise you'll receive 400s with `insufficient_scope`.

This isn't the nicest UX, so we should instead request the
`PUBLISH_SCOPES` up-front, as we don't support Listen, anyway.

Follow-up to snarfed#873.
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 17, 2020
If we don't request `PUBLISH_SCOPES` on the initial login, you then have
to go through the Publish authorization flow before RSVPing to an event,
otherwise you'll receive 400s with `insufficient_scope`.

This isn't the nicest UX, so we should instead request the
`PUBLISH_SCOPES` up-front, as we don't support Listen, anyway.

Follow-up to snarfed#873.
snarfed added a commit that referenced this issue Feb 17, 2020
If we don't request `PUBLISH_SCOPES` on the initial login, you then have
to go through the Publish authorization flow before RSVPing to an event,
otherwise you'll receive 400s with `insufficient_scope`.

This isn't the nicest UX, so we should instead request the
`PUBLISH_SCOPES` up-front, as we don't support Listen, anyway.

Follow-up to #873.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants