532 karma · joined September 28, 2016
I for one, amongst many people I am sure, am deeply grateful for the work of you and your peers in getting this out!
Some notes: 1) I think you are to cheap. 2) signatures of sent webhooks is pretty important for the receiving party.
Would love to hear from the OpenAI folks as to why they chose to use Kubernetes for this problem.
It is a chicken and egg problem though as browsers won’t implement anything without scale and it’s difficult to get scale without lots of users. We polyfill it with a browser extension. It’s not a great solution though.
We always looking for feedback and users :)
Interledger is a payments clearing protocol modeled on IP where settlement is arranged through peering relationships. It is incredible good at low value payments.
Our next work in the space is beginning to open it up to Retail style payments through Open Payments[1]. Initially we are targeting mini payments (<$5). As these are poorly served currently with traditional options due to high fees.
However our final goal is much bigger. The real problem we see in digital payments is not MasterCard, Visa and PayPal but Apple, Google and Facebook. We had OpenId but we ended up only getting login with Apple, Facebook and Google. The same is going for payments. We believe Open Payments is a viable alternative to provide an open payments system that is not big tech.
[1] openpayments.dev
Disclaimer: Work for Coil
One question I don't see addressed in that thread.How do you deal with failures of the node? Do you use active-active type replication or some other strategy?
Checkout codius.org
For me the most exciting part is the seamless network switching potential of /3 on mobile devices