tweets

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

3 rows where "created_at" is on date 2021-10-27, in_reply_to_screen_name = "stubailo" and user = 33521530 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

is_quote_status 2 ✖

user 1 ✖

  • swyx · 3 ✖

in_reply_to_screen_name 1 ✖

  • stubailo · 3 ✖

created_at (date) 1 ✖

  • 2021-10-27 · 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
1453187165291118597 swyx 33521530 2021-10-27T02:29:53+00:00 @stubailo @stolinski y u roasting my design doc https://twitter.com/swyx/status/1453187165291118597/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [21, 47] 1453186117289734146 12767662 stubailo       0 0 2 0 0 0 en  
1453189491032616965 swyx 33521530 2021-10-27T02:39:08+00:00 @stubailo @stolinski got 9 minutes? :) https://twitter.com/swyx/status/1449069225704714246   1449069225704714246 1449069225704714246   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [21, 64] 1453188705900896261 12767662 stubailo       1 0 1 0 0 0 en  
1453400900697874433 swyx 33521530 2021-10-27T16:39:12+00:00 @stubailo @stolinski responding quickly can be done with a short workflow or signalling into and querying out of a long workflow. both are fine, so long as it isn't realtime. i have a nextjs sample here that shows how you can embed a temporal client in a serverless endpoint https://github.com/temporalio/samples-typescript/tree/main/nextjs-ecommerce-oneclick       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [21, 301] 1453394921470132224 12767662 stubailo       0 0 0 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]);