tweets

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

1 row where "created_at" is on date 2021-03-12, is_quote_status = 0, retweeted = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

source 1 ✖

  • Twitter Web App · 1 ✖

retweeted 1 ✖

is_quote_status 1 ✖

created_at (date) 1 ✖

  • 2021-03-12 · 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
1370513317379280897 swyx 33521530 2021-03-12T23:13:32+00:00 🆕 Preemptive Pluralization is (Probably) Not Evil https://www.swyx.io/preemptive-pluralization/ Fully-baking a theory by @r00k on the @artofproductpod, I make the case for a "Premature" Optimization you should consider. TL;DR - Pluralized code is robust to @hillelogram's requirement perturbations!       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 279]             0 50 202 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]);