twitter: tweets: 1 row where favorited = 0, is_quote_status = 0, retweet_count = 432, retweeted = 0 and user = 1593171 sorted by lang

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

1 row where favorited = 0, is_quote_status = 0, retweet_count = 432, retweeted = 0 and user = 1593171 sorted by lang

Search:

descending

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
1056594421079261185	sunil pai, inc. 1593171	2018-10-28T17:11:55+00:00	ok so - I took dan's classes/hooks code from react conf, blacked out the 'unnecessary' bits, then colour coded bits by 'concern'. so much nicer. the effect is amplified in more complex components, where concerns are split and mixed across lifecycle methods. https://twitter.com/threepointone/status/1056594421079261185/photo/1				Twitter Web Client 887710c0899816dfe9fb0176eb05d760cbe15732	0	[0, 257]							0	432	1754	0	0	0	en

Advanced export

JSON shape: default, array, newline-delimited, object

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]);