tweets
1 row where "created_at" is on date 2021-10-12 and quoted_status = 1402049900079026184 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1448053408393428996 | swyx 33521530 | 2021-10-12T22:30:10+00:00 | ok, ok, 1 more way you can beat Amazon: Support. Offer a shared Slack with SLA. Enterprise contracts are being closed on basic premise that "someone who knows what the heck is going on is on Slack with you, whether we are down or you are". Beats this: https://twitter.com/QuinnyPig/status/1402049900079026184 | 1402049900079026184 1402049900079026184 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 278] | 1448049750901551108 | 33521530 | swyx | 1 | 3 | 16 | 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]);