Dave Longley

So, allowing protection to be turned off like in the above suggestion would circumvent the protection feature -- so it's not a viable option. However, we could potentially allow for...

@Fak3, > No, i suggested that @id, @type, @container for the protected terms still be protected from redefinition. Only the property-scoped @context can be modified. Ah, ok. I misunderstood how...

Now that I better understand the proposal, I still think it would be problematic for at least a few reasons. I originally interpreted it the way I did because `@protected`...

Additionally, the `10^21` and other related spec text was informed by the ECMAScript spec: https://tc39.es/ecma262/#sec-numeric-types-number-tostring as well as [RFC 8785](https://datatracker.ietf.org/doc/html/rfc8785) and [RFC 7493](https://datatracker.ietf.org/doc/html/rfc7493). Getting interop and spec text "right" with...

@roptat, > Wouldn't the empty string work too and be more compact? The goal of compaction is not to make the data size as small as possible without regard for...

We could "import" another context in: ```js "@context": { "@import": /* ... */ } ```

> Given that we have to reveal the origin, the simplest would be to always include it for "cors" requests... Shouldn't there be some way of sending a request (at...

@OR13, I think the "holding binding" issue(s) and related conversations started from the idea of creating a dependency of sorts on a proof of possession, but it's grown to encompass...

So I think the problem here is the use of `elliptic` which has been criticized over the years for not doing its best to use constant timing where possible. The...

We're using this library and prefer that Uint8Arrays continue to, by default, use major 2 and not tag 64. Most isomorphic JS is written using Uint8Arrays to express and manipulate...