The issue with bank transfers today is that the SEPA system is robust and established, but got no web compatible API.
But there are two projects (why one, if you can have two!?), one being Wero by different banks, the other being the Digital Euro by the European central bank. If either finds good adaption (Wero is rolling out slowly and for quite a bunch of banks every customer already got a Wero account automatically) this could move things around ...
I believe the usual SEPA flow is either scan this QR code or type this IBAN+reference into your bank's mobile app? SEPA is a "giro" system, meaning the person who owns the money has to push it, rather than a cheque system where the money owner writes something to the merchant who then pulls money from the money owner. These are always less convenient because the money owner has to contact their bank. They're also more secure.
I'm Irish, but I've built a website for an Australian client and they integrated something which did that. In the checkout, you could choose to pay with a system which would log you into your bank's website, where you could approve a payment, then return to the site on which you'd made your purchase, where it would instantly be marked as paid. I think that it may have taken a few days for the money to actually arrive in their bank account, but the payment was authorised instantly.
That would seem like a logical solution. So wouldn't it be convenient for the expensive payment methods if legalities prevented merchants from charging higher fees to customers using them?
Indeed. It's a triumph of consumer protection laws failing to protect consumers. Merchants here have to set their prices a bit higher to compensate for the fees and you still have to pay those higher prices as a customer even if you're using a more efficient payment method. I will never understand why the law wasn't set the other way - requiring explicit disclosure of payment fees to end customers and prohibiting payment services from incorporating these kinds of anticompetitive terms in merchant agreements - so that everyone could make an informed choice and market pressures would push the transaction overheads down.
Maybe check out Goose. It is the standard agent harness being developed by The Linux Foundation under the AAIF. Under active development and the implementation seems to have a good leg up on the other popular agents.
Any Pi extensions you'd specifically recommend? I'm just starting out with Pi, but I've had mixed results with extensions. I'm using Pi with gemma4 26b locally, so anything that's friendly to small local models would be appreciated. I think the only extension I'm using right now is pi-total-recall.
This will be interesting. I can see some world where it’s used with consumers, but for the most part I think it will be in the cloud and that would make most sense
is this true because training companies have not been training AI for both performance and brevity (or some other metric like that)? If this becomes a much more serious issue surely they would adjust the training processes
Isn't it true that the more people that sign this petition serves to increase the case for the NYT to not be allowing access to archive.org (as many have said - most people only care because it allows them to circumvent paywalls)?
reply