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.

Sign up for GitHub

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

Jump to bottom

Silo request: Meetup.com #873

Closed
jamietanna opened this issue May 30, 2019 · 1 comment · Fixed by #906
Closed

Silo request: Meetup.com #873

jamietanna opened this issue May 30, 2019 · 1 comment · Fixed by #906
Labels
new silo

Comments

@jamietanna
Copy link
Contributor

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

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

jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 26, 2019
@jamietanna
Add support for Meetup.com
0802bb4 
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
@jamietanna
Add support for Meetup.com
a09c31a 
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
@jamietanna
Add support for Meetup.com
049c8d8 
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 jamietanna mentioned this issue Dec 26, 2019
Merged
jamietanna added a commit to jamietanna/oauth-dropins that referenced this issue Dec 27, 2019
@jamietanna
Add support for Meetup.com
be3921c 
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
@jamietanna
Add support for Meetup.com
bda4b13 
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
@jamietanna
Add support for Meetup.com
4c39e1b 
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
@jamietanna
Add support for Meetup.com
1be8ca0 
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 pushed a commit to snarfed/oauth-dropins that referenced this issue Dec 28, 2019
@jamietanna @snarfed
Add support for Meetup.com
e668fad 
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
@jamietanna
Add RSVP library support for Meetup.com
e5e8040 
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 jamietanna mentioned this issue Dec 30, 2019
Merged
jamietanna added a commit to jamietanna/granary that referenced this issue Dec 30, 2019
@jamietanna
Add RSVP library support for Meetup.com
f2392af 
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 pushed a commit to snarfed/granary that referenced this issue Dec 30, 2019
@jamietanna @snarfed
Add RSVP library support for Meetup.com
be802e4 
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
@jamietanna
Add missing user_to_actor method for Meetup
660a705 
As part of snarfed/bridgy/issues/873, we need to implement this method
for Brid.gy to correctly determine the actor in use.
@jamietanna jamietanna mentioned this issue Jan 7, 2020
Merged
jamietanna added a commit to jamietanna/granary that referenced this issue Jan 7, 2020
@jamietanna
Add missing user_to_actor method for Meetup
a94d0b1 
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
@jamietanna
Add missing user_to_actor method for Meetup
3a7c3c4 
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
@jamietanna
Add missing user_to_actor method for Meetup
3d76750 
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
@jamietanna
Add missing user_to_actor method for Meetup
4bd4b7d 
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
@jamietanna
Add missing Granary methods for Meetup
44603e0 
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
@jamietanna
Add missing Granary methods for Meetup
b49d69a 
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
@jamietanna
Add missing Granary methods for Meetup
dbcc930 
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
@jamietanna
Add missing Granary methods for Meetup
892be0c 
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
@jamietanna
Add missing Granary methods for Meetup
035877e 
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
@jamietanna
Add missing Granary methods for Meetup
27b3068 
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 pushed a commit to snarfed/granary that referenced this issue Jan 8, 2020
@jamietanna @snarfed
Add missing Granary methods for Meetup
45ff60a 
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 jamietanna mentioned this issue Jan 9, 2020
Merged
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 15, 2020
@jamietanna
Add Bridgy support for Meetup.com
2da01bf 
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 jamietanna mentioned this issue Feb 15, 2020
Merged
3 tasks
jamietanna added a commit to jamietanna/bridgy that referenced this issue Feb 15, 2020
@jamietanna
Add Bridgy support for Meetup.com
a4120f4 
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
@jamietanna
Add Bridgy support for Meetup.com
1929f2f 
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
@jamietanna
Add Bridgy support for Meetup.com
8d9fe02 
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 pushed a commit that referenced this issue Feb 16, 2020
@jamietanna @snarfed
Add Bridgy support for Meetup.com
26fe0a1 
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
@jamietanna
Fix: Request Publish scopes on sign-in
c585230 
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
@jamietanna
Fix: Request Publish scopes on sign-in
1ac93fb 
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 jamietanna mentioned this issue Feb 17, 2020
Merged
snarfed pushed a commit that referenced this issue Feb 17, 2020
@jamietanna @snarfed
Fix: Request Publish scopes on sign-in
fb6f30a 
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.
@ngm ngm mentioned this issue Mar 15, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new silo
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Bridgy support for Meetup.com jamietanna/bridgy
2 participants
@snarfed @jamietanna