tweets
4 rows where "created_at" is on date 2021-09-01 and retweet_count = 1
This data as json, CSV (advanced)
Suggested facets: source, in_reply_to_user_id, is_quote_status, favorite_count, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1432864040624091138 | swyx 33521530 | 2021-09-01T00:33:03+00:00 | To paraphrase: DX advances by extending the number of important problems our code handles without thinking of them. If we can isolate these chores, we can design them into the language, or build it into the platform. The holy grail: Language-AS-platform, Infra-FROM-code. https://twitter.com/swyx/status/1432864040624091138/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 274] | 1432864036241088513 | 33521530 | swyx | 0 | 1 | 12 | 0 | 0 | 0 | en | |||||||
1432864050895994890 | swyx 33521530 | 2021-09-01T00:33:05+00:00 | I previously wrote about Cloud Distros, my term for the "second layer" of clouds forming atop the Big Three: https://twitter.com/swyx/status/1252699745883062272 Self Provisioning Runtimes are one step further into the breach - instead of YAML config and SDK code, these platforms *read the app code*. | 1252699745883062272 1252699745883062272 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 273] | 1432864048677154818 | 33521530 | swyx | 1 | 1 | 12 | 0 | 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 | |||||||
1433117668156928004 | swyx 33521530 | 2021-09-01T17:20:52+00:00 | This is not to say that if you can’t figure it out, it’s not your fault: we are tremendously bad at documenting our code, and documenting our journeys. Seek out your dev community for help, and remember how this feels when its your turn to see newer devs struggling. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 267] | 1432977957388120064 | 33521530 | swyx | 0 | 1 | 8 | 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]);