This database collection is queried along with events_current_processed to get event data. This could result in duplicate events but in practice doesn't really for some reason (I guess people can't be troubled to put the same data in two places).
Awesome stuff, but this code needs to be cleaned haha.
TLDR:
facebook.js needs to be run periodically (and fixed) or you could just manually sign in and mark events as interested on all the date ranges.
a. facebook.js can be improved by searching other search terms along with "ucla" like "ucla acm" or "ucla sigma" etc.
facebook.js needs to run automatically 3 times a day or so somehow. Maybe we can call it with python wherever we call the other stuff 3 times per day...
a. If this doesn't work we can try converting to Selenium/beautifulsoup/pyppetteer some browser automation framework written in Python.
I'm not sure if my implementation to add events that occur multiple times is correct for all cases, it seems to work but idk worth reviewing.
Code needs to be revised for style and effeciency...
Kimeiga
commented
4 years ago
oml i have facebook events integrated into the backend.
facebook.js needs to be run periodically to mark events as interested on facebook.
Then fb2_* will query through the facebook account "Selim Alpay" (the fake Facebook account for Bmaps) and populate [https://mlab.com/databases/events/collections/events_facebook_processed]() with events (deletes and readds all).
This database collection is queried along with events_current_processed to get event data. This could result in duplicate events but in practice doesn't really for some reason (I guess people can't be troubled to put the same data in two places).
Awesome stuff, but this code needs to be cleaned haha.
TLDR:
...yea