tweets
5 rows where "created_at" is on date 2021-09-11 and retweet_count = 1 sorted by lang
This data as json, CSV (advanced)
Suggested facets: user, source, is_quote_status
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1436520685778530307 | AWS Weweases Made Howwibwe 1436382868591165445 | 2021-09-11T02:43:15+00:00 | AWS PawawwewCwustew nyow suppowts cwustew manyagement thwough Amazon API Gateway Amazon PawawwewCwustew is a fuwwy suppowted and maintainyed open souwce cwustew manyagement toow that makes it easiew fow scientists, weseawchews, and IT adminyist... https://aws.amazon.com/about-aws/whats-new/2021/09/aws-parallelcluster-cluster-management-api-gateway/ | AWS Cwoud Weweases 7a22e1ca18d57e07b81ea13350e2b9f2cade0008 | 0 | [0, 272] | 0 | 1 | 5 | 0 | 0 | 0 | en | ||||||||||
1436594934002458626 | swyx 33521530 | 2021-09-11T07:38:17+00:00 | I’d really love to hear behind the scenes on GitHub’s decision to launch this shortcut. The obvious downside: launching an expensive action on a single keypress may negatively surprise users. The upside: the barrier to using Codespaces can’t be lower. I use it once a day now. https://twitter.com/github/status/1425505817827151872 | 1425505817827151872 1425505817827151872 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 278] | 1 | 1 | 80 | 0 | 0 | 0 | en | |||||||||
1436697907453779968 | swyx 33521530 | 2021-09-11T14:27:28+00:00 | @leeerob i was -very- excited about RSCs in December 2020 now just kinda confused until it ships and further cements Next.js’ position as the only logical React metaframework to bet on Nextjs’ platform capture both up and down the stack is just amazing to watch | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [9, 264] | 1436695781172551684 | 81712767 | leeerob | 0 | 1 | 19 | 0 | 0 | en | ||||||||
1436714003997331457 | swyx 33521530 | 2021-09-11T15:31:26+00:00 | @slightlylate i can only imagine. you do perform an important public service when you do these so all i can say is thank you. im wondering if it is worth codifying in a “slightlylatehouse” tool where all your usual commentary is templatized. the green circles need a credible alternative. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [14, 289] | 1436712687367426050 | 229237555 | slightlylate | 0 | 1 | 1 | 0 | 0 | en | ||||||||
1436776365823598595 | swyx 33521530 | 2021-09-11T19:39:14+00:00 | Lighthouse is great but the fact that you can get such wildly different results on the exact same site is just actively counterproductive. The default experience has you “holding it wrong” and none of the impt info is in the screenshot. Dear @ChromeDevTools, you CAN fix this. https://twitter.com/swyx/status/1436776365823598595/photo/1 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 277] | 1436733804174008321 | 33521530 | swyx | 0 | 1 | 38 | 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]);