tweets

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

3 rows where "created_at" is on date 2021-09-09 and favorite_count = 3

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: is_quote_status, 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
1435768792395681796 swyx 33521530 2021-09-09T00:55:30+00:00 @DannPetty @designfulltime hey Dann idk if this is still in the 24 hour limit — i assume it has expired — but down here it still says $179! https://twitter.com/swyx/status/1435768792395681796/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [27, 139] 1435377045404635138 22708585 DannPetty       0 0 3 0 0 0 en  
1435801440929427456 swyx 33521530 2021-09-09T03:05:14+00:00 4/ I've enjoyed working with Chapter to set this up. @KyleLadewig and @stflory have an admirable mission to make learning more accessible...chapters are 99% cheaper than other premium online cohort based courses.       Typefully 295366d0fb34352a1961af2413827f072adefdb9 0 [0, 212] 1435801439331241987 33521530 swyx       0 0 3 0 0   en  
1436017409538854913 swyx 33521530 2021-09-09T17:23:25+00:00 @_phosphoricons @mhevery @QwikDev @InfobipShift here is React saying the opposite: https://twitter.com/acdlite/status/977291318324948992?s=21 the real problem is taking for granted that “X is slow” everywhere in all contexts. performance is relative and conditional. if you arent clear on your assumptions you won’t know when your conclusions are invalid.   977291318324948992 977291318324948992   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [48, 321] 1436016082347872257 1305300579804119046 _phosphoricons       1 0 3 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]);