tweets

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

5 rows where "created_at" is on date 2021-12-07 and in_reply_to_user_id = 12745092

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: retweet_count, favorite_count, 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
1468072485258072064 swyx 33521530 2021-12-07T04:18:50+00:00 @chantastic using convertkit or something else? any pain points?       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [12, 64] 1468072352189534208 12745092 chantastic       0 0 1 0 0   en  
1468073466830082051 swyx 33521530 2021-12-07T04:22:44+00:00 @chantastic hold my vscode. its literally the perfect @temporalio usecase.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [12, 74] 1468073287938891777 12745092 chantastic       0 1 2 0 0   en  
1468075113878736897 swyx 33521530 2021-12-07T04:29:17+00:00 @chantastic @temporalio Nathan's said that for like 8 years haha. i 100% believe him       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [24, 84] 1468074401375473666 12745092 chantastic       0 0 1 0 0   en  
1468077116600188935 swyx 33521530 2021-12-07T04:37:14+00:00 @chantastic @temporalio could you put a mock YAML API up on a gist somewhere? for design inspo so I can code against it like how would you like the time delays specified and any conditions/customizations you would like       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [24, 221] 1468073809898991618 12745092 chantastic       0 0 1 0 0   en  
1468079819699064835 swyx 33521530 2021-12-07T04:47:59+00:00 @chantastic @temporalio sure man       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [24, 32] 1468078804820058112 12745092 chantastic       0 0 1 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]);