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.

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

Help organizers understand what services are/are-not open wrt. event visibility #102

Open
waded opened this issue Sep 12, 2018 · 1 comment
Labels

Comments

@waded
Copy link
Member

waded commented Sep 12, 2018

It may be helpful for organizers to understand the pros/cons of using different calendar services (Facebook, Eventbrite, meetup.com, Google Calendar, BYO CMS that supports iCalendar feed, etc) to publish their events.

Recently, Facebook closed off API access to public page events, and I think we'll see meetup.com do something similar. Might also helpful to touch on what priority gemstate.io puts on different services, and what pros & cons are of each.

@waded
Copy link
Member Author

waded commented Sep 17, 2019

Note that some groups, like the Innovation Collective groups, like to use Facebook closed groups because they, to paraphrase a founder, want to keep people who can't show up (who aren't local) out of it. The downside is it tends to hide the existence of groups that are within it (e.g. people who know stuff about Bitcoin in Cd'A are all within the group, they don't meet outside it, but how would anyone outside Cd'A know that), but I suspect it will yield better results for smaller places since the entire motion's coordinated.

@waded waded added the schema label Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant