-
Standards for audience-data interchange, advertising, analytics? At W3C, it could build privacy in from the start.
Noted while at a podcasting discussion. Will the data be/make the platform?
-
**What happened & What you expected to happen**:
See the notebook in the repo below. I was trying to parallelize some function with `dask`, but encountered a large overhead. I checked the `dask…
h3jia updated
4 years ago
-
I've been noticing that the Bitcoin paper at https://bitcoin.org/bitcoin.pdf is getting a lot of traffic (mainly from people searching for "bitcoin paper", or probably seeing it cited by other papers)…
-
Does metadata about the DID Document (such as [when it was created](https://github.com/w3c/did-spec/pull/28), [updated](https://github.com/w3c/did-spec/pull/27), or [who it was signed by](https://gith…
-
[audioworklet] Expose fetch() in AudioWorkletGlobalScope. #1439 https://github.com/WebAudio/web-audio-api/issues/1439 includes several assumptions re the potential for `fetch()` or `XMLHttpRequest()` …
-
Dependant on #218
# Summary
Essentially we want users to own a tld that includes their username and also be able to register app names arbitrarily.
## Extra context
__Taken from: https://talk.fis…
-
The Verifiable Claims Working Group's one standards-track specification, "Verifiable Credentials Data Model 1.0", has some editorial work to go but is otherwise ready for Candidate Recommendatio…
-
**What happened**:
Set up Kubernetes cluster with OIDC parameters on the kube-apiserver.
Deploy Dex for authentication and obtain a token for kube-apiserver
create a kubernetes context and user f…
-
The Verifiable Claims Working Group's one standards-track specification, "Verifiable Credentials Data Model 1.0", is beyond First Public Working Draft but not yet ready for Candidate Recommendation.
…
-
[//]: # (Thank you for reporting an issue to HTTPS Everywhere.)
[//]: # (We welcome input from users on improving this project.)
[//]: #
[//]: # (Please help us by following this issue template.)
…