tweets

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

10 rows where in_reply_to_screen_name = "acdlite" and is_quote_status = 0 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, source, retweet_count, retweeted, lang

favorite_count 8 ✖

is_quote_status 1 ✖

in_reply_to_screen_name 1 ✖

  • acdlite · 10 ✖
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
1421225521178763266 swyx 33521530 2021-07-30T21:45:43+00:00 @acdlite @reactjs ya i see fixtures as "manual tests" that complement e2e/unit/integration testing. By all means automate everything if you can, but there's a lot of stuff that can't be automated, particularly bugs we don't know about yet. Fixtures help reduce the activation energy to repro bugs!       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [18, 298] 1421224201181143040 21782915 acdlite       0 0 4 0 0   en  
1421229828636774400 swyx 33521530 2021-07-30T22:02:50+00:00 @acdlite @reactjs gotcha, ok will not emphasize their relationship to testing going forward, thank you       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [18, 102] 1421226595994456065 21782915 acdlite       0 0 1 0 0   en  
1421233345716002820 Andrew Clark 21782915 2021-07-30T22:16:49+00:00 @swyx @reactjs Any test that you don't run continuously is destined to break without anyone noticing       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [15, 100] 1421232855024349186 21782915 acdlite       0 4 16 0 1   en  
1421234899181215751 swyx 33521530 2021-07-30T22:22:59+00:00 @acdlite @reactjs yes this does make sense! fixtures that don’t work bc they are out of date are just dead weight. continuous e2e on them is a great principle. and no i totally get that you just want to offer the right perspective since, well, you work on the team 😂 so it is hugely appreciated       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [18, 295] 1421234029983059972 21782915 acdlite       0 0 0 0 0   en  
1432194752267505666 swyx 33521530 2021-08-30T04:13:32+00:00 @acdlite it was very artificial for sure but fits a general pattern of Hollywood hero movies keep bailing out Cap-like decisions with low probability outcomes that validate them. kinda toxic for collective psyche. one of my fave essays on the topic btw https://www.scribd.com/document/444948887/The-Philosophy-of-Civil-War-Part-1       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [9, 277] 1432134218952450054 21782915 acdlite       0 0 3 0 0 0 en  
1446319953984983044 swyx 33521530 2021-10-08T03:42:03+00:00 @acdlite using tfw when you meant mfw       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [9, 37] 1446133172497002498 21782915 acdlite       0 0 5 0 0   en  
1447623242236129285 swyx 33521530 2021-10-11T18:00:51+00:00 @acdlite What's stopping you from coding like this? https://twitter.com/swyx/status/1447623242236129285/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [9, 51] 1447377622753763336 21782915 acdlite       0 1 198 0 0 0 en  
1451410103001698305 swyx 33521530 2021-10-22T04:48:29+00:00 @acdlite its all opaque anyway, that was always the point       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [9, 57] 1451310475724169223 21782915 acdlite       0 0 1 0 0   en  
1468757809437151235 swyx 33521530 2021-12-09T01:42:04+00:00 @acdlite @trueadm fixins gang represent       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [18, 39] 1468737891631349761 21782915 acdlite       0 0 5 0 0   en  
1466139598812188674 swyx 33521530 2021-12-01T20:18:14+00:00 @acdlite https://twitter.com/swyx/status/1466139598812188674/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [8, 8] 1466137489337466880 21782915 acdlite       0 0 10 0 0 0 und  

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]);