I used some other peoples work (like the django twitter app and d3 paths) and I need to give them credit. And ask if it is okay...?

We want to be able to trace multiple protests (and overlay them, hopefully). This app only follows a particular hashtag, and needs a lot of manual work. Ideal scenario would be to only have three steps: set hashtag, start engine, end engine (and these last two could maybe also be done automatically at some point, and maybe even the first!)

One decision that needs to be made is if this app is intended for a Daily Cal reporter or if it is meant to be a crowd-sourced tool. If the first, we can restrict by user. If the latter, we'll need to restrict the geolocation to be within some area around campus. Or if not that, some way to exclude bad tweets. Or maybe this won't ever become a problem.

Currently there's no auto-update, so a user has to refresh the webpage to get updates on the protest. A solution may be to refresh (just) the tweets and the path every minute or so, through some javascript delay function. Not sure if asynchronicity will let me.

Currently, I've had to keep a process running in my terminal to collect the tweets. We need some way to make sure that this happens on whatever host we use, instead of a personal machine. Will we need another dyno? Not sure.

(I think) somewhere along the line the tweet id gets rounded off due to some function using only certain bit numbers. The solution would be to treat it as a string throughout (maybe).