tleyden5iwx

Can they change the name to Proof Of Corncept?

AGI will happen, but we need to start reverse engineering the brain. IMHO LeCun and Hawkins have it right, even though the results are still pretty non-existent.

In the meantime, 100% agree, it's complete fantastical nonsense.

Yeah but there are a lot of vibe engineers, and we care about the code, because we have to own it

Feature request: add a Github Action so I can generate a codemap for my repo and throw it on my README. Then update it when major PRs change the codemap.

Agree with LeCun that current ai doesn’t exhibit anything close to actual intelligence.

I think the solution lies into cracking the core algorithms used by nature to build the brain. Too bad it’s such an inscrutable hairball of analog spaghetti code.

API clients can already easily identify the user during the authentication process. What’s currently “missing” is a way for an API client to pay a service via the API call “on the fly”, without having a credit card on file or some prior account balance.

Maybe a better example is an image generation api. Your agent chooses one based on its research, and without any account or credit card on file, it buys you an image using a x402.

Looks really useful! Do you happen to have a gallery of apps using it? In particular, I'd like to see how desktop or mobile apps handle the oauth flows.

I think the purpose is so that your agent can do things like buy airline tickets for you. Using x402 it doesn't have to go through a typical credit card checkout process, which might have a lot of safeguards that make sure there's an actual human on the other end (captchas, etc)

I don't think like a C programmer, my problem is that I think like a Java/Python/Go programmer, and I'm spoiled by getting used to having a garbage collector always running behind me cleaning up my memory poops.

Even though Rust can end up with some ugly/crazy code, I love it overall because I can feel pretty safe that I'm not going to create hard-to-find memory errors.

Sure, I can (and do) write code that causes my (rust) app to crash, but so far they've all been super trivial errors to debug and fix.

I haven't tried Zig yet though. Does it give me all the same compile time memory usage guarantees?