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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1427988073292476418 | 14063149 | 2021-08-18T13:37:42+00:00 | @JessTelford JWTs for external use tend not to solve the problems people think they do; for internal use, or cross authorisation boundaries, they can be good because then you can assert using public/private key cryptography that the token your presented really came from the authorising server | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 293] | 1427986367905161221 | 14063149 | ThisIsMissEm | 0 | 1 | 14 | 0 | 0 | en |