Comment by wpapper
10 hours ago
Thank you for the kind words! I’m a PM on the team that is building this. I’ve believed in microtransactions for over a decade and hope that we can finally bring them to life.
Proper spend delegation and permissions is a big focus of ours - it’s great to let your agent have discretion, as long as the damage from going off course is limited. Definitely want people to feel comfortable experimenting with emerging tech
Feel free to email me at (my username)@(my company) if you have any feature requests or things you’d like to see
Do you have any plans on mitigating the privacy consequences of microtransactions? I'm fine with paying for (some) content, but I'd prefer if there weren't some companies using that information to manipulate me or the more impressionable members of our society.
We plan to make it easy for both buyers and sellers to rotate addresses. Done right, everything should be pseudonymous to the outside world.
(Full privacy is a harder problem to solve, but address rotation is a good 80/20 solution for now)
Good to hear.
I think web servers monetizing any user identifiers possible should be assumed by this point in the web's evolution, and precluded to the extent possible at the protocol level.
No one is going to say "Oh, we've got micro-transaction revenue now, let's do away with ad tracking." They're going to say "Great, now we have both streams of revenue."
If Cloudflare et al. are stepping into the middle of the transactions, I'd much rather scope my identity leakage to only them than everyone running a web server.
IMHO this is only interesting if it _truely_ breaks a KYC path. Otherwise; who cares?
Please tell me this will be IPv6 only or at least IPv6 first! Or allow differentiated pricing so IPv4 calls can be made more expensive. CF, as much as I have issues with the constant CAPTCHAS I run into and blocking my Hurricane Electric tunnel every so often, is in a unique position to get us past having to support the legacy internet protocol.