tweets

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

6 rows where "created_at" is on date 2021-11-07 and favorite_count = 1 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source

user 1 ✖

favorite_count 1 ✖

created_at (date) 1 ✖

  • 2021-11-07 · 6 ✖
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  
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  
1457412996733423616 swyx 33521530 2021-11-07T18:21:50+00:00 @dejavucoder @audacitus @BrandonHexsel ship more tends to humble you very very quickly       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [39, 87] 1457412337212669954 1446445479068241923 dejavucoder       0 0 1 0 0   en  
1457444573601431552 swyx 33521530 2021-11-07T20:27:19+00:00 @tylertringas no but it is not your fault; the kind of people that want to deploy a lot of money want to deploy a lot of money fast and return a lot of money fast, that tends to lead to frenzied companies or conversely, frenzied companies are more likely to promise to deploy fast/return fast       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [14, 293] 1457439574020530182 33353061 tylertringas       0 0 1 0 0   en  
1457460664230834176 swyx 33521530 2021-11-07T21:31:15+00:00 @buildsghost @floydophone @sebmck even the thing about checked-in source is controversial - i saw a thoughtleader™ on here a month or so ago passionately arguing for only publishing dist (not src) files because something something size of node modules       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [34, 251] 1457448799928926212 1175464650395111424 buildsghost       0 0 1 0 0   en  
1457471843107889158 swyx 33521530 2021-11-07T22:15:40+00:00 @zevav hey glad you are enjoying it!! :) :)       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [7, 43] 1457466032365445120 38199764 zevav       0 0 1 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]);