Show replies and threads of tweets

[nicholaschiang]

Imported from @nicholaschiang's original Linear issue TS-22.

I could easily create a nice thread-reader type experience where I show all of the replies and retweets of a tweet for an article. Kinda like a hierarchy:

Article → Tweet → Replies & Threads → Retweets → Replies & Threads, etc, etc.

[nicholaschiang]

From @nicholaschiang on Thursday, 3/24/22, 5:43 PM PDT:

Currently there's no easy way to get a tweet's replies (see https://linear.app/roote/document/twitter-sucks-5d618997021d).

[nicholaschiang]

From @nicholaschiang on Thursday, 3/24/22, 12:30 PM PDT:

To do this, I'm going to have possibility infinite Remix nested routes where each URL is to a reply or retweet or thread, etc. and then when a new retweet is opened I should sync from Twitter and perhaps show a tiny bit of a skeleton screen (for <50ms). When you click on a tweet, I:

• Open a nested Remix route: /lists/:id/tweets/:id
• Remix automatically calls my nested route's loader to fetch the tweet replies from Postgres.
• Manually call an action to revalidate that data from Postgres by fetching from Twitter.
  • Use SWR here or (if it doesn't slow things down to have two requests to Twitter) use a similar strategy to tweets.server and only fetch all 100 replies if we don't already have the last reply cached.
  • Allow the user to override our SWR or caching strategy to manually revalidate the latest data from Twitter (e.g. show a "Last synced 23s ago" indicator in the nested route and, when clicked, call this action with some special query parameter ?swr=false or something).
• Use fetcher.submission to optimistically show data from Twitter (without waiting on Postgres).
• Remix automatically re-fetches loader data from Postgres after action resolves.

And then recursively repeat that process an infinite number of times using a catch-all route ($.ts). I'll have to investigate whether those catch-all routes actually recursively render themselves into their own <Outlet>…

[nicholaschiang]

Partially addressed by #64.