tweets

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

1 row where is_quote_status = 1 and user = 15629200 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1 ✖

  • Nicole Sullivan · 1 ✖

retweet_count 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
1471213109767405568 Nicole Sullivan 15629200 2021-12-15T20:18:33+00:00 Utility classes: I'm not in a mood to be erased today. I was experimenting with utility classes in large production sites starting in ~2004. In 2009, I got brave and shared! I have receipts.✍🏻 Others released similar things in 2011-2014. https://twitter.com/zachleat/status/1470775386611011590   1470775386611011590 1470775386611011590   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 238]             1 135 588 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]);