home / twitter

tweets

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

3 rows where "created_at" is on date 2021-10-03 and retweet_count = 1 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: in_reply_to_user_id, in_reply_to_screen_name, is_quote_status

user 1 ✖

  • swyx 3

retweet_count 1 ✖

  • 1 · 3 ✖

quoted_status 1 ✖

  • 1172690454363672577 1

created_at (date) 1 ✖

  • 2021-10-03 · 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
1444556693673701378 swyx 33521530 2021-10-03T06:55:28+00:00 @jlengstorf @astrodotbuild right here with ya :) https://twitter.com/swyx/status/1172690454363672577?s=20   1172690454363672577 1172690454363672577   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [27, 72] 1442707241627385860 15668072 jlengstorf       1 1 14 0 0 0 en  
1444724789994606592 swyx 33521530 2021-10-03T18:03:26+00:00 @JCardenete i will never forget my first boss, an Angular guy, dismissing React out of hand as a "serious framework" because it "doesnt have dependency injection". lol       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [12, 168] 1444701422356877313 562755125 JCardenete       0 1 21 0 0   en  
1444725460697436161 swyx 33521530 2021-10-03T18:06:06+00:00 @jlengstorf @astrodotbuild the built in css transition stuff is cool, but what really sold me was the js motion stores. take a couple minutes and read this: https://svelte.dev/tutorial/tweened see the smooth upgrade from a writable store to a tweened motion store!! progressive upgrade makes animation *fun*.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [27, 298] 1444677444267483142 15668072 jlengstorf       0 1 8 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]);
Powered by Datasette · Queries took 968.461ms