tweets
3 rows where "created_at" is on date 2021-08-23, is_quote_status = 0, retweeted = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1429701072348647425 | swyx 33521530 | 2021-08-23T07:04:32+00:00 | @chantastic @alexandereardon @sveltejs (it actually does compile to JS under the hood, but the impedance mismatch is far lower its a joke-but-not-joke that the Svelte ecosystem is larger than React's because its a superset of HTML, the first language of the web, with the attendant teachability/compatibility benefits) | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [39, 319] | 1429699966444851202 | 12745092 | chantastic | 0 | 0 | 6 | 0 | 0 | en | ||||||||
1429888354192019476 | swyx 33521530 | 2021-08-23T19:28:44+00:00 | 🆕 Blog: Why Isn't Usage Based Billing A Bigger Category? https://dev.to/swyx/why-isn-t-usage-based-billing-a-bigger-category-m8b | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 81] | 0 | 2 | 29 | 0 | 0 | 0 | en | ||||||||||
1429941443863347206 | swyx 33521530 | 2021-08-23T22:59:41+00:00 | @TomerAberbach np :) API design is a pet topic of mine. As I build up my career in the "Developer Experience" industry I hope to develop my own strong opinions on what an ideal API design (and design process) looks like. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [15, 220] | 1429940285715460098 | 708470652693565440 | TomerAberbach | 0 | 0 | 1 | 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]);