4 ms·
> If you're paying for something, the concept of an "account" has to exist in order to record the payment against. If you're paying for something, that generall
by xur17 7y ago
> If you're paying for something, the concept of an "account" has to exist in order to record the payment against. If you're paying for something, that generally transfers a chunk of personal information for anti-fraud purposes. Given that, an email is not a huge ask, and is very useful for e.g. billing reminders. It doesn't have to be a spam thing and GDPR is gradually cracking down on that.
This is obviously a somewhat niche use case, but given you accept Bitcoin, you might be open to it.
I'd love to be able to upload files for a very small fee (few pennies) with no account, and then allow anyone with a link to the file to top up the hosting funds for the image. If you run a lightning node, this would be perfectly feasible for sub-penny amounts.
- pjc50 7y ago> allow anyone with a link to the file to top up the hosting funds for the image This is a genuinely differentiating feature and might be useful even without the Bitcoin aspect. It's easy to imagine someone being annoyed by a deep linked image going away - but being able to pay to revive it.
- xur17 7y agoI agree. You likely could tackle this by requiring users to have accounts that they can deposit funds into (with some minimum to avoid credit card fees), and distribute to pages. The big advantage with microtransactions is that users don't need accounts.