tweets
4 rows where "created_at" is on date 2021-09-05 and favorite_count = 4 sorted by favorite_count
This data as json, CSV (advanced)
Suggested facets: in_reply_to_user_id, in_reply_to_screen_name, is_quote_status
source 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1434435021532803075 | swyx 33521530 | 2021-09-05T08:35:34+00:00 | @dan_abramov @reactjs @ryanflorence we all need good custom dropdown/typeahead/datepicker components. does that stuff really need to hook into React? no (i think). yet the best ones seem to all assume React. am i arguing myself into web components? i’m not sure. i like the “headless” nature of hooks. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [36, 302] | 1434433245664456704 | 33521530 | swyx | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1434448316734099461 | swyx 33521530 | 2021-09-05T09:28:24+00:00 | @fraser_drops @chrisshank23 yes! also a great option. i just know that this is not the default choice for React devs (React prefers everything in local component state as much as possible) and theres a learning curve for state charts. but that’s the dream for @statelyai | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [28, 270] | 1434444454803345412 | 1114700683612053505 | fraser_drops | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1434500277567115266 | swyx 33521530 | 2021-09-05T12:54:52+00:00 | awesome writeup on adding custom monaco autocompletes for in-app editors! https://twitter.com/tim_nolet/status/1402925458623172611 | 1402925458623172611 1402925458623172611 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 73] | 1321978673868599296 | 33521530 | swyx | 1 | 0 | 4 | 0 | 0 | 0 | en | ||||||
1434501288788697088 | swyx 33521530 | 2021-09-05T12:58:53+00:00 | @passle_ @reactjs WCs are definitely one way to get there! what i do enjoy about hooks is they are “headless” so you get to take them apart or compose them however you like. that is genius. best way out of this ive seen is reusable statecharts (mentioned in other reply chain) | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [18, 276] | 1434476696238018563 | 4874949729 | passle_ | 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]);