tweets

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

2 rows where display_text_range = "[8, 67]"

✎ 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
1461058299852320769 swyx 33521530 2021-11-17T19:46:58+00:00 @Swizec infinite games, not long term games https://twitter.com/swyx/status/1281424520100737025?s=20   1281424520100737025 1281424520100737025   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [8, 67] 1461057956171059202 15353121 Swizec       1 0 1 0 0 0 en  
1467984394220552192 swyx 33521530 2021-12-06T22:28:48+00:00 @danluu i suspect its more the "Familiarity breeds contempt" effect       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [8, 67] 1467982643237044225 18275645 danluu       0 0 2 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]);