ahopebailie

15 ms·

1.
by ahopebailie 1y ago
I have always been a fan of how Tigerbeetle abstracts away time so you can simulate ticks for testing purposes. Not applicable to all systems but really powerful for their use case.
2.
How SA's Fynbos Money is helping users to make long-term investments(disruptafrica.com)
1 points by ahopebailie 2y ago|0 comments
3.
by ahopebailie 4y ago
On the contrary I think both products are excellent. The issue I have is that we've taken 20 years to find a better alternative than raw card data in Web forms and as a result we're gonna be stuck with a choice of only those 2 wal
4.
by ahopebailie 4y ago
I think you miss the point that card payments should never have evolved to still require us to type sensitive data into a web form at all. Also, don't forget that 2FA etc are not ubiquitous, especially not in the US. As I implied, PCI
5.
by ahopebailie 4y ago
It's actually about what is supported natively in Web browsers and what the vendors of those browsers have done to make it better. Sadly you are correct that the mentality of the browser vendors is VERY card (and US) centric so accommo
6.
by ahopebailie 4y ago
This is pretty much the exact distinction between the US attitude to cards and the rest of the world. In the US, the ability to dispute a card tx is just part of life. Everywhere else the banks have forced poor UX onto merchants in the name
7.
by ahopebailie 6y ago
We're working to make the Web Monetization API a standard that browsers can adopt natively: https://webmonetization.org The extension helps us bootstrap the ecosystem but a native integration is far superior. Check out Puma
8.
by ahopebailie 6y ago
This was a straight donation. A thriving Web ecosystem of independent developers and creators building and hosting their own content is what gets us out of bed in the morning. Credit to Ali Spivak who kicked this all off and helped us reali
9.
by ahopebailie 6y ago
That's where the idea started but that means the user has to be able to send Bitcoin. The purpose of Interledger is to abstract away that issue which is why Web Monetization is built on Interledger. You don't have to sign up with
10.
by ahopebailie 6y ago
https://wiki.mozilla.org/Identity/Persona_AAR
11.
by ahopebailie 6y ago
No. Although it would be great if they did.
12.
by ahopebailie 6y ago
This is a pretty good summary. Interledger (interledger.org) is a protocol stack and a network. The network consists of a number of companies that have setup arrangements to settle payments between them via different payment rails and imple
13.
by ahopebailie 6y ago
Those two efforts address different use cases. Web Monetization is an API for websites that wish to accept a stream of small micropayments as long as the user is on the site. This suits pay-as-you-use content and service models and is a goo
14.
by ahopebailie 7y ago
Google have some great ones which are applicable across the board (it's a standard!), but they are busy being updated: https://developers.google.com/web/ilt/pwa/introduction-to-th... also: https:/&
15.
by ahopebailie 7y ago
The APIs aren't really designed to solve for this. If the site knows you and has payment credentials stored they won't need to use Payment Request API (although they still can). Storing payment credentials differs by payment metho
16.
by ahopebailie 7y ago
My expectation is that the PSPs will help to hide the complexity from merchants that don't have the resources to use the (admittedly complex) API directly. e.g. Stripe already have support for PR API in their SDK
17.
by ahopebailie 7y ago
Not true at all. The ISO20022 RA (Swift) has been involved since the beginning as have numerous banks from Europe and LOTS of non-card payment methods are represented through their associations or scheme participants. Part of the challenge
18.
by ahopebailie 7y ago
Not explicitly but it does come up regularly. The challenge with standards is that they are very slow to solidify so we have to keep ensuring we are tackling a manageable (small) scope. In my personal opinion recurring payments are quite sp
19.
by ahopebailie 7y ago
I was originally a member of the web payments community group which existed before payments was on any standards track at W3C. The high level of interest and activity in the community led W3C to form an interest group to explore if payments
20.
by ahopebailie 7y ago
Sorry, link: https://www.theverge.com/2020/1/14/21064698/google-third-par...
21.
by ahopebailie 7y ago
Here's a decent write up. In short, 3rd-party cookies and storage are being blocked (or phased out). This means you can insert an iframe into a page but the cookies/storage it has access to will be partitioned based on the origin
22.
by ahopebailie 7y ago
I co-chair the working group doing this work. Happy to answer (almost) any questions? PR API is part of a set of specifications designed to improve payments on the Web. Most importantly, it is the invocation side of a cross-origin payment s