home / twitter

twitter

Data source: swyx's twitter data

Custom SQL query returning 4 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
1434287058596597762 33521530 2021-09-04T22:47:37+00:00 RT @pullara: Let me get this straight... @jhuber had the GENIUS idea to buy @YouTube, debated internally for a bit, got pushback... ...… 1433880742682112001     9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 140]             1 12 0 0 1   en  
1437095732436258816 33521530 2021-09-12T16:48:17+00:00 @jamonholmgren yes! I call this Lampshading. Ignorance can be Power, when wielded correctly. https://twitter.com/swyx/status/1238321393374298112   1238321393374298112   9335de48b3673c3f69433a34861c115d1d382be3 0 [15, 117] 1437089665018826754 30273948 jamonholmgren       1 1 4 0 0 0 en  
1439976152995545090 50136899 2021-09-20T15:34:02+00:00 "GraphQL helps solve the overfetching problem. In practice, I think the importance of this is overhyped unless you are Facebook or Airbnb." 👏👏👏 https://twitter.com/swyx/status/1439966955570618376   1439966955570618376   9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 144]             1 29 342 0 1 0 en  
1467343720936792071 727704217012604928 2021-12-05T04:02:59+00:00 I'm not a frequent podcast listener, but I am _loving_ these deep-dive discussions that Swyx is recording. Great guests, thorough discussion of meaningful topics, and some really good insight into the state of our industry. https://twitter.com/swyx/status/1467304180003917824   1467304180003917824   9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 223]             1 5 45 1 1 0 en  
Powered by Datasette · Queries took 2.243ms · Data source: swyx's twitter data