issue_comments
7 rows where "created_at" is on date 2022-10-24 and issue = 1421552095 sorted by updated_at descending
This data as json, CSV (advanced)
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1289776707 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289776707 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M4G5D | simonw 9599 | 2022-10-24T23:29:03Z | 2022-10-24T23:29:03Z | OWNER | I'm going to implement the first version of this token mechanism using permissions that exist already. Right now that's: https://docs.datasette.io/en/0.62/authentication.html#built-in-permissions Here are the shortcuts I'll use for them:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289775162 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289775162 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M4Gg6 | simonw 9599 | 2022-10-24T23:27:00Z | 2022-10-24T23:27:00Z | OWNER | Might be neat for API tokens to be signed with an additional secret than can be rotated independently of But again, I don't want to implement something like that until I see an actual need for it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289774183 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289774183 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M4GRn | simonw 9599 | 2022-10-24T23:25:52Z | 2022-10-24T23:25:52Z | OWNER | ... also, maybe there should be a UI (perhaps on that page) for resetting the Datasette secret? Useful for emergency invalidation of all tokens. No, I'm not going to build that unless someone asks for it. Restarting the server with a fresh secret should be easy enough. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289773634 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289773634 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M4GJC | simonw 9599 | 2022-10-24T23:25:06Z | 2022-10-24T23:25:06Z | OWNER | If you start Datasette without providing a This means any signed API tokens you create will stop working if the server restarts. I think the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289766513 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289766513 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M4EZx | simonw 9599 | 2022-10-24T23:16:00Z | 2022-10-24T23:16:00Z | OWNER | Here's what that example looks like signed:
Note that Datasette doesn't have its own mechanism for signing things for a specific duration yet: https://docs.datasette.io/en/stable/internals.html#sign-value-namespace-default So I'll need to add a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289733483 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289733483 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M38Vr | simonw 9599 | 2022-10-24T22:54:37Z | 2022-10-24T23:12:10Z | OWNER | Token design concept:
Minified version of the above looks like this (101 characters):
The
Then the permissions themselves are two character codes which are shortened versions - so:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289718660 | https://github.com/simonw/datasette/issues/1852#issuecomment-1289718660 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M34uE | simonw 9599 | 2022-10-24T22:35:01Z | 2022-10-24T22:35:01Z | OWNER | Maybe these tokens can be restricted to specific databases and tables when they are first created? Since they're signed tokens, I could bundle a bunch of extra stuff in them - this token is allowed to do these permissions against these tables/rows for example. General wisdom seems to be that 8KB is a sensible maximum length for this kind of token, which is easily long enough to fit in a bunch of database / table / permissions. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 1