Title: Workaround for lack of messaging API · Issue #15 · BostonPython/studygroup · GitHub
Open Graph Title: Workaround for lack of messaging API · Issue #15 · BostonPython/studygroup
X Title: Workaround for lack of messaging API · Issue #15 · BostonPython/studygroup
Description: Meetup's current API spec doesn't have an endpoint for messages (and a Google search result turns up a 404), and I've seen Google Groups conversations that talk about its removal. So, it seems like this project needs an alternative way t...
Open Graph Description: Meetup's current API spec doesn't have an endpoint for messages (and a Google search result turns up a 404), and I've seen Google Groups conversations that talk about its removal. So, it seems like...
X Description: Meetup's current API spec doesn't have an endpoint for messages (and a Google search result turns up a 404), and I've seen Google Groups conversations that talk about its removal. So, i...
Opengraph URL: https://github.com/BostonPython/studygroup/issues/15
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Workaround for lack of messaging API","articleBody":"[Meetup's current API spec](https://www.meetup.com/meetup_api/) doesn't have an endpoint for messages (and a [Google search result](http://www.meetup.com/meetup_api/docs/2/message/) turns up a 404), and I've seen Google Groups conversations that talk about its removal. So, it seems like this project needs an alternative way to message Members.\r\n\r\nOne possibility is asking for an email address when a Member joins a Group. That's a barrier to joining, though maybe surmountable with some help text. But, thinking about email got me thinking that a Group sounds like a moderated mailing list with a event scheduling component.\r\n\r\nSearching for \"meetup mailing list\" led me to Meetup's [Custom email list](http://www.meetup.com/help/article/868897/) feature. @nedbat, have you looked into that before? I wonder if StudyGroup could be a wrapper around that feature. The actual management of lists would have to be done in the desktop web interface, but the StudyGroup interface could streamline the proposal and joining process.","author":{"url":"https://github.com/bhrutledge","@type":"Person","name":"bhrutledge"},"datePublished":"2016-12-12T00:48:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/15/studygroup/issues/15"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:8e7fa134-0324-e7eb-8d3d-f3d81ddaf9dc |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D546:15720B:5D2A3D8:7ED53FA:6978417F |
| html-safe-nonce | 9e411cd49aeabe37150f71d620b221fd5993685f5d3b27be0ef4af4418380588 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJENTQ2OjE1NzIwQjo1RDJBM0Q4OjdFRDUzRkE6Njk3ODQxN0YiLCJ2aXNpdG9yX2lkIjoiNjQ2OTUwNzc1Nzk3MDU3MTY0NyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | b3ba18b2f9c707f9646cb8b2fbd7ea098a27e42625dbf112bc5fbf6c0ae0e74f |
| hovercard-subject-tag | issue:194870415 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/BostonPython/studygroup/15/issue_layout |
| twitter:image | https://opengraph.githubassets.com/78388fc29ddda1629d1c991f1913834542da10ccfa5c725bd5755dd8da824e15/BostonPython/studygroup/issues/15 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/78388fc29ddda1629d1c991f1913834542da10ccfa5c725bd5755dd8da824e15/BostonPython/studygroup/issues/15 |
| og:image:alt | Meetup's current API spec doesn't have an endpoint for messages (and a Google search result turns up a 404), and I've seen Google Groups conversations that talk about its removal. So, it seems like... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | bhrutledge |
| hostname | github.com |
| expected-hostname | github.com |
| None | 2981c597c945c1d90ac6fa355ce7929b2f413dfe7872ca5c435ee53a24a1de50 |
| turbo-cache-control | no-preview |
| go-import | github.com/BostonPython/studygroup git https://github.com/BostonPython/studygroup.git |
| octolytics-dimension-user_id | 5473307 |
| octolytics-dimension-user_login | BostonPython |
| octolytics-dimension-repository_id | 16872134 |
| octolytics-dimension-repository_nwo | BostonPython/studygroup |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 16872134 |
| octolytics-dimension-repository_network_root_nwo | BostonPython/studygroup |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 520b65a872113b919c1bbdb03834a50af15859fd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width