tweets

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

6 rows where "created_at" is on date 2021-09-11 and in_reply_to_user_id = 33521530

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source, display_text_range, is_quote_status, retweet_count, 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
1436602844216500227 swyx 33521530 2021-09-11T08:09:43+00:00 Enjoying @corywilkerson’s explanation of “.dev” on @changelog https://changelog.com/podcast/459 they dont quite go into whether there was any internal resistance to the shortcut (@ 40mins in), but loved learning about the Github Computer Club and the minor tips (dotfiles, linking vscode)       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 280] 1436594934002458626 33521530 swyx       0 0 9 0 0 0 en  
1436643604085235714 swyx 33521530 2021-09-11T10:51:41+00:00 @smc90 tries to get @BillCarr89 to defend "Are Right A Lot" in this podcast/blogpost on Future dot com and i'm sorry but blaming your direct reports for letting you ignore them is pretty damn toxic wtf https://future.a16z.com/podcasts/working-backwards-amazon-bezos-memos-releases-narratives/ https://twitter.com/swyx/status/1436643604085235714/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 226] 1390439828571922432 33521530 swyx       0 0 11 0 0 0 en  
1436712591292829697 swyx 33521530 2021-09-11T15:25:49+00:00 Since @QwikDev serializes all its state onto HTML, the question arises what to do with unserializable state. Chanced upon Dan’s comment today: “This is what doomed ASP .NET WebForms, and we'd like to learn from their mistakes rather than repeat them.” https://github.com/reactjs/rfcs/pull/188#issuecomment-824139957 https://twitter.com/swyx/status/1436712591292829697/photo/1       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 277] 1435223333398843397 33521530 swyx       0 0 4 0 0 0 en  
1436720513049669632 swyx 33521530 2021-09-11T15:57:17+00:00 I'm no perf expert or perf shamer (let he who is without sin...) But here's what I do believe: 1. local Lighthouse runs are not credible. Use webpagetest or http://web.dev/measure. 2. you do NOT have to use the same tech for app and site! :) https://twitter.com/swyx/status/1317635707838496768?lang=en   1317635707838496768 1317635707838496768   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 269] 1436689311315890177 33521530 swyx       1 10 159 0 0 0 en  
1436733804174008321 swyx 33521530 2021-09-11T16:50:06+00:00 in fact i’m -so- not a perfshamer I shall now say the thing I’m not supposed to say: before today you didnt know or care that Notion had a 9.1MB JS marketing site; if it impacted them enough they would’ve fixed it sooner; you may have a fast site but they have 10 million users.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 279] 1436720513049669632 33521530 swyx       0 9 133 0 0   en  
1436776365823598595 swyx 33521530 2021-09-11T19:39:14+00:00 Lighthouse is great but the fact that you can get such wildly different results on the exact same site is just actively counterproductive. The default experience has you “holding it wrong” and none of the impt info is in the screenshot. Dear @ChromeDevTools, you CAN fix this. https://twitter.com/swyx/status/1436776365823598595/photo/1       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 277] 1436733804174008321 33521530 swyx       0 1 38 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]);