tweets

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

4 rows where "created_at" is on date 2021-09-08 and in_reply_to_screen_name = "swyx" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: is_quote_status, favorite_count

retweeted 1 ✖

  • 0 4

in_reply_to_screen_name 1 ✖

  • swyx · 4 ✖

created_at (date) 1 ✖

  • 2021-09-08 · 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
1435471481266388993 swyx 33521530 2021-09-08T05:14:05+00:00 Brian makes good points here about where we want provisioning to be implicit vs explicit: we definitely dont want typos to drop db’s but ironically i do raise Begin Data as a form of implicit provisioning of DB https://twitter.com/brianleroux/status/1435324306238619649   1435324306238619649 1435324306238619649   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 211] 1433939106459885570 33521530 swyx       1 0 2 0 0 0 en  
1435749807025541123 swyx 33521530 2021-09-08T23:40:03+00:00 @DotProto @timdorr example: extensions require formal notice to users on transferral of ownership? if you like, limit security features to extensions >1m users for implementation purposes       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [19, 192] 1435748951014223874 33521530 swyx       0 0 1 0 0   en  
1435750019093651460 swyx 33521530 2021-09-08T23:40:54+00:00 @DotProto @timdorr whatever the policy, playing this out a few turns you're basically having to choose between doing this now proactively or being forced to do it from social pressure reactively after a high profile pwning. i'm hopeful that smart folks at Google can figure this one out!       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [19, 288] 1435749807025541123 33521530 swyx       0 0 2 0 0   en  
1435752162911563781 swyx 33521530 2021-09-08T23:49:25+00:00 @DotProto @timdorr as for how much pain is acceptable: pretend you just woke up and the @NYtimes H1 headline is "1.3 million developers hacked via Chrome extension" and you are being called before Congress. what do?       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [19, 217] 1435751957386387462 33521530 swyx       0 0 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]);