On 09/26/2012 12:09 PM, *Dominique* wrote:
> Hi Nathan,
>
> Thanks for the note! Unfortunately it doesn't seem to answer any of our
> questions. We've been asking about objects, specifically, the ones
> mentioned in the text pointed to by the link you included in your
> response such as Containers and Communities. It would be really great if
> we could get some description of these objects, just to hold us over
> until your documentation comes up to speed. :-)
An everywhere container is, for example, this Mashable instance:
http://www.meetup.com/Mashable/
Within a container you have communities like this one for New York:
http://www.meetup.com/Mashable/New-York-NY/
And finally, an event within the community:
http://www.meetup.com/Mashable/New-York-NY/454852/
>
> And now you've opened another area of concern for me ;-)... if I'm
> looking at the "everywhere" API, what is this other platform, the "much
> larger API" of which you speak?
Meetup. For example, the New York Tech Meetup:
http://www.meetup.com/ny-tech
> Where is it's documentation?
Same place:
http://www.meetup.com/meetup_api/
All methods that are not marked as "everywhere" methods are for the
Meetup (groups) API. All everywhere methods start with /ew in the path.
> Should I
> instead be writing to that API since it's the one you say is documented
> and you're using?
It depends whether you want to work with Meetup Groups or Meetup
Everywhere. The primary difference is that every Meetup group is founded
and run by an organizer, and groups are independent; there is nothing
like the global container that Everywhere has. Also, organizers pay dues
to use the platform:
http://www.meetup.com/help/Does-it-cost-money-to-start-a-Meetup-Group
If you have more questions, I think the next best step would be to
explain what you are trying to build.
Nathan