tweets
3 rows where "created_at" is on date 2021-08-07, retweet_count = 1 and retweeted = 0 sorted by lang
This data as json, CSV (advanced)
Suggested facets: source
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1423897482279329800 | swyx 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 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 99] | 1352579686581190656 | 33521530 | swyx | 0 | 1 | 23 | 0 | 0 | 0 | en | |||||||
1424145861651558405 | swyx 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. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 276] | 0 | 1 | 30 | 0 | 0 | en | |||||||||||
1424154174778843136 | swyx 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 1422553148099645451 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 280] | 1 | 1 | 28 | 0 | 0 | 0 | en |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [tweets] ( [id] INTEGER PRIMARY KEY, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [full_text] TEXT, [retweeted_status] INTEGER, [quoted_status] INTEGER, [place] TEXT REFERENCES [places]([id]), [source] TEXT REFERENCES [sources]([id]), [truncated] INTEGER, [display_text_range] TEXT, [in_reply_to_status_id] INTEGER, [in_reply_to_user_id] INTEGER, [in_reply_to_screen_name] TEXT, [geo] TEXT, [coordinates] TEXT, [contributors] TEXT, [is_quote_status] INTEGER, [retweet_count] INTEGER, [favorite_count] INTEGER, [favorited] INTEGER, [retweeted] INTEGER, [possibly_sensitive] INTEGER, [lang] TEXT, [scopes] TEXT, FOREIGN KEY([retweeted_status]) REFERENCES [tweets]([id]), FOREIGN KEY([quoted_status]) REFERENCES [tweets]([id]) ); CREATE INDEX [idx_tweets_source] ON [tweets] ([source]);