tweets

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

1 row where favorited = 0, is_quote_status = 0, retweeted = 0 and user = 23795212 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

retweeted 1 ✖

retweet_count 1 ✖

is_quote_status 1 ✖

created_at (date) 1 ✖

quoted_status 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
1436890184449236994 Ben Lesh 👈😎👈 23795212 2021-09-12T03:11:30+00:00 Okay, I've taken the time to articulate all of my thoughts in a single space about the current pipeline proposal. I've also included as much information as I can about functional piping, and the two most popular pipelines. (It's opinionated, sorry) https://benlesh.com/posts/tc39-pipeline-proposal-hack-vs-f-sharp/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 275]             0 143 555 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]);