tweets
3 rows where "created_at" is on date 2021-08-17 and in_reply_to_screen_name = "andrewingram" sorted by id
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1427669027913015300 | swyx 33521530 | 2021-08-17T16:29:55+00:00 | @andrewingram @_philpl i have historically underestimated how crazy things can get but my sense is this would not be feasible given how Apollo relies on interop with the rest of the GraphQL ecosystem. More likely that they define a proprietary superset, which effectively each vendor needs to do anyway. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [23, 303] | 1427667480139403265 | 9164512 | andrewingram | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1427670290167865347 | swyx 33521530 | 2021-08-17T16:34:56+00:00 | @andrewingram its also an interesting name collision with @edgeandnode's @graphprotocol, also called The Graph everyone trying to build the One Graph to rule them all 👀 (and ofc @onegraphio is already all the way there) | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [14, 220] | 1427654400814862354 | 9164512 | andrewingram | 0 | 0 | 7 | 0 | 0 | en | ||||||||
1427673966949277697 | swyx 33521530 | 2021-08-17T16:49:33+00:00 | @andrewingram @apollographql i mean, paying them money/developing with them is betting on them. Relay may have the hearts of individual developers but they dont have an enterprise sales team and coordinated marketing/devrel effort. not saying that's required (see: React) but it surely helps | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [29, 292] | 1427645962860875786 | 9164512 | andrewingram | 0 | 0 | 2 | 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]);