tweets
10 rows where favorited = 0 and in_reply_to_user_id = 232076816
This data as json, CSV (advanced)
Suggested facets: source, favorite_count, lang, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1421693817523105792 | swyx 33521530 | 2021-08-01T04:46:34+00:00 | @ritakozlov_ CAT. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 17] | 1421489656827301896 | 232076816 | ritakozlov_ | 0 | 0 | 4 | 0 | 0 | und | ||||||||
1425253637979181061 | swyx 33521530 | 2021-08-11T00:32:01+00:00 | @ritakozlov_ it does look good! the problem (that we are also wrestling with) is when you tie API to cron its hard to do some things like "every 3rd wednesday" or "last day of the month" as this code sample was probably trying to do also we're designing for long running wfs that may overlap https://twitter.com/swyx/status/1425253637979181061/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [13, 293] | 1425240576975278080 | 232076816 | ritakozlov_ | 0 | 0 | 5 | 0 | 0 | 0 | en | |||||||
1425266629017890816 | swyx 33521530 | 2021-08-11T01:23:39+00:00 | @ritakozlov_ i mean sure that works too i wouldnt overreact 😅 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 61] | 1425265547550158848 | 232076816 | ritakozlov_ | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1425267775967096832 | swyx 33521530 | 2021-08-11T01:28:12+00:00 | @ritakozlov_ @jasnell reject cloud embrace corn | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [22, 47] | 1425267547469848584 | 232076816 | ritakozlov_ | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1425561725877637121 | swyx 33521530 | 2021-08-11T20:56:15+00:00 | @ritakozlov_ @_AlbertZhao well look at that! i missed the L/W additions. awesome! | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [26, 81] | 1425560858353049601 | 232076816 | ritakozlov_ | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1430211358188965893 | swyx 33521530 | 2021-08-24T16:52:14+00:00 | @ritakozlov_ @threepointone ayyyy congrats very nice!! | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [28, 54] | 1430204719885029379 | 232076816 | ritakozlov_ | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1435473821490950144 | swyx 33521530 | 2021-09-08T05:23:23+00:00 | @ritakozlov_ oh amazing! always wondered how people do this. idk if this is feedback or not but calling it “vanity domains” trivialized a fairly important feature for me. if i ran a hosting platform, id want every user of mine to run on their own domain, own their own destiny. not vanity. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 290] | 1435228859897679878 | 232076816 | ritakozlov_ | 0 | 0 | 3 | 0 | 0 | en | ||||||||
1443112483670032402 | swyx 33521530 | 2021-09-29T07:16:42+00:00 | @ritakozlov_ buy Netlify pls thx | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 32] | 1442979853054058508 | 232076816 | ritakozlov_ | 0 | 0 | 3 | 0 | 0 | en | ||||||||
1470149275849924610 | swyx 33521530 | 2021-12-12T21:51:16+00:00 | @ritakozlov_ i feel like this has a 50% chance of being a really underrated idea and 50% being a reference to a meme 😂 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 118] | 1470148371751055366 | 232076816 | ritakozlov_ | 0 | 0 | 2 | 0 | 0 | en | ||||||||
1470151235244158978 | swyx 33521530 | 2021-12-12T21:59:03+00:00 | @ritakozlov_ will give it a try! i cook a fair bit too but i stick to a very small set of things i know (and premarinated supermarket chicken haha) | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 147] | 1470150583344680964 | 232076816 | ritakozlov_ | 0 | 0 | 1 | 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]);