tweets
2 rows where display_text_range = "[12, 292]"
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1438969813225799682 | swyx 33521530 | 2021-09-17T20:55:12+00:00 | @temporalio Temporal Server runs as a cluster of 4 scalable @Golang services with pluggable storage, integrated Web UI/CLI, and optional ElasticSearch visibility. "Why so many moving parts?" In a word: Scale. (we're working on simplifying) In 23 minutes: Read/watch https://docs.temporal.io/blog/workflow-engine-principles https://twitter.com/swyx/status/1438969813225799682/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [12, 292] | 1438939235801653249 | 33521530 | swyx | 0 | 0 | 13 | 0 | 0 | 0 | en | |||||||
1475055088359985153 | swyx 33521530 | 2021-12-26T10:45:12+00:00 | @atomiksdev the reality is that what works for one audience wont work for another. this docs writing team has an impossible task writing the One True Explanation for an audience of millions at all experience levels. but its ok - the people who dont resonate with it will go to other resources | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [12, 292] | 1474946634383380480 | 604296890 | atomiksdev | 0 | 0 | 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]);