home / twitter

tweets

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

3 rows where favorite_count = 99 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: retweeted

created_at (date) 3 ✖

  • 2021-08-10 1
  • 2021-10-08 1
  • 2021-10-12 1

user 2 ✖

  • swyx 2
  • Will Larson 1

source 1 ✖

  • Twitter Web App · 3 ✖

favorite_count 1 ✖

  • 99 · 3 ✖
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
1425204981804650496 swyx 33521530 2021-08-10T21:18:41+00:00 Need research help: What is the best job scheduling/cronjob system you've used and what's one thing you LOVE about it?       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 118]             0 6 99 0 0   en  
1446525397508657155 Will Larson 2330381 2021-10-08T17:18:24+00:00 Systems thinking is my fav thinking tool, but many of my largest reasoning errors stemmed from surface use ("here's an intuitive mental model") while skipping the details ("comparing outputs of an explicit model against real behavior"). Some lessons! https://lethain.com/how-to-safely-think-in-systems/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 275]             0 17 99 0 1 0 en  
1448024106633363456 swyx 33521530 2021-10-12T20:33:44+00:00 This year I've done a total 180 on open source strategy. Remember Elastic making a fuss with "Amazon: NOT OK"? I was quite persuaded. If MongoDB, Redis, Cockroach, Confluent relicensed and do fine, maybe SSPL just becomes acceptable "open source". Now I think MIT is just fine.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 279]             0 11 99 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]);
Powered by Datasette · Queries took 1408.404ms