tweets
3 rows where "created_at" is on date 2021-08-11 and in_reply_to_user_id = 229237555
This data as json, CSV (advanced)
Suggested facets: source
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1425301069903523842 | swyx 33521530 | 2021-08-11T03:40:30+00:00 | @slightlylate i like the “special occasion food” phrasing! do you think React Server Components solve this problem well? I went back in your history and only saw mentions about JSF but on this specific “turn off clientside JS by default” goal, it is supposed to do that, runtime aside. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [14, 288] | 1425137032461004800 | 229237555 | slightlylate | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1425330017928572936 | swyx 33521530 | 2021-08-11T05:35:32+00:00 | @slightlylate greatly appreciate your thoughts, as always. i was too narrowly focused on the technical aspects of RSCs. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [14, 119] | 1425329048406970375 | 229237555 | slightlylate | 0 | 0 | 2 | 0 | 0 | en | ||||||||
1425336133622198272 | swyx 33521530 | 2021-08-11T05:59:50+00:00 | @slightlylate RSCs ofc wont fix everything but i still think a worthwhile start to an acknowledged problem. right now i'm more concerned that their momentum has stalled. idk if you know but you were definitely part of my influence for exploring new tools beyond React since 2019. so thanks :) | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [14, 293] | 1425330896652185600 | 229237555 | slightlylate | 0 | 0 | 3 | 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]);