tweets

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

1 row where "created_at" is on date 2021-09-15, lang = "en" and user = 2461541

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: 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
1438052380227117076 ☞ Desigan Chinniah ☜ 2461541 2021-09-15T08:09:39+00:00 Q: Engineers — you've always wanted to time travel, right? A: Now you can. When debugging w/ @ReplayIO. Crafted by @jasonlaster11 @sophaskins @jonbell + team Advised by myself @rachelnabors @auchenberg @swyx + more Hunted by @nickabouzeid Grab it ›› https://www.producthunt.com/posts/replay-4 https://twitter.com/jasonlaster11/status/1438035707704995840   1438035707704995840 1438035707704995840   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 278]             1 9 16 0 1 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]);