Dodo

[lambtron]

Value proposition:

• people get notified when you follow them, but they don't know when you unfollow them
• this is a low friction way for you to follow someone, but still maintain a 'clean' list of people you follow
• make sure that your 'Transient' list is private or people will get mad!

User use case:

• add someone to 'Transient' twitter list
• app will scan that list and remove people after they've been there for a month

https://dev.twitter.com/rest/reference/get/lists/list https://dev.twitter.com/rest/reference/get/lists/members https://dev.twitter.com/rest/reference/post/friendships/destroy (unfollow)

[lambtron]

• [x] come up with a better name, a play on transience and birds (twitter)
• [x] setup app scaffold (no data store needed for personal use, can use twitter app credentials)
• [ ] A) setup scheduler that would accomplish the below tasks
• [ ] 1. run nightly
• [ ] 2. scan all members of 'Transient' twitter list
• [x] 3. check the join_date (confirm that this even exists)
• [x] 4. if join_date exceeds one month, then 'unfollow'
• [ ] maybe add some metrics? # of members in list over time or something?
• [ ] B) productize it? (confirm if the below works due to permissions issues)
• [ ] 1. users must create their own 'Transient' list
• [ ] 2. users then authenticate into this app
• [ ] 3. we'll need a small data store to just keep the user's credentials

[lambtron]

A3 and A4 are nullified since join_date does not exist (i.e. when the user became a member of the list).

One option is to run the scheduler monthly and just purge on that date.

Other option is to have a data store of users, which would include joinedAt (when the user was added); a nightly scheduler would then go through the 'Transient' list and add new members, while also going through the users db and remove those users where joinedAt exceeded a month.

[lambtron]

Dodo, as a name? Because they're extinct.

[lambtron]

https://github.com/lambtron/dodo