tweets

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

5 rows where "created_at" is on date 2021-11-07 and source = "95f3aaaddaa45937ac94765e0ddb68ba2be92d20" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, retweet_count, favorite_count

created_at (date) 1 ✖

  • 2021-11-07 · 5 ✖
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
1457158423313674241 swyx 33521530 2021-11-07T01:30:15+00:00 @robhope @OnePageLove @uxlove @EmailLove_ keep the 3 branch ones as dedicated feeds with automated posts @robhope as the superfeed with manual RTs and QTs of significant news from each gives people the “subscribe to as many or as little newsletters from us as you like” option in twitter native format       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [42, 303] 1456606745472688131 14931736 robhope       0 0 1 0 0   en  
1457158536064995332 swyx 33521530 2021-11-07T01:30:42+00:00 @johnny_reilly @orta @typescript queued up to watch, appreciate the rec       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [33, 71] 1456894278404354052 261582708 johnny_reilly       0 0 2 0 0   en  
1457181314776371200 swyx 33521530 2021-11-07T03:01:13+00:00 @httpJunkie @leeerob @reactjs @Cloudflare @vercel @remix_run thank you Eric! yeah feels like the reception for this was super strong for a friday drop!       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [61, 151] 1457020052855685122 1594100137 httpJunkie       0 0 0 0 0   en  
1457256545343840258 swyx 33521530 2021-11-07T08:00:09+00:00 @ejames_c i actually dont find the inability to predict a good thing. people really want predictions. personal outcomes really depend on weighting probabilities right. its not enough to sit back and say “ah look everything is so complex it all depends”. you have to *do something*.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [10, 282] 1457002379258204165 14243237 ejames_c       0 0 1 0 0   en  
1457353577819746321 Ryan Hoover 14417215 2021-11-07T14:25:43+00:00 Why so many people with a startup idea never ship https://twitter.com/rrhoover/status/1457353577819746321/photo/1       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 49]             0 3179 18350 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]);