twitter: tweets: 1 row where quoted_status = 1468143869426606081 sorted by lang

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

1 row where quoted_status = 1468143869426606081 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
1468156417248923650	swyx 33521530	2021-12-07T09:52:21+00:00	Excellent answer from @yongfook on why too many people “building an audience first” w/o making anything of substance on @IndieHackers. Like most writers, I also don’t have a problem with the audience first approach. But it’s easy to overdo the “in public” and forget the “build”. https://twitter.com/jakobgreenfeld/status/1468143869426606081 https://twitter.com/swyx/status/1468156417248923650/photo/1		1468143869426606081 1468143869426606081		Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20	0	[0, 304]							1	6	35	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]);