tweets

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

1 row where "created_at" is on date 2021-09-11, favorite_count = 4 and quoted_status = 1436708762115473411

✎ 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
1436716037202980868 swyx 33521530 2021-09-11T15:39:30+00:00 @simonw i genuinely think this one assumption made many remaining decisions for them: https://twitter.com/slightlylate/status/1436708762115473411?s=20 I hear unexamined assumptions like these a lot and people don't realize these are far weightier decisions than they seem at first glance. Rhyme shortcircuits reason.   1436708762115473411 1436708762115473411   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [8, 276] 1436710644045152262 12497 simonw       1 0 4 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]);