home / twitter

twitter

Data source: swyx's twitter data

Custom SQL query returning 3 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
1423897482279329800 33521530 2021-08-07T06:43:09+00:00 omg heres the latest IETF spec with tons more all professionally analyzed! https://www.ietf.org/id/draft-peabody-dispatch-new-uuid-format-01.html https://twitter.com/swyx/status/1423897482279329800/photo/1       95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 99] 1352579686581190656 33521530 swyx       0 1 23 0 0 0 en  
1424145861651558405 33521530 2021-08-07T23:10:07+00:00 Not everything is an infinite game. I think people are too easy on themselves when they learn this concept. The more that infinite game mentality diffuses into popular consciousness, the more valuable it becomes to play lots of finite games. Life, after all, is one of them.       1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 276]             0 1 30 0 0   en  
1424154174778843136 33521530 2021-08-07T23:43:09+00:00 TLDR of @cloudflare's solution: - introduce intuitive "locking" behavior on in-/out-bound messages based on storage operations - in-memory cache for speed and coalescing multiple writes - opt-outs for latency/memory efficiency - no breaking changes detailed yet accessible read! https://twitter.com/KentonVarda/status/1422553148099645451   1422553148099645451   1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 280]             1 1 28 0 0 0 en  
Powered by Datasette · Queries took 2.733ms · Data source: swyx's twitter data