Shayne Miel (he/him)
Shayne Miel (he/him)
I am brand new to both Torch and RNNs, but I think my code is correct. I would love feedback on it! What this PR does is calculate the log...
- Added optional `receiver_key` to enable encryption of SETs - Added language in Security Considerations section to describe when SETs MUST be encrypted - Added language in Security Considerations offering...
I am proposing that, when creating a new stream, the receiver should pass the `aud` value, instead of assuming the transmitter already knows it. This issue is specifically tied to...
Some of our endpoints don't have examples. Others do. At least one of them (just below `Table 6: Read Stream Status Errors`) has a few examples that are general to...
When you read a stream's status (GET), you get back a response with two fields: - status - reason When you set a stream's status (POST), you send an object...
The event schemas in the CAEP spec make no mention of a `subject` claim. However, `subject` appears in all of the normative examples. We should consider removing `subject` from the...
In the current SSF spec, the Transmitter can make a `jwks.json` file available to its Receivers. This allows the Transmitter to sign the JWTs that it is sending the Receiver,...
In the StreamConfiguration section, the `description` field says: > An optinal string to describe the properties of the stream. This is useful in multi stream systems to identify the stream...
Please address these comments as part of registering the well known endpoint: https://github.com/protocol-registries/well-known-uris/issues/44#issuecomment-2062849418
The info is not rendering as a bulleted list because of missing newlines