havnagiggle
Joined 7 years ago
Joined 7 years ago
I run the same presubmits on pre-receive and merge requests, so you wouldn't get too far shooting your own foot. But yeah, if you're not using the feature then it wouldn't save you so it's not foolproof. I also run tools for scanning for credentials, etc.
Generally though, you are also investing your time into leveling up junior engineers to take over responsibilities from you. I just never really see that happening with AI. Even as it gets "better" technically, there's no real growth pattern to its work and it doesn't understand ownership or responsibility.
But if scaling isn't a problem, then sure just write it yourself.
It's as good of a proof for TLS certs, but it's susceptible to DNS hijacking, etc. Make the contract immutable to meet tornado.cash standard. There are already oracles for DNS lookups so this contract might already exist somewhere.
Add in a couple of features:
1. Allow tracking per domain so publishers can know that there is a demand to set it up on their end.
2. Allow refunds in case the publisher never opens it up.
The convenience of the scamming is partly why it _is_ a solution to this problem: people can transfer value as fast as they desire, and it works. There is also just a problem off on and off-boarding where you get hit by Visa/Mastercard level of fees. So is it really solving the problem at that point?
One area I would like to see is some kind of governed/regulated profit sharing. Basically giving your votes to content/production and this puts it on the books for some fraction of payment. You get X shares to distribute to content regularly. It would also be helpful if our government would provide support for independent producers where there's a clear trackable benefit (e.g. open source libraries that a ton of people rely on and a business can say "yes I need this, help them keep doing it").