Commits on Feb 16, 2020

1. Allow silos to not implement Listen …

   Although they will be in the minority, there is the chance that we may
   not support Listen flows on some silos.
   
   Therefore we can make sure that `social_user` keeps this in mind when
   rendering, and ignore the Listen-specific UI if unnecessary.

   

   jamietanna committed Feb 16, 2020
   Copy the full SHA

   260c36c View commit details

   Browse the repository at this point in the history

2. Add Bridgy support for Meetup.com …

   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/

   

   jamietanna committed Feb 16, 2020
   Copy the full SHA

   8d9fe02 View commit details

   Browse the repository at this point in the history