-
# Context
The Base ZTDF specification includes a yet to be implemented `tdf_spec_version` field. This version field is sufficient in the context of of the OpenTDF ecosystem, but we also want to sup…
-
https://spec.matrix.org/v1.1/client-server-api/#user-room-and-group-mentions
![image](https://user-images.githubusercontent.com/1342360/143858062-59a7ac66-46b9-44ce-a83d-2d57d75e87fe.png)
> ther…
-
The spec says:
> Finally: If the requested skeleton included both seconds and fractional seconds and the dateFormatItem skeleton included seconds but not fractional seconds, then the seconds field …
sffc updated
4 months ago
-
## Request for Mozilla Position on an Emerging Web Specification
* Specification title: Availability of client capabilities - PublicKeyCredential’s getClientCapabilities() Method
* Specificati…
-
**Context**
The W3C working group for distributed tracing is aiming to move the W3C baggage specification from candidate recommendation stage to an actual recommendation. As part of this, we were r…
-
> I enabled trace logging in GoToSocial and retried a follow. Looks like it's upset with this:
>
> ```json
> {
> "@context": "https://www.w3.org/ns/activitystreams",
> "actor": "https://…
-
#### What
Is there any available example of building common features that are compliant to relay server spec with nexus?
#### Why
- I'm trying to migrate my frontend to relay for some perf/stru…
-
TL;DR: I want the ETag to change when the `access-control-allow-origin` header is different but the response body is the same.
---
We are facing an issue right now with a couple moving parts…
-
As per msalle and specs https://datatracker.ietf.org/doc/html/rfc8414#section-3 or https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig, OA4MP is not compliant in that the discove…
-
**LocalAI version:**
[`274ace2`](https://github.com/go-skynet/LocalAI/commit/274ace289823a8bacb7b4987b5c961b62d5eee99)
**Describe the bug**
When enabling the stream API each choice completion…
Karrq updated
6 months ago