Johannes Ernst
Johannes Ernst
As I'm going through the spec with a fine comb for the purposes of identifying which piece of software has which responsibilities under which circumstances, so we can build a...
I note that those implementations whose actor files we collect at https://fedidevs.org/reference/actor/ also specify a `oauthRegistrationEndpoint` value, which is not mentioned in the AP spec.
The description of `endpoints` says: > This mapping may be nested inside the actor document as the value or may be a link to a JSON-LD document This indirectly appears...
This is a bit nitpicky, but "SHOULD" is part of the controlled vocabulary for the spec, and thus spelled in uppercase. There are many places in the spec where the...
I don't know Docusaurus 2, nor node really, so I don't quite know how to fix it :-)
Consider `https://foo:[email protected]`. How is that supposed to be mapped? If the user component is not permitted, document that explicitly. Alternatively make an example that shows how this is mapped.
Consider `https://foo.example/bar/baz.html`. * Applying the algorithm, this leads to `did:web:foo.example.com:bar:baz.html`. Is that intended? If so, add an example to the doc. If not, be clear it shouldn't be. (I believe...
If the recovery key gets regenerated at some point, stewards cannot distinguish between the "old" and the "new" recovery sheet. Choices: * use time stamp when the recovery secret was...
Take a look at what's in `paradux.datatransfer`, and implement an `s3.py` similarly to the existing implementations. Simply creating the file in that folder should let paradux discover it.
After #12 is implemented, after the configuration image has been updated, right after unmount, we should automatically upload the image to the defined configuration locations, so its backups remain current.