Data source: swyx's twitter data
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |