tweets

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

6 rows where "created_at" is on date 2021-09-05 and in_reply_to_screen_name = "swyx" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: retweet_count, favorite_count

retweeted 1 ✖

  • 0 6

in_reply_to_screen_name 1 ✖

  • swyx · 6 ✖

created_at (date) 1 ✖

  • 2021-09-05 · 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
1434389932177559555 swyx 33521530 2021-09-05T05:36:24+00:00 Taken from this excellent compendium of Visual Programming - a very valuable format of blogpost! https://drossbucket.com/2021/06/30/hacker-news-folk-wisdom-on-visual-programming/       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 121] 1434388834087800832 33521530 swyx       0 2 14 0 0 0 en  
1434404727664558080 swyx 33521530 2021-09-05T06:35:11+00:00 Another rarity in this category: the sober retrospective where people close to the matter discuss mistakes made in dev marketing. excellent post by @ahmetb kNative’s initial marketing definitely spoke to too niche a usecase and it suffered for it. https://ahmet.im/blog/knative-positioning/       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 273] 1416543395976151040 33521530 swyx       0 1 6 0 0 0 en  
1434409635444887554 swyx 33521530 2021-09-05T06:54:41+00:00 @patrickjwoods argues here that Community is not Marketing: https://future.a16z.com/community-%E2%89%A0-marketing-why-we-need-go-to-community-not-just-go-to-market/ and elaborates the many ways in which community can do more than product — starting with why people should even show up       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 204] 1367520242415542273 33521530 swyx       0 0 10 0 0 0 en  
1434433245664456704 swyx 33521530 2021-09-05T08:28:30+00:00 @dan_abramov @reactjs @ryanflorence we can happily use d3, ag-grid, pose, xstate, redux, tailwind, etc in all other frameworks. could there be more? probably. i ofc grant that its silly to try to do this for every ui interaction, particularly the concurrent rendering stuff that React is market leading on.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [36, 307] 1434432665617375233 33521530 swyx       0 0 2 0 0   en  
1434435021532803075 swyx 33521530 2021-09-05T08:35:34+00:00 @dan_abramov @reactjs @ryanflorence we all need good custom dropdown/typeahead/datepicker components. does that stuff really need to hook into React? no (i think). yet the best ones seem to all assume React. am i arguing myself into web components? i’m not sure. i like the “headless” nature of hooks.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [36, 302] 1434433245664456704 33521530 swyx       0 0 4 0 0   en  
1434500277567115266 swyx 33521530 2021-09-05T12:54:52+00:00 awesome writeup on adding custom monaco autocompletes for in-app editors! https://twitter.com/tim_nolet/status/1402925458623172611   1402925458623172611 1402925458623172611   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 73] 1321978673868599296 33521530 swyx       1 0 4 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]);