tweets

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

2 rows where user = 397782926 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

is_quote_status 2 ✖

created_at (date) 2 ✖

in_reply_to_screen_name 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
1438972757862191106 Hillel 397782926 2021-09-17T21:06:54+00:00 Audiences also have different *purposes*. The docs for a software package change if the reader's purpose is to: * Use it on a new project * Understand its use in an existing project * Write plugins for it * Teach others how to use it * Port it to a different language       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 268] 1438972755848880133 397782926 hillelogram       0 1 11 0 0   en  
1455261914297249798 Hillel 397782926 2021-11-01T19:54:12+00:00 Other examples are preemptive pluralization (https://twitter.com/swyx/status/1370513317379280897) and preemptive pagination. Not always the right choice, but right often enough that you should seriously consider them even when following YAGNI   1370513317379280897 1370513317379280897   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 214] 1455261278335913984 397782926 hillelogram       1 3 35 1 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]);