calebglawson / baquet Goto Github PK

list_memberships
list_subscriptions (but do a list_all)

columns
created_at
description
full_name
id_str
member_count
subscriber_count
uri
user

Somehow, some way, this needs to happen.

• Get all tags
• Get tags on a tweet
• Return them in a list format, eliminate exposure of association object
• Get all tweets that match a tag

1. Following watchlist percent
2. Following watchlist completion
3. Friends watchlist percent
4. Friends watchlist completion
5. Retweet watchlist percent
6. Favorite watchlist percent

Use marshmallow?

We need the ability to:

• View Sublists
• View Sublist users
• View Sublist exclusions
• Exclude users from sublist
• Import subblist (blockbot, twitter)
• Refresh sublist (same as import)
• Remove sublist

Relationship:
User 1:* UserSubList *:1 Sublist *:1 SubListType

Ability to tag or leave a note on a tweet, favorite, or user for easy recall.

If following and friends are not cleared upon each refresh of the data, we risk leaving stale data behind.

Lint and DRY. Do an end to end manual test.

Provide a mechanism to ensure that SQL connections are able to be terminated properly

Cache the results of hydrate user ids to the Directory, when hydrating, check for any user data that we have fetched already and only fetch user IDs for which we do not have the cached data.

Add a new boolean flag called show, which will determine if the user entry is to be shown in get directory. User should only be shown if we have a file for them.

Identified by user_id + slug or list_id. By default append, unless replace=True