home / twitter

tweets

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

4 rows where favorite_count = 49 and possibly_sensitive = 0 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source, is_quote_status, favorited, retweeted, created_at (date)

possibly_sensitive 1 ✖

  • - · 4 ✖

lang 1 ✖

  • en 4

favorite_count 1 ✖

  • 49 · 4 ✖
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
1426537001868685314 Rajat Gupta 1297539457696980994 2021-08-14T13:31:39+00:00 If you mugged up the rules of React Hooks like me - watch this. Great explanation of the internals by @swyx https://youtu.be/KJP1E-Y-xyo       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 133]             0 10 49 0 1 0 en  
1434106223721426945 Svelte Society 🧡 1176969867733479424 2021-09-04T10:49:02+00:00 Svelte Summit Fall 2021 is happening on November 20th! CFPs are open as well! https://twitter.com/kevmodrome/status/1434105682077364224   1434105682077364224 1434105682077364224   Tweetbot for Mac 2d56427825d31a620d10acb51615805f894c90f6 0 [0, 77]             1 11 49 0 1 0 en  
1452046180683161609 swyx 33521530 2021-10-23T22:56:01+00:00 it worries me that there’s an uncritical acceptance of @Reactjs conclusions without examining if those assumptions apply to you. React is verbose React is successful Must be verbose to be successful Here’s my attempt to articulate more timeless lessons than “2 way binding bad”: https://twitter.com/swyx/status/1383516418205835264   1383516418205835264 1383516418205835264   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 280]             1 2 49 0 0 0 en  
1466544085041233922 Jason Laster 312750384 2021-12-02T23:05:31+00:00 Would you like to help scale the craziest backend I’ve ever seen? http://Replay.io's tech stack is TS, EC2, K8S, and Pulumi, but what makes it fun is that one debugging session can be anywhere from one to one hundred browsers co-located across several instances.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 270]             0 21 49 1 1 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]);
Powered by Datasette · Queries took 2148.388ms