issue_comments: 1289733483
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/1852#issuecomment-1289733483 | https://api.github.com/repos/simonw/datasette/issues/1852 | 1289733483 | IC_kwDOBm6k_c5M38Vr | 9599 | 2022-10-24T22:54:37Z | 2022-10-24T23:12:10Z | OWNER | Token design concept: ```json { "t": { "a": ["ir", "ur", "dr"], "d": { "fixtures": ["ir", "ur", "dr"] }, "t": { "fixtures": { "searchable": ["ir"] } } } } ``` That JSON would be minified and signed. Minified version of the above looks like this (101 characters): `{"t":{"a":["ir","ur","dr"],"d":{"fixtures":["ir","ur","dr"]},"t":{"fixtures":{"searchable":["ir"]}}}}` The `"t"` key shows this is a token that as a default API key. `"a"` means "all" - these are permissions that have been granted on all tables and databases. `"d"` means "databases" - this is a way to set permissions for all tables in a specific database. `"t"` means "tables" - this lets you set permissions at a finely grained table level. Then the permissions themselves are two character codes which are shortened versions - so: - `ir` = `insert-row` - `ur` = `update-row` - `dr` = `delete-row` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1421552095 |