tweets

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

7 rows where in_reply_to_screen_name = "ThisIsMissEm" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source, retweet_count, favorite_count, created_at (date)

is_quote_status 1 ✖

  • 0 7

in_reply_to_screen_name 1 ✖

  • ThisIsMissEm · 7 ✖
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
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  
1427988073292476418 Emelia πŸ‘ΈπŸ» 14063149 2021-08-18T13:37:42+00:00 @JessTelford JWTs for external use tend not to solve the problems people think they do; for internal use, or cross authorisation boundaries, they can be good because then you can assert using public/private key cryptography that the token your presented really came from the authorising server       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [13, 293] 1427986367905161221 14063149 ThisIsMissEm       0 1 14 0 0   en  
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  

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