What problem does this feature solve?

I'm using @nuxtjs/auth module in a Nuxt App for building a SaaS product where URLs contains the customer ID (e.g: https://nuxt.app/acme/login). In Nuxt, it could be represented to an URL like so in the router: /:customerId/login (in this example, :customerId is equal to acme).

*Long story short : I have [a Nuxt

What problem does this feature solve?

In the past, Brotli was not supported on nodejs servers.

If I understand correctly, this is now supported since a few months : nodejs/node#20458

This PR dropped support for Brotli : nuxt-community/axios-module#180

Maybe it's time to revert this BR because Axios is supporting it too : https://github.com/ax

OSX build notes have the following line
brew install automake berkeley-db4 libtool boost --c++11 miniupnpc openssl pkg-config protobuf python3 qt libevent

However, the boost --c++11 isn't a valid command anymore. Need to update it

Link : https://django-graphql-jwt.domake.io/en/latest/authentication.html#delete-cookies
Section : Delete Cookies
Wrong : # Long running refresh tokens
delete_refresh_token_cookie =
graphql_jwt.refresh_token.DeleteRefreshTokenCookie.Field()

Right : # Long running refresh tokens
delete_refresh_token_cookie =
graphql_jwt.DeleteRefreshTokenCookie.Field()

Given that PASETO is designed for "Resistance to Implementation Error / Misuse", I'm surprised the examples don't cover calling JSONToken.Validate, nor does JSONToken.UnmarshalJSON do this on it's own.

The documentation does indicate that the standard claims are optional, which would mean that calling the default set of validation functions during JSONToken.Unmarshal might break the curre

It is redundant to keep Dex Helm chart in this repository, we should leave dex-k8s-authenticator chart and a good explanation of how to integrate it with Dex chart taken from stable/Dex repository.

Blockers

• Solidity 0.6.2 release

Issue

We should use this everywhere for gas savings:

ethereum/solidity#3835

Large integers, like 9999999999999999999999999 are valid in JSON files and are valid as data parts in the 0xcert conventions. However these numbers are currently not representable in JavaScript in full fidelity. This violates some guarantees made by (or assumptions you might make while using) the 0xcert Framework. Workarounds are available.

Discussion

These examples are running Safari Ver