tweets

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

2 rows where favorited = 0, in_reply_to_user_id = 126277070 and retweeted = 0

✎ 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
1441214916287819784 swyx 33521530 2021-09-24T01:36:27+00:00 @sebtechlife thank you!!       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [13, 24] 1441212725581914117 126277070 sebagudelo       0 0 0 0 0   en  
1469098349051596800 swyx 33521530 2021-12-10T00:15:15+00:00 @sebagudelo more to the point it prompts churn 🙃 “might as well look at other vendors if we’re gonna have to go into this next tier”       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [12, 132] 1469095918834122754 126277070 sebagudelo       0 0 8 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]);