tweets

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

5 rows where in_reply_to_screen_name = "anildash" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: favorite_count

created_at (date) 5 ✖

user 1 ✖

in_reply_to_screen_name 1 ✖

  • anildash · 5 ✖
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
1423896518440804355 swyx 33521530 2021-08-07T06:39:19+00:00 @anildash if you go to the dark side it might even cost you an arm and a leg       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [10, 76] 1423878718695563267 36823 anildash       0 0 3 0 0   en  
1431045425696542723 swyx 33521530 2021-08-27T00:06:31+00:00 @anildash I was assured it could not get thicker than this Rick was slick but he missed And we last partied back in ‘19 (hold up, it fits)       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [10, 138] 1431028108468101126 36823 anildash       0 0 2 0 0   en  
1447366630246285316 swyx 33521530 2021-10-11T01:01:10+00:00 @anildash i find the spanish “Salud” so nice and ironic. Toast to health, then drink tiny amounts of poison!       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [10, 108] 1447296607591018500 36823 anildash       0 0 4 0 0   en  
1453532106563338241 swyx 33521530 2021-10-28T01:20:34+00:00 @anildash honestly out of the possible range of things to emerge from before you were famous, this has got to be up there in terms of “makes you relatable and even more endearing”       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [10, 179] 1453368190763929602 36823 anildash       0 0 2 0 0   en  
1474103628918972417 swyx 33521530 2021-12-23T19:44:27+00:00 @anildash not that i have any practical experience with this tech but ive found it surprising that many companies that start out with CRDT end up rewriting to OT for a variety of implementation reasons. specific cases elude me right now but just wanted to flag in case you have an opinion       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [10, 288] 1474086639915909121 36823 anildash       0 1 4 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]);