Data source: swyx's twitter data
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1134311153960534016 | 14904098 | 2019-05-31T04:10:28+00:00 | Super curious to see how this works out. Historically I’ve been very skeptical of schema federation and the costs it incurs on an org, so I’m hoping to learn from the community on what works and doesn’t work from this new attempt. https://twitter.com/apollographql/status/1134086759489384449 | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 230] | 1 | 11 | 82 | 0 | 0 | 0 | en |