lasryaric
Joined 15 years ago
Joined 15 years ago
If you can deliver on your promise then I would definitely be a user and a customer.
I am a software engineer and the design part is always a big problem for me, until a friend and ex-colleague of mine arrives.
Once, my co-founder @Ilan Abehassera sent me a link to an article about Stripe on Techcrunch:
I signed up to Stripe, within minutes I was able to charge my own credit card through a CURL bash call, everything was clear, recurring payment perfectly handled, discount, etc etc. And this was at the very beginning of Stripe. Then I had to come up with why we should quickly switch from Paypal to Stripe.
Anyway, very good memoery, you definitely set the standard for how an API should be designed and I can't thank you enough for that!
You can make XHR (aka ajax) requests only if the CORS policy allows it (concretely, this local web server you are trying to access is answering with a specific HTTP header saying "I authorize the website xyz.com to send XHR request to me via the web browser of the client of xyz.com).
Now for everything outside of XHR(ajax), you can send different type of requests : <script src="..."></script> but this let you only load js files. <img src="..." /> but this lets you only load images, you can't really do much other than try to load images with that.
So if you get into the detail of each "web api" (XHR, <img/>, <script/>, etc) you will see that you are actually very limited.
I guess this should serve as a cue that there is something off in what you are writing. You did not just discover a major security flaw in all web browsers while not being an experimented (at least web) software engineer.
I think it's reasonable to think that I can share that nobody bought my shares. I can't talk for any other employee or anybody else.
Again, this is just my view of the industry, with a few data points here and there.