issue_comments: 641059221
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/datasette/issues/823#issuecomment-641059221 | https://api.github.com/repos/simonw/datasette/issues/823 | 641059221 | MDEyOklzc3VlQ29tbWVudDY0MTA1OTIyMQ== | 9599 | 2020-06-09T06:23:51Z | 2020-06-09T06:24:09Z | OWNER | I don't like the "id" requirement. I can think of plenty of situations where a unique ID might not be available: - auth against an external token - an email address or a phone number for example - auth using encrypted tokens - where decrypting the token tells you exactly what permissions that token should have, like in https://blog.thea.codes/building-a-stateless-api-proxy/ | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 635107393 |