tweets
1 row where "created_at" is on date 2021-12-21 and display_text_range = "[19, 272]" sorted by lang
This data as json, CSV (advanced)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1473395963696140288 | swyx 33521530 | 2021-12-21T20:52:26+00:00 | @dvassallo @circle they released group chat, which is good but needs to be for "rooms" than individuals. then the hard part is overcoming network effect of Discord. even then, may be strategically the wrong move if the bet is just to be extremely good at async community. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [19, 272] | 1473355746385412096 | 24179991 | dvassallo | 0 | 0 | 1 | 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]);