tweets
2 rows where "created_at" is on date 2021-08-08, in_reply_to_screen_name = "swyx" and is_quote_status = 0
This data as json, CSV (advanced)
Suggested facets: created_at (date)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1424172141289689090 | swyx 33521530 | 2021-08-08T00:54:32+00:00 | "How do you cut a monolith in half?" LOTS of gold in @tef_ebooks's exploration of why msg brokers don't replace load balancers or databases. The long-lived section is very relevant to @temporalio (lock manager + db + scheduler + protocol). https://programmingisterrible.com/post/162346490883/how-do-you-cut-a-monolith-in-half https://twitter.com/swyx/status/1424172141289689090/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 266] | 1417315435892985856 | 33521530 | swyx | 0 | 1 | 10 | 0 | 0 | 0 | en | |||||||
1424198548720029698 | swyx 33521530 | 2021-08-08T02:39:29+00:00 | useful taxonomy of approaches to naming things: - Functional / Descriptive (BMW) - Invented (eg Agilent) - Experiential (eg Infoseek) - Evocative (eg Uber) With the same note on Apple https://www.igorinternational.com/process/i/Igor-naming-guide-AugustP-1-2021.pdf https://twitter.com/swyx/status/1424198548720029698/photo/1 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 211] | 1418034673150685185 | 33521530 | swyx | 0 | 0 | 7 | 0 | 0 | 0 | en |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [tweets] ( [id] INTEGER PRIMARY KEY, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [full_text] TEXT, [retweeted_status] INTEGER, [quoted_status] INTEGER, [place] TEXT REFERENCES [places]([id]), [source] TEXT REFERENCES [sources]([id]), [truncated] INTEGER, [display_text_range] TEXT, [in_reply_to_status_id] INTEGER, [in_reply_to_user_id] INTEGER, [in_reply_to_screen_name] TEXT, [geo] TEXT, [coordinates] TEXT, [contributors] TEXT, [is_quote_status] INTEGER, [retweet_count] INTEGER, [favorite_count] INTEGER, [favorited] INTEGER, [retweeted] INTEGER, [possibly_sensitive] INTEGER, [lang] TEXT, [scopes] TEXT, FOREIGN KEY([retweeted_status]) REFERENCES [tweets]([id]), FOREIGN KEY([quoted_status]) REFERENCES [tweets]([id]) ); CREATE INDEX [idx_tweets_source] ON [tweets] ([source]);