tweets
6 rows where favorite_count = 29, possibly_sensitive = 0 and user = 33521530
This data as json, CSV (advanced)
Suggested facets: source, is_quote_status, retweet_count, created_at (date)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1429888354192019476 | swyx 33521530 | 2021-08-23T19:28:44+00:00 | 🆕 Blog: Why Isn't Usage Based Billing A Bigger Category? https://dev.to/swyx/why-isn-t-usage-based-billing-a-bigger-category-m8b | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 81] | 0 | 2 | 29 | 0 | 0 | 0 | en | ||||||||||
1436628297039982592 | swyx 33521530 | 2021-09-11T09:50:51+00:00 | Incredible discussion of platform economics and YouTube optimization by @veritasium: https://www.youtube.com/watch?v=S2xHZPH5Sng Non-obvious conflict: subscriptions (follows) vs recommendations (feed). Every ad supported platform wants to maximize time on site, which means the feed eventually wins. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 280] | 0 | 3 | 29 | 0 | 0 | 0 | en | ||||||||||
1444851185668673541 | swyx 33521530 | 2021-10-04T02:25:41+00:00 | Sending out newsletter soon! https://www.getrevue.co/profile/swyx?via=twitter-profile-webview Including preview of my latest piece: "Eating the Cloud from Outside In" TL;DR - AWS is playing Chess, but @Cloudflare is playing Go https://twitter.com/swyx/status/1444851185668673541/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 187] | 0 | 0 | 29 | 0 | 0 | 0 | en | ||||||||||
1456024072052215814 | swyx 33521530 | 2021-11-03T22:22:45+00:00 | #NewProfilePic thanks to @samjulien at the @cascadiajs @auth0 booth! https://twitter.com/swyx/status/1456024072052215814/photo/1 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 68] | 0 | 4 | 29 | 0 | 0 | 0 | en | ||||||||||
1460365662509928451 | swyx 33521530 | 2021-11-15T21:54:40+00:00 | *starts playing Adele* https://twitter.com/kentcdodds/status/1460294601747550210 | 1460294601747550210 1460294601747550210 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 47] | 1460365475808874496 | 33521530 | swyx | 1 | 0 | 29 | 0 | 0 | 0 | en | ||||||
1461046537224527877 | swyx 33521530 | 2021-11-17T19:00:14+00:00 | @Netlify My previous post on the Series B -> C transition is here: https://dev.to/swyx/working-at-a-startup-from-series-b-to-c-445p I wonder if anyone's written about what its like from C -> D, would love to read. Am hoping to write the A -> B experience someday :) | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [9, 235] | 1461043514641305600 | 33521530 | swyx | 0 | 2 | 29 | 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]);