tweets
4 rows where "created_at" is on date 2021-09-01 and favorite_count = 7 sorted by coordinates
This data as json, CSV (advanced)
Suggested facets: source, in_reply_to_user_id, in_reply_to_screen_name, is_quote_status, retweet_count
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1432864036241088513 | swyx 33521530 | 2021-09-01T00:33:02+00:00 | At the same time, infrastructure engineers increasingly embracing higher and higher abstractions to solve their problems. The DevOps movement is not so much "Devs doing Ops" as it is Ops doing Dev. As platforms develop, we are learning the chores that can be cleanly delegated. https://twitter.com/swyx/status/1432864036241088513/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 277] | 1432864032235540480 | 33521530 | swyx | 0 | 2 | 7 | 0 | 0 | 0 | en | |||||||
1432864048677154818 | swyx 33521530 | 2021-09-01T00:33:05+00:00 | This was part of my @Temporalio pitch: https://twitter.com/swyx/status/1417165270641045505 Because you can dynamically use retries, timeouts, task queues and timers *without any setup* and Temporal takes care of it behind the scenes: this unlocks *self-provisioning asynchrony* in your app code. https://twitter.com/swyx/status/1432864048677154818/photo/1 | 1417165270641045505 1417165270641045505 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 268] | 1432864045133008899 | 33521530 | swyx | 1 | 0 | 7 | 0 | 0 | 0 | en | ||||||
1432898918589763587 | swyx 33521530 | 2021-09-01T02:51:38+00:00 | @beyang YES. PLEASE. ESP IF IT LETS ME SEARCH WITHIN FOLDERS URGH | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [8, 65] | 1432894718266986499 | 16520821 | beyang | 0 | 0 | 7 | 0 | 0 | en | ||||||||
1432902470418661381 | swyx 33521530 | 2021-09-01T03:05:45+00:00 | @oldmanuk @mitchellh i made an alternative twitter query builder UI as well, in case this question comes up again in future https://bettertwitter.netlify.app/ | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [21, 148] | 1432813730690179073 | 7969342 | oldmanuk | 0 | 1 | 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]);