home / twitter

twitter

Data source: swyx's twitter data

Custom SQL query returning 2 rows (hide)

Query parameters

This data as json, CSV

idusercreated_atfull_textretweeted_statusquoted_statusplacesourcetruncateddisplay_text_rangein_reply_to_status_idin_reply_to_user_idin_reply_to_screen_namegeocoordinatescontributorsis_quote_statusretweet_countfavorite_countfavoritedretweetedpossibly_sensitivelangscopes
1431072897099911169 33521530 2021-08-27T01:55:41+00:00 @heathedan for example, you dont have to spend 2 months researching the right choice if you can just try each in turn until one fits. key is to make it cheap to switch; have a decoupled test suite, don’t tie your brand/identity to any one solution, seek “good enough” https://twitter.com/swyx/status/1221129594146840577?s=21   1221129594146840577   95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [11, 291] 1431070301308211203 784577340638625792 heathedan       1 0 5 0 0 0 en  
1432504165440184321 33521530 2021-08-31T00:43:02+00:00 @shreyas “Good Enough” is better than “Best”: https://twitter.com/swyx/status/1221129594146840577?s=21   1221129594146840577   95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [9, 70] 1432501769989357568 2048741 shreyas       1 0 4 0 0 0 en  
Powered by Datasette · Queries took 2.55ms · Data source: swyx's twitter data