3 ms·
Looks like a cool project, but I'm not sure how it would be useful. In the demo video and examples they talk about how it can handle credit card payments via St
by insertnickname 12y ago
Looks like a cool project, but I'm not sure how it would be useful. In the demo video and examples they talk about how it can handle credit card payments via Stripe... why would I want to another party—that contributes virtually nothing—to a credit card transaction?
I also wonder how they deal with abuse. If not restricted, this could easily be used in a DoS attack for example.
- smarx 12y agoHi, Webscript founder here. Generally, I think our customers fall into two large buckets: 1. Experienced developers who want something lighter-weight than, e.g., Heroku. 2. Inexperienced developers (perhaps even first-time developers) who are trying to do something simple (e.g. send themselves a text message when a webhook fires). To take your Stripe example, I imagine based on your question that you're thinking about the case where you have a server-side app already, in which case handling Stripe is very little extra work. If you are instead, for example, selling a digital good via a static website, Webscript would be a lot easier than building a full web app. You could have the job done via Webscript by the time you created a new app and set up your git repo for Heroku. As to the DoS attack angle, do you have an example of how you see Webscript being used for something like that? If you mean flooding some target with HTTP requests, it seems like it would be more efficient for an attacker to send the requests themselves rather than try to funnel them through Webscript.
- shackattack 12y agoI love webscript.io, and am part of the second group – I want to accomplish some sort of webhook-based workflow, with minimal effort or scaffolding. I've used it a few times for hackdays, and it's great how simple + fast it makes it to go from an idea to a rough implementation.