tweets

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

3 rows where user = 90488576

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source, retweeted

created_at (date) 3 ✖

is_quote_status 2 ✖

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
1319423392852832256 Charity Majors 90488576 2020-10-22T23:40:25+00:00 "treat complacency like cancer" -- this piece is aces. by @appyg99, clearly a girl after my own heart. https://apoorvagovind.substack.com/p/how-to-waste-your-career-one-comfortable       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 126]             0 40 195 0 1 0 en  
1426405785832095749 Charity Majors 90488576 2021-08-14T04:50:15+00:00 Ever wondered what columnar databases are, or peered skeptically at my claim that you basically can't have observability without one? Read this piece, and wonder no more. (Also HOLY SHIT this blew my mind and is my favorite article of 2021 to date! Five stars ⭐⭐⭐⭐⭐) 🤣 https://twitter.com/honeycombio/status/1425853831775129601   1425853831775129601 1425853831775129601 San Francisco 5a110d312052166f Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 269]             1 43 243 0 1 0 en  
1450802073860132864 Charity Majors 90488576 2021-10-20T12:32:23+00:00 good morning kittens, guess what honeycomb been up to? ? oh not much really, we've only just STAVED OFF OUR OWN INEVITABLE DEMISE AND DESTRUCTION, 🔥YET AGAIN🔥. We can hardly even fail if we try for another two, three years now! Take that, heat death of the universe!🪐🌑 💜 https://twitter.com/honeycombio/status/1450795843863334922     San Francisco 5a110d312052166f Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 271]             1 27 701 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]);