tweets

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

1 row where "created_at" is on date 2021-11-18, favorite_count = 19 and source = "95f3aaaddaa45937ac94765e0ddb68ba2be92d20"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

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
1461420430137257986 swyx 33521530 2021-11-18T19:45:57+00:00 @jkup tried it, for me its just not worth it unless you are literally not paying attention to the stream. standard twitch streaming is full of interruptions, because naturally viewers want to interact with you live for it to be a good stream, but its terrible for focus       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [6, 269] 1461403751516971008 255634108 jkup       0 0 19 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]);