Receiving webhooks

[GarboMuffin]

Here's a weird idea. We have many ways to send webhooks but naturally no way to receive them so people have to resort to things like polling. Not great.

What we could do is have some service like webhooks.turbowarp.org and a corresponding extension. The process is:

1. Extension can generates very long random code. Can store it in the project.
2. We tell the user to use the URL webhooks.turbowarp.org/post/verylongrandomcode as the webhook they give to whatever website lets you add webhooks (are there any interesting ones?)
3. Anything sent to that code gets forwarded over a websocket or server-sent events to the project.

Tada: it's a webhook going the other way

concerns:

• figuring out reasonable rate limiting, max sizes, etc.
• generating the random web hook codes server-side might be better against abuse
• the random code remaining private is important; storing it in the project seems a bit dangerous but not sure of better solution as long as people know about the risk when sharing their project file
• the payload would be fully readable by the server; hopefully there's nothing sensitive in there
• if project is not opened then webhook events should probably just be ignored

[CubesterYT]

There's good handling services like Postman, GitHub, etc that people could use to fetch data from with a incoming webhook.

(Unrelated but similar, we should open an issue discussing hosting our own cors proxy)

[yuri-kiss]

There's good handling services like Postman, GitHub, etc that people could use to fetch data from with a incoming webhook.

(Unrelated but similar, we should open an issue discussing hosting our own cors proxy)

The cors proxy one already has an issue which is related