tweets
1 row where "created_at" is on date 2021-11-12, in_reply_to_user_id = 1593171 and source = "95f3aaaddaa45937ac94765e0ddb68ba2be92d20"
This data as json, CSV (advanced)
Suggested facets: 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1458964004102049811 | swyx 33521530 | 2021-11-12T01:04:59+00:00 | @threepointone it is meaningful in that it matters where your data lives. this is why CF making KV and DO as clean abstractions is so important for edge and literally nobody else has figured this out | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [15, 199] | 1458891120696516612 | 1593171 | threepointone | 0 | 0 | 2 | 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]);