tweets
2 rows where retweet_count = 45, retweeted = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by coordinates
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1439702355553886211 | swyx 33521530 | 2021-09-19T21:26:04+00:00 | 🆕 Latest podcast is with @threepointone! https://www.youtube.com/watch?v=H3h1WICelqs We discuss: - @Reactjs vs @Temporalio - @statelyai State Charts - React Streaming SSR - ESBuild vs swc - Figma vs Canva - Gatsby vs Next.js - React Server Components & @Shopify Hydrogen - Notion's 9MB JS website | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 282] | 0 | 45 | 341 | 0 | 0 | 0 | en | ||||||||||
1444544841149341700 | swyx 33521530 | 2021-10-03T06:08:23+00:00 | This thread of backend engineers discovering what ACID databases are, and asking if it matters, feels like it touches on a fundamental tension in our industry Would you require that a backend engineer know what ACID is to hire them? Even if they sling PostgreSQL like a champ? https://twitter.com/Coding_Career/status/1444542756647419909 https://twitter.com/swyx/status/1444544841149341700/photo/1 | 1444542756647419909 1444542756647419909 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 301] | 1 | 45 | 339 | 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]);