tweets

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

1 row where display_text_range = "[32, 178]", lang = "en", source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" and user = 33521530 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

  • swyx · 1 ✖

lang 1 ✖

display_text_range 1 ✖

  • [32, 178] · 1 ✖

created_at (date) 1 ✖

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
1425210747668160515 swyx 33521530 2021-08-10T21:41:36+00:00 @janbhwilhelm @flybayer @skn0tt yea it does look pretty sweet! Does it offer an API to "backfill" i.e. manually retry jobs that failed or didnt start because the system was down?       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [32, 178] 1425207824322371585 958043149275934720 janbhwilhelm       0 0 5 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]);