Open tophboogie opened 7 years ago
I was tinkering with this a bit today, but I was having trouble on how we should store the info on who we have currently - what do you think about having an endpoint for 'who' (like to give the :keys for the link to the different collections)?
also the frontend is ready for this change I think, but there are two possible ways to do this:
setActivePerson
from the store<Link to='person/date....
I think I prefer the first one, but they will both cause the store to start asking the server for .../api/activePerson/words/:date...
@heinburger do you mean that a 'who' endpoint would provide a list of current people, and that list would be dynamically updated on the frontend? I like it. But if we really want to go full-auto we should have an array of twitter IDs on the backend and a script that dynamically creates a database for each person and does the scraping. I mean.. depends on how deep we want to go, I was thinking of just creating one or two manually and leaving things at that. At least for now. I want to launch this!
ok yeah, it could get kind of complex i guess - the manual way would be the best for now for sure, but perhaps we should keep it in mind
add more databases, api endpoints, and a frontend switch to toggle between different tweeters