3 ms·

You're making it sound like this is more useful for money laundering than any desirable purpose.

by Kalium 4y ago

ChuckMcM 4y ago
Hmm, that wasn't what I was trying to communicate. The original question was "what problem is this solving?" The ability to create a link that you click on, and it only gives you access to the results after you pay some money, has been implemented by many frameworks and commerce "stacks". Given that if you implement something that way with an off the shelf front end, you probably already have the capability to gateway the link with a payment ask. So that sets up the situation that we have a thing that just does one part of this kind of the thing, the pay when you click. Sort of "instant paywall for URIs" kind of thing. I think the question "Why would I use that?" or "What problem is this trying to solve?" implies that there is something about the well known solutions that prevents you from using them. My guess was that you wouldn't use one of the existing solutions if you wanted to obfuscate the connection between the payment and the product. And it is just a guess, I have no investment in it being "the actual reason" or being right about my guess, just speculating here. From your comment it suggests that you know of "desirable purposes" for just such a service. (which sounds like a problem solution right?) I would love to hear them. I am sure I'll learn something new and that will be awesome.
- EricMausler 4y ago
  Maybe as a ticket entry system? Bar with a cover charge puts a QR code on the front door. QR code leads you to a paid link, you pay for access, it shows a thumbs up, you show the bouncer, they let you in. Let's the venue track how many people showed up, doesn't require a whole account situation, and also reduces the need for people to deal with card processing or cash at the door. Also let's you come and go without a wristband or stamp or something else to verify you already paid. Trivial to change the URL each day so you can't use a previous day. Or let it ride for weekend access, etc Not sure if better solutions already exist though
- Kalium 4y ago
  > My guess was that you wouldn't use one of the existing solutions if you wanted to obfuscate the connection between the payment and the product. And it is just a guess, I have no investment in it being "the actual reason" or being right about my guess, just speculating here. I think you're on to something here. Much like cryptocurrencies, I'm thinking that the most important uses here are at best questionably legitimate. Very few honest and above-board businesses have an interest in obfuscating what's being sold like this, but quite a few less legitimate ones do. Hit a URL to send money? Sounds great for money laundering, fraud, or extortion when you can move money around using convenient services and the veneer of legitimacy.

You're making it sound like this is more useful for money laundering than any desirable purpose.

by Kalium 4y ago

You're making it sound like this is more useful for money laundering than any desirable purpose.

Hmm, that wasn't what I was trying to communicate. The original question was "what problem is this solving?" The ability to create a link that you click on, and it only gives you access to the results after you pay some money, has been implemented by many frameworks and commerce "stacks". Given that if you implement something that way with an off the shelf front end, you probably already have the capability to gateway the link with a payment ask. So that sets up the situation that we have a thing that just does one part of this kind of the thing, the pay when you click. Sort of "instant paywall for URIs" kind of thing. I think the question "Why would I use that?" or "What problem is this trying to solve?" implies that there is something about the well known solutions that prevents you from using them. My guess was that you wouldn't use one of the existing solutions if you wanted to obfuscate the connection between the payment and the product. And it is just a guess, I have no investment in it being "the actual reason" or being right about my guess, just speculating here. From your comment it suggests that you know of "desirable purposes" for just such a service. (which sounds like a problem solution right?) I would love to hear them. I am sure I'll learn something new and that will be awesome.

EricMausler 4y ago
Maybe as a ticket entry system? Bar with a cover charge puts a QR code on the front door. QR code leads you to a paid link, you pay for access, it shows a thumbs up, you show the bouncer, they let you in. Let's the venue track how many people showed up, doesn't require a whole account situation, and also reduces the need for people to deal with card processing or cash at the door. Also let's you come and go without a wristband or stamp or something else to verify you already paid. Trivial to change the URL each day so you can't use a previous day. Or let it ride for weekend access, etc Not sure if better solutions already exist though
Kalium 4y ago
> My guess was that you wouldn't use one of the existing solutions if you wanted to obfuscate the connection between the payment and the product. And it is just a guess, I have no investment in it being "the actual reason" or being right about my guess, just speculating here. I think you're on to something here. Much like cryptocurrencies, I'm thinking that the most important uses here are at best questionably legitimate. Very few honest and above-board businesses have an interest in obfuscating what's being sold like this, but quite a few less legitimate ones do. Hit a URL to send money? Sounds great for money laundering, fraud, or extortion when you can move money around using convenient services and the veneer of legitimacy.