Christian Banse

> @ripienaar I'm aware that form3tech-oss promptly fixed it in their fork of jwt-go when I notified them, and I see that it is now also fixed in golang-jwt/jwt. Nevertheless,...

> In case we don't get any responses on [gofrs/help-requests#41](https://github.com/gofrs/help-requests/issues/41) I propose creating a separate repo among those interested within this thread. > > `golang-jwt/jwt` or `go-jot/jwt` or other, any...

@jkanywhere This sounds interesting. Can we interest you in bringing this over to http://github.com/golang-jwt/jwt with a new PR? This project is not maintained anymore and we decided to do a...

We have just released a `v3.2.1` version of our forked/cloned community maintained version at https://github.com/golang-jwt/jwt/releases/tag/v3.2.1

Is there any update to this pull request? I would really appreciate this feature.

> Since this will technically be a breaking change, I want to jump onto the latest version of the new repo which is now tagged as v4 ([migration guide](https://github.com/golang-jwt/jwt/blob/main/MIGRATION_GUIDE.md)). >...

I finally go around to move this to our current `v4` release of jwt-go

Well I was thinking about the motivation behind the websocket thingie and it makes sense from a developer point of view. But what if we would actually provide sort of...

Personally, i would also like to see #124 for this as well.

Nice! Could we try adding the map parameter 2 on event 42? This looks like the uuid of either the owner or the "opener". I can check it in the...