tweets
2 rows where "created_at" is on date 2021-12-01, favorite_count = 4 and retweeted = 0
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1465909286748536833 | swyx 33521530 | 2021-12-01T05:03:03+00:00 | @uidotdev @cassidoo @tylermcginnis quick feedback - this landing page doesnt state the date or time, just has the subscription - i was very confused. i got recommended it from a different place than this tweet, and at first i thought it was an article and was very confused by why it was so short | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [20, 297] | 1465741650412457986 | 1212257215504977921 | uidotdev | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1465990628433489924 | swyx 33521530 | 2021-12-01T10:26:17+00:00 | @dev__adi @ryanflorence @deno_deploy @remix_run we had the “fat function” issue with SvelteKit as well. i think @antony concluded that the benefits of having everything in one function outweighed the complexity of deploying it - although i think @brianleroux would probably say that that doesnt scale for cold starts | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [48, 316] | 1465684400419454976 | 1650129775 | dev__adi | 0 | 0 | 4 | 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]);