-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Taler #1309
Comments
FYI: "It's not on our immediate list" to support recurring payments. https://lists.gnu.org/archive/html/taler/2019-01/msg00003.html |
Liberapay doesn't need Taler to support recurring payments itself. |
I don't understand how that should work with my definition of recurring payments. #1400 |
It doesn't. If a payment method doesn't allow pulling money, then patrons have to renew their donations manually, and thus pay several months in advance to avoid being bothered too often. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@Changaco Is there anything new, or is it a old idea that was never forward developed? I would love to see Taler as third payment processor but the first free, open and secure processor. |
@fossdd There isn't anything new, I'm still waiting for Taler to become actually usable with real money. |
So what is actual user story behind "usable with real money"? No exchanges to buy and sell Taler? |
@techtonik the software is not ready to be used in production. and when it is, yes, there have to be exchanges. but don't mistake it for yet another cryptocurrenty (blockchain). it uses cryptography, but no blockchain. you will not be able to get it from a cryptocurrency exchange but from your bank (they are in contact with some banks and also the european central bank) you can read here what it is and how it works https://taler.net/en |
This comment was marked as off-topic.
This comment was marked as off-topic.
They have a roadmap here: https://bugs.gnunet.org/roadmap_page.php (you have to select Taler as a project at the top right)
again, it is not a blockchain. there is no p2p network and no mining. forget blockchain for a moment... there will be multiple exchanges, so if you not trust one, choose another one. like e-mail. you could call it decentralized they have a demo: https://demo.taler.net/en/ try it out and report issues you find! you can use it in the browser with a browser plugin or on the smartphone to use in stores etc. they have a vending machine at a university for testing where you can use real money already https://taler.net/en/news/2020-09.html |
This comment was marked as off-topic.
This comment was marked as off-topic.
Double spending prevention works since 0.0. We just do an online check in the Postgres database. Trivial. Remember, Taler is NOT a decentralized system, so we don't need consensus with third parties to make atomic commits. As for what is needed, well, mostly regulatory hurdles. For example, we're discussing when and how to do what style of authentication/KYC/etc. with PSD2 experts. Plus actual deployment of an exchange with a bank (currently battle-testing the https://docs.taler.net/taler-exchange-setup-guide.html so that real banks can do it). And then there is the little capitalist thing called the business case (who would use it, which merchants, which users, etc.). Happy to hear that liberapay is considering to support Taler, that'll help with the business case ;-). Also, I personally think davidak is right to point to our bug tracker, as we do need a bit more work on the tiny bugs (and some more security audits) before we'd be happy to launch as well. But the "big issue" is really ticking all of the boxes to ensure we are compliant with European banking regulation. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
As the Taler project has entered a new phase, and I've been asked about it on Mastodon, here is the current situation for Liberapay, as I see it. There are two possible ways for Taler to be usable with Liberapay. The first is for Taler to be added as a payment method by Stripe. This would enable us to make Taler available to donors as a payment option without requiring any action from the recipients. The second is to integrate Taler directly in Liberapay. This would require recipients to opt-in to Taler by providing us with their bank account numbers. These two integration pathways are not mutually exclusive, and there would be some advantages in implementing both. For a direct integration, I would prefer that the Liberapay software interact directly with the Taler wallets and exchanges through their respective APIs (i.e. this one and that one, I think) rather than with the merchant backend developed by the GNU Taler team. The possibility of applying for a grant is of no direct use to me because my work on Liberapay is already funded by the community, but if there was someone else able and willing to work on integrating Taler into Liberapay, then a grant might enable paying them to get it done. |
@Changaco I doubt Stripe integration will ever happen. "making sale incomes transparent" is particularly a scary thing for merchants to read from the project presentation. For direct integration, I don't really understand why a bank account is needed. Maybe the transactional technology itself is awesome, and the theory for it since the invention of public key signatures, but for users it is just another layer of wallet management complexity on top of what we already have. |
Now that Liberapay is no longer limited to Mangopay's wallets we should be able to add support for GNU Taler when it becomes operational. This payment method is designed to provide an unparalleled level of privacy to the payer.
Related issues: #1062 and #1268.
The text was updated successfully, but these errors were encountered: