home / twitter

tweets

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

3 rows where "created_at" is on date 2021-12-17, is_quote_status = 1 and retweet_count = 0 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: in_reply_to_screen_name, created_at (date)

in_reply_to_user_id 2 ✖

  • 33521530 2
  • 2048741 1

retweet_count 1 ✖

  • - · 3 ✖

is_quote_status 1 ✖

  • 1 · 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
1471750589012856834 swyx 33521530 2021-12-17T07:54:18+00:00 Clubhouse coming out of a brutal 2021 with some life https://twitter.com/pitdesi/status/1471493259046252548   1471493259046252548 1471493259046252548   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 52] 1417896330848968704 33521530 swyx       1 0 3 0 0 0 en  
1471980286921564167 swyx 33521530 2021-12-17T23:07:03+00:00 @shreyas @adanisaureen you can prototype it by putting it in your Twitter location like @jsjoeio did https://twitter.com/dr/status/1374247809730318336   1374247809730318336 1374247809730318336   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [23, 124] 1471964790012612608 2048741 shreyas       1 0 2 0 0 0 en  
1471985415137726477 swyx 33521530 2021-12-17T23:27:25+00:00 @forrestbrazeal Postel's Law ("be conservative in what you do, be liberal in what you accept from others" aka Robustness Principle) becoming relevant as I learn about API design. However, too much defensive coding from too many layers can cause overhead & confusion. https://twitter.com/mfeathers/status/995896831165919232?s=20   995896831165919232 995896831165919232   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [16, 296] 1323643707271213056 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]);
Powered by Datasette · Queries took 4441.631ms