tweets
3 rows where favorite_count = 14 and in_reply_to_screen_name = "swyx"
This data as json, CSV (advanced)
Suggested facets: 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1434389932177559555 | swyx 33521530 | 2021-09-05T05:36:24+00:00 | Taken from this excellent compendium of Visual Programming - a very valuable format of blogpost! https://drossbucket.com/2021/06/30/hacker-news-folk-wisdom-on-visual-programming/ | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 121] | 1434388834087800832 | 33521530 | swyx | 0 | 2 | 14 | 0 | 0 | 0 | en | |||||||
1440797518749601803 | swyx 33521530 | 2021-09-22T21:57:51+00:00 | Quite a few questions on Smart Servers so far. Coincidentally @chris_mccord just published about their path to Phoenix Liveview, which is worth a look for what the Smart Server paradigm can do https://fly.io/blog/how-we-got-to-liveview/ amazing scoop for @flydotio in hiring him!! | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 262] | 1439966955570618376 | 33521530 | swyx | 0 | 0 | 14 | 0 | 0 | 0 | en | |||||||
1450575707826839554 | swyx 33521530 | 2021-10-19T21:32:53+00:00 | Lol - the top pieces of news yesterday according to @newsycombinator: - Apple launching Macbook Pros - Apple launching M1 Pro/M1 Max - my blogpost https://news.ycombinator.com/front?day=2021-10-18 https://twitter.com/swyx/status/1450575707826839554/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 172] | 1450201578330222593 | 33521530 | swyx | 0 | 0 | 14 | 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]);