Johann Pardanaud

Wild idea: maybe sockets are just something really boring and hard to use and we can just replace them with an HTTP server for Node and an HTTP client for...

This issue is still valid? I can't see where it's written "All products"...

One more thing to do with this issue is to improve responses for the `/api/user/` endpoint. Currently, if you create a user with a password which doesn't meet minimum requirements,...

I can confirm the problem persists, I'm currently trying to broadcast some messages from the `us-east4` region to the `europe-west8` one, but I receive nothing. Until today, it worked fine....

FYI, it seems rather erratic, today it works while yesterday it wasn't. 😅

One more thing: this issue doesn't seem related to a broken deployment. A few hours ago, I've deployed a new version of my app, and the broadcasting from `us-east4` to...

I see one issue with the current WebSocket server: not being able to discard heavy incoming messages. A malicious user could make the data transfer rise up quickly on Deno...

Instead of breaking the spec, maybe the event could be added to [`UpgradeWebSocketOptions`](https://doc.deno.land/deno/stable/~/Deno.UpgradeWebSocketOptions) as a `onframe` field? As an added bonus, this would apply only to the server and the...

>from what i can see we dont have access to low-level info like the frame Ha! Just saw the code you linked was in a dependency, now I understand the...

Good point, the middle code should desugar to this to allow this behaviour: ``` js var Foo = (function () { class Foo { } Foo = dec(Foo) || Foo;...