tweets
4 rows where "created_at" is on date 2021-08-10, favorite_count = 0, is_quote_status = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang
This data as json, CSV (advanced)
Suggested facets: in_reply_to_user_id, in_reply_to_screen_name, retweet_count, retweeted
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1425175777000136706 | swyx 33521530 | 2021-08-10T19:22:38+00:00 | RT @swyx: One thing I've consistently had to relearn in developer marketing: "Talk benefits, not features" doesn't work! Developers are s… | 1361279902889086980 1361279902889086980 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 140] | 0 | 105 | 0 | 0 | 1 | en | ||||||||||
1425208387147419648 | swyx 33521530 | 2021-08-10T21:32:13+00:00 | @venkey_ariv yeah i am looking into usability mainly. thank you! need to research Splunk. looking to standardize terminology about scheduled runs: - Overlap Policy: SKIP, BUFFER_ONE, BUFFER_ALL, ALLOW_ALL to control what happens if a job runs over into the next window | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [13, 270] | 1425206384199536645 | 1010918910 | venkey_ariv | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1425210442134089732 | swyx 33521530 | 2021-08-10T21:40:23+00:00 | @brianleroux whats an underappreciated thing it does well? | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [13, 58] | 1425209754117345284 | 676363 | brianleroux | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1425213339769073666 | swyx 33521530 | 2021-08-10T21:51:54+00:00 | @brianleroux would be fun to build a little cost estimator thing into that arc transpiler tool: "given some load assumptions and this arc file, whats the ballpark cost?" | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [13, 169] | 1425212085185744896 | 676363 | brianleroux | 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]);