ANNOUNCE: deprecating /2/message

[Doug Tangren]

We would like to announce the official deprecation of the /2/message endpoint.

Meetup wishes to foster connections between its members and we realize part of that is ensuring that members are able to easily communicate with each other both offline as well as online.

Meetup as a platform has been transitioning away from a world where email was the only channel for enabling those kinds of online member to member interactions. Over the last year we introduced a new feature to our product called Messages which exists mostly outside of our members’ email inboxes. Deprecating and removing /2/message is part of that transition.

We will be not be turning off this service until the first week of June to allow for a period of transition in your apps. For the time being, we will not be providing an alternative API service until we feel like our members will be comfortable sharing their private message inboxes with public API clients.

Doug Tangren
Meetup Platform API Engineer

[Ben Hobbs]

Can I please suggest alternatives given that this will make it much more difficult to contact members...

Given this deprecation can I suggest lifting the limit before this shows using the Meetup messaging "Fast typing! We're impressed, but it's hard to keep up. Please wait a moment before starting a new conversation." proportionate to group size. I have a group of 15,000 and cannot use it without constant delays.

Also the manage list option could be accessed via API so lists created offline could be duplicated within the meetup contact options, or a meetup member search option when adding members to the lists (currently it only shows meetup names)

[Doug Tangren]

On Wed, Apr 15, 2015 at 4:01 PM, Ben Hobbs <bjho...@gmail.com> wrote:

Can I please suggest alternatives given that this will make it much more difficult to contact members...

Given this deprecation can I suggest lifting the limit before this shows using the Meetup messaging "Fast typing! We're impressed, but it's hard to keep up. Please wait a moment before starting a new conversation." proportionate to group size. I have a group of 15,000 and cannot use it without constant delays.

Also the manage list option could be accessed via API so lists created offline could be duplicated within the meetup contact options, or a meetup member search option when adding members to the lists (currently it only shows meetup names)

We currently don't have plans on opening up messages API's just yet until we feel our member's will be comfortable with the ability for 3rd party apps to have access to their private conversation data. The limits applied to messaging in our own apps and on meetup.com is in place to help prevent member's from spamming other members.

 

On Thursday, April 2, 2015 at 10:35:56 PM UTC+1, Doug Tangren wrote:

We would like to announce the official deprecation of the /2/message endpoint.

Meetup wishes to foster connections between its members and we realize part of that is ensuring that members are able to easily communicate with each other both offline as well as online.

Meetup as a platform has been transitioning away from a world where email was the only channel for enabling those kinds of online member to member interactions. Over the last year we introduced a new feature to our product called Messages which exists mostly outside of our members’ email inboxes. Deprecating and removing /2/message is part of that transition.

We will be not be turning off this service until the first week of June to allow for a period of transition in your apps. For the time being, we will not be providing an alternative API service until we feel like our members will be comfortable sharing their private message inboxes with public API clients.

Doug Tangren
Meetup Platform API Engineer

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ben Hobbs]

Yes I understand and approve of limiting spam. What is defined programmatically as spam though should be proportionate to group size when an organiser though, at least when contacting one's own members. If I contact 100 people of my 15000 members this is a small number, if my group size were 10 then clearly it'd be spam.

You received this message because you are subscribed to a topic in the Google Groups "Meetup API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meetup-api/43bFyyhBhL0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meetup-api+...@googlegroups.com.

[Justin Crook]

I'm with Benjamin on this one.

As an organiser I like to email new members individually to offer them welcome messages.

If I get a large following to a group in a small amount of time, this delays my email process greatly.. 

I also like to keep in contact with them individually to let them know they're important to the group. It's difficult when I keep getting delayed with this message.

Please lift it for organisers. If we were aspiring then I dare say we'd be reported at which point can be investigated and warned / terminated from using meet up. 

Members of groups also have the ability to leave a group if they're constantly being spammed by the organiser.

Thanks for reading team

Justin

[Jens]

Doug

why not allow users authenticated as one of the group's organizers to use some kind of messaging API. I don't think any organizer is interested in spamming their users - and if so, they would have an easier way through organizer messages.

I also agree that any messaging limits should be relative to the size of the groups / active members / number of meetups, etc.

Cheers,

Jens.