tweets

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

9 rows where "created_at" is on date 2021-08-03, favorite_count = 0 and retweet_count = 0

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: in_reply_to_user_id, in_reply_to_screen_name, 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
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  
1422419942129901574 swyx 33521530 2021-08-03T04:51:56+00:00 @yash_kr_verma i think this could be a good answer but i dont like discussing this thing without numbers. if the delay is <10ms i really don't care. especially if i'm serving API requests, not web pages.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [15, 206] 1422418499343831043 3112402897 yash_kr_verma       0 0 0 0 0   en  
1422431411634507777 swyx 33521530 2021-08-03T05:37:30+00:00 @ThisIsMissEm - i think pqueue as source of truth (with compute being secondary) can make a lot of sense, as opposed to the norm of compute-first and adding persistence/queueing as afterthought - depends what kind of routing - you have to route things to the right queue at least       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [14, 279] 1422429638740135936 14063149 ThisIsMissEm       0 0 0 0 0   en  
1422436468631347202 swyx 33521530 2021-08-03T05:57:36+00:00 @ThisIsMissEm ya i hear you on not everything needing persistence. i wouldnt do this for a CDN or web server, for instance. but could be great for job runner/workflow engine fun fact, @netlify can offer *backfillable* analytics because it logs anonymous visitor statistics for every request.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [14, 293] 1422433377668452370 14063149 ThisIsMissEm       0 0 0 0 0   en  
1422438456353951750 swyx 33521530 2021-08-03T06:05:30+00:00 @ThisIsMissEm @Netlify i mean i did say anonymous. Netlify was well aware of GDPR when launching this thing. lmk if any specifics alarm you and i'd be happy to dig in further as i have some interest in what potential problems there may be https://www.netlify.com/gdpr-ccpa/ https://www.netlify.com/products/analytics/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [23, 287] 1422437143713042439 14063149 ThisIsMissEm       0 0 0 0 0 0 en  
1422438939432869888 swyx 33521530 2021-08-03T06:07:25+00:00 @ThisIsMissEm @Netlify yes schema evolution was a concern in the thread i responded to today (https://news.ycombinator.com/item?id=28034882) which prompted revival of this tweet :) bottom line is frameworks can help with coding hygiene and i'm trying to frame @temporalio as a framework to help (https://www.youtube.com/watch?v=kkP899WxgzY)       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [23, 299] 1422437929071300611 14063149 ThisIsMissEm       0 0 0 0 0 0 en  
1422442377491279872 swyx 33521530 2021-08-03T06:21:05+00:00 @ThisIsMissEm @Netlify ah the beauty of unilateral global regulation: distributes all the compliance costs, centralizes all the fines.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [23, 134] 1422441506221215763 14063149 ThisIsMissEm       0 0 0 0 0   en  
1422580099199602688 swyx 33521530 2021-08-03T15:28:20+00:00 @_2c2c @temporalio @tef_ebooks is an all-round great dev blogger + follow his twitter for crow pics       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [19, 99] 1422577505685282818 2461201788 _2c2c       0 0 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]);