Data source: swyx's twitter data
| id | user | created_at | full_text | retweeted_status | quoted_status | place | source | truncated | display_text_range | in_reply_to_status_id | in_reply_to_user_id | in_reply_to_screen_name | geo | coordinates | contributors | is_quote_status | retweet_count | favorite_count | favorited | retweeted | possibly_sensitive | lang | scopes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1467254739255513088 | 33521530 | 2021-12-04T22:09:24+00:00 | @mikekelly85 @simonvc @temporalio hi! I work at Temporal. k8s is just a deployment strategy, we don't require it. we have 2-3 person startups running us in production (https://twitter.com/swyx/status/1453477956160868358). The internals are complex but the exposed API is simple. like every framework! https://twitter.com/rauchg/status/1316808667925082112 | 1316808667925082112 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [34, 297] | 1467178065348468736 | 15151905 | mikekelly85 | 1 | 0 | 1 | 0 | 0 | 0 | en |