tweets

This is data scraped from swyx's timeline! See blog post

6 rows where "created_at" is on date 2021-10-27, favorite_count = 0, is_quote_status = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: retweet_count

is_quote_status 1 ✖

created_at (date) 1 ✖

  • 2021-10-27 · 6 ✖
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
1453188758518394888 swyx 33521530 2021-10-27T02:36:13+00:00 @ThisIsMissEm @stubailo @stolinski no because the primary action is "signal", with an option to start if signaling a nonexistent workflow. its kinda niche       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [35, 154] 1453187706557763588 14063149 ThisIsMissEm       0 0 0 0 0   en  
1453191338581585921 swyx 33521530 2021-10-27T02:46:28+00:00 @_changxu @BrendanFalk i am no stranger to long running jobs whether it is at work or for personal stuff       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [23, 104] 1453190863555686401 14806290 _changxu       0 0 0 0 0   en  
1453400900697874433 swyx 33521530 2021-10-27T16:39:12+00:00 @stubailo @stolinski responding quickly can be done with a short workflow or signalling into and querying out of a long workflow. both are fine, so long as it isn't realtime. i have a nextjs sample here that shows how you can embed a temporal client in a serverless endpoint https://github.com/temporalio/samples-typescript/tree/main/nextjs-ecommerce-oneclick       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [21, 301] 1453394921470132224 12767662 stubailo       0 0 0 0 0 0 en  
1453403681710215169 swyx 33521530 2021-10-27T16:50:15+00:00 @andrewingram i wonder if anyone has written a "You May Not Need Foo" blogpost yet, with constructive suggestions. i think i'm just blind + lazy + unimaginative to better ideas       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [14, 176] 1453402880547954690 9164512 andrewingram       0 0 0 0 0   en  
1453478581644902401 swyx 33521530 2021-10-27T21:47:52+00:00 @rubnvp @mattlovesjenni @chriscoyier honestly yeah i have the image pain point too, but have just been living with it :(       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [37, 120] 1453464365470994439 885512094 rubnvp       0 0 0 0 0   en  
1453489774073765888 swyx 33521530 2021-10-27T22:32:21+00:00 RT @swyx: The primary beneficiary of you being #1 on Product Hunt is Product Hunt. The primary beneficiary of you being Employee of the Mo… 1284597930398105600 1284597930398105600     Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 140]             0 14 0 0 1   en  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);