Quote from: stan.distortion on April 13, 2016, 08:31:26 PM

Quote from: snogcel on April 13, 2016, 07:53:51 PM

Quote from: spatula on April 13, 2016, 06:45:37 PM

Quote from: stan.distortion on April 13, 2016, 06:42:04 PM

Services on the second tier seem to be getting strong interest. The DAPI is allowing all kinds of things that where impossible for a distributed system not long ago, traditionally centralised services running on a distributed platform.

Can you give some examples of what you think the DAPI will be used for? I'm sure there all kinds of uses that I can't even think of as this is brand new technology.

Payment processors are probably the most prime candidate for this type of functionality. Easily accessible payment verification will be a huge advantage for Dash in terms of ecommerce growth. I've come to think of Dash as being the "WWW" to Bitcoin's "TCP", take that as you will ;-)

Cheers

Any chance of expanding on that a bit? I should have been following how things are going but lost track.

No joke, Dash has passed the point of too much happening to keep track, every month there's a new wave of budget proposals adding to that and some of those projects are hiring:
https://dashtalk.org/threads/python-and-javascript-developers-wanted-27k-in-bounties.8654/

Definitely! Happy to expand a little bit on it. I recall a couple years ago I wrote a WooCommerce Payment Processor plugin. I thought it was pretty cool at the time and recently happened to stumble on a video I'd recorded of it in action. A couple things came to mind:

1. Confirmation took about 10 minutes in total... looking back that is an excruciating time span to wait ;-)
2. The payment method itself bounced API requests off a centralized server. You'd hit it once to create payment address, present it to the user, then poll the API every 10 - 15 seconds until you got a "paid" response back.

DAPI changes all of that --

1. Confirmation is of course nearly instantaneous. Pretty slick ;-)
2. You don't need a payment processor at all; you create a payment request directly within the Dash network - it hits the end-users wallet, they send the funds and the API sends a callback to your online shop.

It's all inclusive, that's the biggest difference. It's why I think of WWW vs. TCP, they're all packets at the end of the day - the biggest difference is the end-user experience.