tweets
2 rows where display_text_range = "[22, 268]" sorted by in_reply_to_screen_name
This data as json, CSV (advanced)
created_at (date) 2 ✖
- 2021-11-16 1
- 2021-12-26 1
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1460489833160142848 | swyx 33521530 | 2021-11-16T06:08:05+00:00 | @YairDev @JoshWComeau @csswizardry's article changed the way i think about margins forever: https://csswizardry.com/2012/06/single-direction-margin-declarations/ knowing about collapse is good, but having rules so that you dont even think about it 99% of the time can be better (altho i like layout components too) | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [22, 268] | 1459780398741864448 | 1297737445404966913 | YairDev | 0 | 1 | 7 | 0 | 0 | 0 | en | |||||||
1475137021014605825 | swyx 33521530 | 2021-12-26T16:10:47+00:00 | @calcsam @Rich_Harris bit specific, people want to play in the NBA, no matter the position. Steph Curry is 6'2. that aside, to the extent that "talent" is innate and "luck" is exogenous/stochastic, i do like the characterisation of NBA careers as high-talent low-luck | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [22, 268] | 1475135726060589063 | 788059556 | calcsam | 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]);