tweets

This is data scraped from swyx's timeline! See blog post

3 rows where "created_at" is on date 2021-10-17 and in_reply_to_user_id = 33521530 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source, is_quote_status, retweet_count

in_reply_to_user_id 1 ✖

  • 33521530 · 3 ✖

in_reply_to_screen_name 1 ✖

created_at (date) 1 ✖

  • 2021-10-17 · 3 ✖
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
1449609391666171906 swyx 33521530 2021-10-17T05:33:06+00:00 Re: the dark arts of launch timing. There’s a bell curve: The mediocre makers do it because they value the wrong things. The big players do it because media cycles matter. The rest should build async distribution and focus on shipping great work, as often as they can manage.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 279] 1449465216199061507 33521530 swyx       0 1 8 0 0   en  
1449800380804517888 swyx 33521530 2021-10-17T18:12:01+00:00 @harisvsulaiman @reactjs @taillogs still ongoing hahah. beta coming soon. http://temporal.io/node       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [35, 97] 1316799481543684096 33521530 swyx       0 0 2 0 0 0 en  
1449884413848809475 swyx 33521530 2021-10-17T23:45:56+00:00 @noseratio @jhooks our job is executing work across time and unreliable networks and machines: https://twitter.com/threepointone/status/1449112317917110276?s=21, React’s job is rendering the most current version of app state that is ready. i guess perhaps the analogy falls down there but there’s still useful things to borrow from React.   1449112317917110276 1449112317917110276   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [19, 297] 1449882287240187909 33521530 swyx       1 0 1 0 0 0 en  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);