tweets

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

1 row where favorited = 0, retweeted = 0 and user = 12819682 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

  • Mitchell Hashimoto · 1 ✖

retweeted 1 ✖

retweet_count 1 ✖

  • 7 1

is_quote_status 1 ✖

  • 0 1

created_at (date) 1 ✖

quoted_status 0 ✖

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
1316510643030114304 Mitchell Hashimoto 12819682 2020-10-14T22:46:11+00:00 @BRMatt Oh yeah, EVERYTHING. Basically all long-running background processes. It is an incredible technology. Disclaimer: I’m now an advisor to Temporal, but only because I was a huge fan already prior. Examples coming…       Tweetbot for Mac 2d56427825d31a620d10acb51615805f894c90f6 0 [8, 219] 1316508745548156928 23248421 BRMatt       0 7 27 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]);