Which makes it take forever for the component to load

Presumably something in how react calls constructors and where the call is placed today

For a given user, pull in:

• their account
• their following
• the tweets of their following within the last 24 hours

This looks like it'll involve

• modifying the twitter user model to include the username (as opposed to just ID and name)
• modify the get_twitter_user_from_twitter method to get the username and store it
• modify the read_tweets_of_following_by_twitter_user_id method to also pull the user's username and store it in the returned tweet object
• modify the FE to turn the user's name into a link of the form https://twitter.com/{{username}}/status/{{tweet_id}}

It sorta works today but confirm it's the right way to do it, maybe check out CORS middleware

https://fastapi.tiangolo.com/tutorial/testing/

• Feed of links
• • Show the link url as a hyperlink
• • Show the number of users who tweeted it
• • Order by number of users desc
• Only pull links for the current user within the last 24 hours

Things to do:

• Add attribute to twitter_user for last_tweet_id, change the twitter polling task to store that and check against that when polling twitter, and only store tweets that have valid urls in the db
• based on that, Remove the url check from the route and the twitter_user.read_tweets_of_following_by_twitter_user_id function
• refactor twitter_user.read_tweets_of_following_by_twitter_user_id to first loop and get all following ids, then make a single db query (add the requisite crud helper) that pulls the tweets of the last 24 hours for all users (this will need to account for getting the combined username details in the tweets array that gets returned)

• Dockerize the API
• Dockerize the FE
• Dockerize the SQLite??

Give a way to select users who receive priority in the list

Display starred users

• Add something to the user model to indicate which twitter_users are starred for that user
• Change the rendering order to show starred users first
• Add a UI element to distinguish a starred users

Star users

• Add a UI element for starring or unstarring a user
• Add an API call to star or unstar a user
• Have that API call modify the model for that user to add or remove the given user being toggled

Use since_id to limit the number of new tweets pulled and stay under the monthly tweet cap

This should be in create_tweets_of_a_twitter_user_by_id:

• Add a crud method to get the most recent tweet from that user
• If none, then just call client.get_users_tweets like normal
• Else, pass that Id as since_id in the call to client.get_users_tweets

I mean also just design the two column layout for real

Need a way to handle follows changing (unfollowing, new follows)

Probably a something like both changing the twitter following creation to check for pre-existing follows (and skip them if so) and maybe something like regenerating the following list?

Maybe a two-column layout? Link on left, tweets on right?

Get title at least, maybe first paragraph or something

• Get all users
• Get single user by id
• Get a single twitter user by id
• Create user
• Create twitter user
• Create tweet
• Create follow
• Get all twitter users a user is following
• Get all followers of followers of a user
• Get all tweets from users followers (within optional date)
• Get all tweets from followers of followers (within optional date)

To explore:

• making a recurring task that just gets the X newest tweets from every account in the db?
• changing to just get tweets, not get followings?
• others?

https://fastapi.tiangolo.com/tutorial/background-tasks/

with the actual real data from twitter

User can log in a view their feed, and only their feed

No logged out user can view a feed

Requires a login page, hashed password in the user model, and figuring out the oauth flow between the FE and BE

Timezones are probably gonna be an issue for the time limit bit; figure out if that's true and figure out a way to deal with it

https://fastapi.tiangolo.com/tutorial/bigger-applications/

One level deeper, get the followings of each user the user is following
This almost certainly will run into twitter rate limits if not done as some sort of partial background task, or with a backoff