tweets

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

3 rows where "created_at" is on date 2021-08-03 and in_reply_to_screen_name = "sgrove"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: favorite_count

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
1422419304096485384 swyx 33521530 2021-08-03T04:49:24+00:00 @sgrove @temporalio you mean CPS? continuation passing? if so then no... just `await` an `async` workflow and the framework handles the "blocking"       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [20, 146] 1422418903381078021 14435843 sgrove       0 0 0 0 0   en  
1422426258676195328 swyx 33521530 2021-08-03T05:17:02+00:00 @sgrove @ejames_c @temporalio Ah. I couldnt find a very good definition of CSP in Go (the go docs are way too brief) but yes - we have Signals and Queries https://docs.temporal.io/docs/go/signals/ i was also referring to "synchronous" started workflows, which solve a concern people had for queue-first systems like i proposed       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [30, 309] 1422423624682655748 14435843 sgrove       0 0 1 0 0 0 en  
1422629085101006848 swyx 33521530 2021-08-03T18:42:59+00:00 @sgrove @ejames_c @temporalio Tracked it down for those following along: https://www.cs.cmu.edu/~crary/819-f09/Hoare78.pdf       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [30, 96] 1422583140845903876 14435843 sgrove       0 0 0 0 0 0 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]);