I love this guy.
Re playing this gem https://neal.fun/stimulation-clicker/
Thanks, I spent my lunch hour completing it without cheating. Amazing!
Readit Newshakanito commented on Getting AI to write good SQL cloud.google.com/blog/pro... · Posted by u/richards
The current method of solving this is providing the AI with the documentation of the SDKs your code uses. Current LLMs have quite big context windows so you can feed them a lot of documentation. Some tools can even crawl multipage documentation and index them for the use of LLMs.
How do you do that practically/reliably? Would be great to just paste a link to the SDK Github repo, but doesn't seem to work (yet) in my experience
hakanito commented on Getting AI to write good SQL cloud.google.com/blog/pro... · Posted by u/richards
The game changer for me will be when AI stops hallucinating SDK methods. I often find myself asking ”show me how to do advanced concept X in somewhat niche Y sdk”, and while it produces confident answers, 90% of the time it is suggesting SDK methods that do not exist, so a lot of time is wasted just arguing about that
hakanito commented on It is hard to recommend Google Cloud ashishb.net/programming/g... · Posted by u/todsacerdoti
> CF could probably get a lot more customers if they would allow you to use custom nameservers for your domain.
Why would they want that? The whole point of CF as a registrar was so you could use the other services. The registrar is sold at cost. It's a way to lock you in.
It would lower the barrier to switch to Cloudflare for new customers, and once they are inside with a credit card on file it’s arguably easier to explore their product offerings
hakanito commented on It is hard to recommend Google Cloud ashishb.net/programming/g... · Posted by u/todsacerdoti
> I get it, it was a "consumer" product essentially, hence selling the
> business to Squarespace instead of someone like Cloudflare.
Grocery stores don't make their money from selling bread and milk, but a store that doesn't sell bread and milk is run by fools.
The obvious go-to choice was Cloudflare for us too, but then it turned out you can't use CF just as a registrar (at least on the basic plan or equivalent), you need to use Cloudflare's nameservers as well... But we use Google's Cloud DNS for everything, so that was a showstopper. In the end we went with AWS Route 53.
CF could probably get a lot more customers if they would allow you to use custom nameservers for your domain.
hakanito commented on Why won't some people pay for news? (2022) diaspora.glasswings.com/p... · Posted by u/dredmorbius
hakanito commented on Why won't some people pay for news? (2022) diaspora.glasswings.com/p... · Posted by u/dredmorbius
That's been a dream for nearly as long as the web has been around. I'm pretty sure there are mailing list threads from the '90s about turning micropayments into a standardized web API. As far as I can tell, this never caught on because it's almost always more profitable to operate your own paywall scheme or payment network than to participate in someone else's (provided that you're powerful enough to get away with it).
The point is you should be able to operate you own paywall. The tech is mature enough in 2024 to make it work.
Make the browser store you credit/debit card info, make the browser handle the payment UI, make the browser expose JS apis to invoke payments and receipt fetching against pluggable payment providers.
My ideal world looks like this. New html button element:
`<pay amount="1.00" currency="USD" reference="my-article-123" checkoutUrl="https://...">Unlock for $1.00</pay>`
Clicking it opens browser checkout flow. The url you get from stripe/paypal or another whitelisted payment provider that has implemented the spec, some flow similar to OAuth. On a successful tx, a signed receipt (something like a jwt) is returned from the provider and saved by the browser, on disk on your computer.
The webpage can then load signed receipt references from the browser api, sends it to the backend which can return the article content if the receipt jwt is valid.
It can be fixed if the right people from Chrome and Stripe got together in a room and brainstormed for a bit. Then everyone else would follow.
hakanito commented on Why won't some people pay for news? (2022) diaspora.glasswings.com/p... · Posted by u/dredmorbius
Because I don't want to pay monthly for a bunch of content I probably won't read. I want to pay a small amount of money, with as little friction as possible, for the specific content I want to read now.
This is what I want too. Been wanting it for years.
Maybe once payments are bundled into the browser coupled with some W3 standard…
Without prior software dev experience people may take what the LLM gives them at face value, and that's where the slop comes from imho.