tweets

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

2 rows where user = 676363 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

created_at (date) 2 ✖

user 1 ✖

  • Brian LeRoux · 2 ✖

place 0 ✖

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
1435324306238619649 Brian LeRoux 676363 2021-09-07T19:29:16+00:00 I've been thinking about @swyx's 'self provisioning runtime' thought experiment a bunch. while I do think 'self provisioning' is a nice concept but believe we would want this to be explicit, not implicit. 1/? https://www.swyx.io/self-provisioning-runtime/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 233]             0 2 13 0 1 0 en  
1441062360811143175 Brian LeRoux 676363 2021-09-23T15:30:15+00:00 This in no way assuaged my overall skepticism but super appreciate the hype-free honesty of the current state of "web3". More of this and I'll be waaaay less skeptical. https://twitter.com/iam_preethi/status/1441059558454136834   1441059558454136834 1441059558454136834   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 168]             1 3 22 0 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]);