tweets

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

1 row where "created_at" is on date 2021-08-16, quoted_status = 1427351638872772633 and user = 33521530 sorted by lang descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1 ✖

  • swyx · 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
1427394565107945489 swyx 33521530 2021-08-16T22:19:18+00:00 @willklein_ @Nutlope @kevmodrome @jkup some thoughts here! for tracking need to balance usefulness (whether you can actually act on it) with ability to track (some data is nice to have but difficult to collect). i ended up breaking it down by sub discipline instead https://twitter.com/swyx/status/1427351638872772633   1427351638872772633 1427351638872772633   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [39, 267] 1420139767820259328 17496447 willklein_       1 0 2 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]);