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
1435895069098356736 33521530 2021-09-09T09:17:16+00:00 @dunkhippo33 devtools angels! https://twitter.com/swyx/status/1357105644810063873?s=21   1357105644810063873   574fe4fa937eeb131136f7e3678f32d4ff3078d5 0 [13, 53] 1435829987366506496 14756283 dunkhippo33       1 0 2 0 0 0 de  
1436017409538854913 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   95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [48, 321] 1436016082347872257 1305300579804119046 _phosphoricons       1 0 3 0 0 0 en  
Powered by Datasette · Queries took 88.406ms · Data source: swyx's twitter data