tweets
2 rows where "created_at" is on date 2021-09-01 and retweet_count = 2 sorted by lang
This data as json, CSV (advanced)
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 | |||||||
1432864045133008899 | swyx 33521530 | 2021-09-01T00:33:04+00:00 | "Are you ignoring Heroku?" Heroku was so right so early - and then stagnated. We can do a lot more at build time, and at runtime. Among the platforms innovating on this: @begin, @vercel, @netlify, @PulumiCorp, @goserverless, @WaspLang! There's a tangible movement building. https://twitter.com/swyx/status/1432864045133008899/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 278] | 1432864042343813120 | 33521530 | swyx | 0 | 2 | 9 | 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]);