tweets
4 rows where "created_at" is on date 2021-08-11 and in_reply_to_screen_name = "ritakozlov_" sorted by lang descending
This data as json, CSV (advanced)
source 2 ✖
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1425253637979181061 | swyx 33521530 | 2021-08-11T00:32:01+00:00 | @ritakozlov_ it does look good! the problem (that we are also wrestling with) is when you tie API to cron its hard to do some things like "every 3rd wednesday" or "last day of the month" as this code sample was probably trying to do also we're designing for long running wfs that may overlap https://twitter.com/swyx/status/1425253637979181061/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [13, 293] | 1425240576975278080 | 232076816 | ritakozlov_ | 0 | 0 | 5 | 0 | 0 | 0 | en | |||||||
1425266629017890816 | swyx 33521530 | 2021-08-11T01:23:39+00:00 | @ritakozlov_ i mean sure that works too i wouldnt overreact 😅 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 61] | 1425265547550158848 | 232076816 | ritakozlov_ | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1425267775967096832 | swyx 33521530 | 2021-08-11T01:28:12+00:00 | @ritakozlov_ @jasnell reject cloud embrace corn | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [22, 47] | 1425267547469848584 | 232076816 | ritakozlov_ | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1425561725877637121 | swyx 33521530 | 2021-08-11T20:56:15+00:00 | @ritakozlov_ @_AlbertZhao well look at that! i missed the L/W additions. awesome! | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [26, 81] | 1425560858353049601 | 232076816 | ritakozlov_ | 0 | 0 | 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]);