tweets

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

4 rows where "created_at" is on date 2021-10-10, in_reply_to_screen_name = "swyx" and retweeted = 0 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: is_quote_status, retweet_count, favorite_count

in_reply_to_screen_name 1 ✖

  • swyx · 4 ✖

created_at (date) 1 ✖

  • 2021-10-10 · 4 ✖
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
1447028051653525504 swyx 33521530 2021-10-10T02:35:46+00:00 posted! https://twitter.com/swyx/status/1439966955570618376?s=20   1439966955570618376 1439966955570618376   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 31] 1437109166334783494 33521530 swyx       1 0 6 0 0 0 en  
1447029534591569922 swyx 33521530 2021-10-10T02:41:40+00:00 @chris_mccord @flydotio I think I was too kind to the "Smart Server" movement in my original take on this. @Rich_Harris gives a compelling keynote in the recent @jamstackconf arguing that frameworks will embrace #TransitionalApps, and gives the latest @Sveltejs Kit demo! https://twitter.com/Rich_Harris/status/1446601175197880325   1446601175197880325 1446601175197880325   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [24, 297] 1440797518749601803 33521530 swyx       1 0 11 0 0 0 en  
1447250019233386504 swyx 33521530 2021-10-10T17:17:47+00:00 @levelsio @stephsmithio more benefits https://twitter.com/rothgar/status/1446867332748300288   1446867332748300288 1446867332748300288   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [24, 37] 1446052399324356609 33521530 swyx       1 0 6 0 0 0 en  
1447312315485810691 swyx 33521530 2021-10-10T21:25:20+00:00 APIs that have memory, that collaborate with you on your intent, are so much more human than cold-blooded pass/fail machines. The only reason we don’t do it is because our platforms make it hard to casually provision state and pause/resume logic. @temporalio literally fixes this       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 280] 1447312313426460672 33521530 swyx       0 3 19 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]);