tweets
1 row where favorited = 0, quoted_status = 1431686864570826753 and retweeted = 0 sorted by lang
This data as json, CSV (advanced)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1431715021868896259 | swyx 33521530 | 2021-08-28T20:27:15+00:00 | NEVER a bad look to acknowledge your weaknesses, flaws, and anti-goals. Better you say it upfront than have users drag it out of you (or worse, disbelieve your denials) It shows confidence that you solve an impt problem well enough you dont need to be all things to all people. https://twitter.com/kilianvalkhof/status/1431686864570826753 | 1431686864570826753 1431686864570826753 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 278] | 1 | 0 | 12 | 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]);