In the effort towards #360 we need the twitter lists to be a database entity. This means:
Creating a new "twitter list" table.
Removing the concept of "list names" and instead using primary keys.
Adding a foreign key relationship between twitter accounts and twitter lists
Changing twitter sync to load lists / list data from DB rather than constants
This might also mean changing the newsletter generation, but we can be a little more ugly there since that is being actively rewritten (and indeed this issue is just an attempt to split up the PRs associated with that rewrite).
In the effort towards #360 we need the twitter lists to be a database entity. This means:
This might also mean changing the newsletter generation, but we can be a little more ugly there since that is being actively rewritten (and indeed this issue is just an attempt to split up the PRs associated with that rewrite).