tweets

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

1 row where "created_at" is on date 2021-11-17, in_reply_to_screen_name = "technoheads" and is_quote_status = 0 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

retweeted 1 ✖

  • 0 1

is_quote_status 1 ✖

in_reply_to_screen_name 1 ✖

  • technoheads · 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
1461114281416482822 swyx 33521530 2021-11-17T23:29:25+00:00 @technoheads yes indeed. unfortunately i believe @hillelogram has consistently pointed out that other empirical research on whether or not type systems actually help has been more equivocal. ultimately we spread the research that supports the POV we want to tell anyway.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [13, 270] 1461113837332176897 19136507 technoheads       0 0 1 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]);