tweets

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

1 row where "created_at" is on date 2021-09-11 and in_reply_to_screen_name = "rauchg" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

in_reply_to_screen_name 1 ✖

  • rauchg · 1 ✖

created_at (date) 1 ✖

  • 2021-09-11 · 1 ✖
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
1436716757436321799 swyx 33521530 2021-09-11T15:42:22+00:00 @rauchg @leeerob yeah i don't doubt that switching from CSR to SSR was the unmitigated win here. Still they have characterized it as "initial required JS", sounds like you would have phrased it differently. also no way Nextjs takes up 800kb, something else is going on that they couldnt rip out       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [17, 294] 1436710278494707719 15540222 rauchg       0 0 8 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]);