tweets
3 rows where favorited = 0, in_reply_to_screen_name = "JoeEmison" and retweeted = 0
This data as json, CSV (advanced)
Suggested facets: is_quote_status, retweet_count, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1469127306048245761 | swyx 33521530 | 2021-12-10T02:10:19+00:00 | @JoeEmison this happened to me *today*. still trying to convince them its not a good idea instead of an example to follow. https://twitter.com/swyx/status/1469092201376354305?s=21 | 1469092201376354305 1469092201376354305 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [11, 146] | 1395784944287461383 | 272692606 | JoeEmison | 1 | 0 | 0 | 0 | 0 | 0 | en | ||||||
| 1469128619716870146 | swyx 33521530 | 2021-12-10T02:15:32+00:00 | @JoeEmison @dmessing something i didnt stick around long enough to understand at Amplify was why people running atop AWS could build a faster experience than Amplify. You could blame CFN/CloudFront, but then @begin does that, with like a team of 4 people. wish i had the time to figure it out. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [21, 293] | 1469052947262754820 | 272692606 | JoeEmison | 0 | 1 | 14 | 0 | 0 | en | ||||||||
| 1469129397365981184 | swyx 33521530 | 2021-12-10T02:18:38+00:00 | @JoeEmison @dmessing @begin thats the easy reaction, but knowing the smart/motivated people in amplify, thats not it. anyway it was above my paygrade. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [28, 150] | 1469128734980587524 | 272692606 | JoeEmison | 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]);