tweets
3 rows where display_text_range = "[0, 304]"
This data as json, CSV (advanced)
Suggested facets: 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1210295490853490688 | swyx 33521530 | 2019-12-26T20:25:05+00:00 | ✍️In Defense of Hammers 🔨 Why "Right Tool for Most Jobs" beats "Right Tool for the Job" 🔗https://www.swyx.io/writing/hammers Long overdue tweet-turned-blogpost 😅 shoutouts due to @laurieontech, @tlakomy, @wking__, @rmngrc and everyone who commented & helped me think through this! ❤️ https://twitter.com/swyx/status/1171549189064613888 https://twitter.com/swyx/status/1210295490853490688/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 304] | 1 | 22 | 82 | 0 | 0 | 0 | en | ||||||||||
1424502535411224581 | swyx 33521530 | 2021-08-08T22:47:25+00:00 | My take on Why @TailwindCSS: https://www.swyx.io/why-tailwind/ Probably obvious to experts, but it's the top organic Google result for "Why Tailwind" now. I think more people should write straightforward "Why X" or "What is X" posts. You don't always have to write earthshattering theses. https://twitter.com/Tyler_Potts_/status/1424481436766199819 https://twitter.com/swyx/status/1424502535411224581/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 304] | 1 | 30 | 226 | 0 | 0 | 0 | en | ||||||||||
1468156417248923650 | swyx 33521530 | 2021-12-07T09:52:21+00:00 | Excellent answer from @yongfook on why too many people “building an audience first” w/o making anything of substance on @IndieHackers. Like most writers, I also don’t have a problem with the audience first approach. But it’s easy to overdo the “in public” and forget the “build”. https://twitter.com/jakobgreenfeld/status/1468143869426606081 https://twitter.com/swyx/status/1468156417248923650/photo/1 | 1468143869426606081 1468143869426606081 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 304] | 1 | 6 | 35 | 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]);