This could be an extremely interesting legal argument, but I suppose the language used requires a request in 'writing' of some sort, which I suppose HTTP requests would fail.
Razorpay has been such a terrible experience for me as a consumer, that I'd actively avoid using it as my payment processor.
I know at least 3 scam operations having their payments processed through razorpay, and these are proper scams selling non existent products. So far all my complaint emails to razorpay have gone unanswered.
Have the entire world change their implementation rather than the one company which is doing it wrong?
This is not how RFCs work. There's a reason RFCs came about, and it was to prevent this exact type of situation. Just because a company has a large market share, doesn't mean RFCs should be changed to suit it.
Because if they didn't pretend that it was the same to fly a 737 and a 737 max, then they would be required to have pilots get a separate type certification for the max, which is costly for airlines and makes the airlines very reluctant to order the max.
Wow, $1 for 100 emails is very very very very expensive. So expensive that I'd opt to build this in house rather and take on the costs associated with it and still come out saving money.
Actually a lot of email addresses cannot be validated this way since most ESPs including gmail have adopted an 'accept-all' approach to incoming email. So getting the email accepted by the server is no indication that the address exists, or that the email will actually be delivered to that address even if it exists.
One of the suggestions that came up more often from people who tried out Socket Wrench was the ability to connect to Socketio servers. However supporting socketio namespaces complicated the UX, so I decided to wait till I got a lot more people asking for SocketIO support to implement it.
This is pretty much the only reason, apart from issues, that I actually open Github in the browser for. Now I can do even that from the terminal. Yes! Thank you!
The automatic report generation from templates is nice. But the killer feature for me would be the programmable actions. No more clicking and confirming and verifying while creating new testing accounts sounds like heaven, especially if you're working in a studio developing a new app every month like me.
Ooh, this is just in time for me. Was searching for a React charting plugin with multiple styles just in the morning. Will give this a spin in development and come back with more comments. Thanks :)
How does this compare against existing services? Wondering since we use box for file sharing at our company, and file upload speed has never really been an issue for us.
This has actually existed as an independent library called Mailcheck.js[1] for a long time and I have used it in quite a number of projects. So if that is the only reason you want to use this API it would be better to go with mailcheck.js, simply to remove an external dependency.