Juan Leni

Never bored! Passionate about AI/ML, playing with blockchains these days. @_zondax_

[Juan Leni @jleni]

Decouple, encapsulate and refactor/rewrite.. That's how you can safely replace inefficient components.. Remote work is the "decouple+encapsulate" step. AI, will eventually refactor and take over many professions. (drawing->@madewulf) #AI #remotework #progress #wetware

[No context Hazz ⛩ @HazzimIO]

No comments.

[Juan Leni @jleni]

asking for a friend:
“We don’t train on your data” is not the same as:

“We don’t analyze your usage.”
“We don’t aggregate demand signals.”
“We don’t mine metadata.”
“We don’t infer what customers are building.”
“We don’t use derived intelligence to compete with you.”

Enterprise plan, SOC 2, DPA, blabla, etc. are useful.

But I wonder: are they contractually barred from front-running customers?

[Juan Leni @jleni]

asking for a friend:
“We don’t train on your data” is not the same as:

“We don’t analyze your usage.”
“We don’t aggregate demand signals.”
“We don’t mine metadata.”
“We don’t infer what customers are building.”
“We don’t use derived intelligence to compete with you.”

Enterprise plan, SOC 2, DPA, blabla, etc. are useful.

But I wonder: are they contractually barred from front-running customers?

[Juan Leni @jleni]

the scarier part is that you select "do not train with my data" but ...AFAIK.. nothing stops them to use your questions, thinking process, etc.. as market research and eventually frontrun people or your company?
Some human laywer: How tight are the consumer and enterprise contracts?

[kunobi @_kunobi_]

kache does not make your soup taste better. it does make your builds faster. please stop putting it in soup. https://t.co/c4XzxQPZ5s

[Juan Leni @jleni]

@elonmusk Simulate some universe with tiny feeble beings

[Frank Braun @thefrankbraun]

It's waaaaay more likely the Zcash price drop is uninformed market participants overreacting to the GOOD news of a Orchard vulnerability being fixed than due to an exploit and subsequent market dump.

The total supply of the Orchard pool would have to drop way more for it to be a result of an active exploit.

I think is is purely the result of a lot of FUDing and a short term market panic.

Insane buying opportunity IMHO.

[Eunice D Wong 🦄 @Eunicedwong]

The $ZEC dump is a perfect example of market illiteracy.

$ZEC is crashing today mainly because the Zcash team publicly disclosed a critical vulnerability in the Orchard shielded pool that could have theoretically allowed an attacker to create unlimited counterfeit $ZEC. Although the bug was fixed immediately, due to Orchard’s privacy features, it’s impossible to prove whether it was used before being fixed.

There is an extremely low likelihood exploit was executed, and panic sellers are overreacting to this uncertainty.

Long term thesis hasn't changed. In an AI driven world where every transaction is tracked, financial privacy will become the scarcest assets and $ZEC is still one of the strongest privacy plays in crypto. Catching this falling knife is going to look like a genius move.

[Beff (e/acc) @beffjezos]

Anthropic: ALL YOUR JOBS AND HOBBIES ARE BELONG TO US. BOW DOWN TO ALMIGHTY CLAUDE AND US IN THE PRIESTLY CLASS

Next thing you know: "Why are people looking to confiscate half our company 😩😭"

[That one guy 🛡️ @i8myapl]

@JohnAlanWoods Really? We're at that childish point of 'my coin is better than your coin' now?

[Juan Leni @jleni]

@zooko @TomZarebczan @1MILLIONMRR @robustus When you say "effective circulating supply" you mean the sum of all unspent notes. And it will be possible to compare with the orchard input-outputs (turnstile cap)?

[mert @mert]

@TrustlessState You would put orchard in withdraw only mode and then wallets would point to new pool

if turnstile doesnt trigger as withdrawals happen, there was no exploit

[mert @mert]

just woke up and seeing a fair bit of fake info

- first, there is no *known* exploit. the possibility of a bug has always existed, so there is no new information. what's happened is a highly advanced zcash expert spent a lot of resources trying to find bugs and *patched* one. that's all the information that's new: that a bug was patched.

- again, all signs show no exploit but you can not 100% guarantee this until the next network upgrade, which core devs are working on right now. Eta soon.

- you can NOT have infinite total ZEC supply EVEN if this bug was exploited.

What would instead happen is that the single orchard pool would be insolvent assuming no social recovery. Now for all purposes, that would still be catastrophic but very different than people implying you can just bridge out infinite amounts (you cant)

So tl dr - you cant have infinite supply bridging out, that's not possible. you CAN have a case where ppl in the shielded pool get insolvent if and only if the bug was exploited. my money is on the bug not being exploited but to prove this for everyone, the next upgrade will help you verify it yourself

[kunobi @_kunobi_]

Kunobi v1.2.0 is now stable. This release started as a fairly simple idea: make the workflows people use every day require fewer clicks, fewer context switches, and less digging around in side panels.

Release notes: https://t.co/m6jZCJuJGA

#Kubernetes #GitOps #FluxCD #ArgoCD

[kunobi @_kunobi_]

Last week we launched Kunobi 1.0.0.

Today we're sharing more details behind the launch, what changed moving out of beta, and where it's going next.

More context here: https://t.co/9jfRfMnolK

#Kubernetes #GitOps #FluxCD #ArgoCD

[kunobi @_kunobi_]

Right now early adopters can get Kunobi Pro at launch pricing for just $9/month, while we continue building the product alongside the community.

Check out for more details: https://t.co/Kt0UifM5ti

#Kubernetes #GitOps #PlatformEngineering #DevOps

[kunobi @_kunobi_]

This release marks our move from beta to stable, and the start of a bigger vision: shared operational context for humans and agents working across infrastructure.

Read the full announcement:https://t.co/Ztu18WTMI1

#Kubernetes #GitOps #FluxCD #ArgoCD #PlatformEngineering #DevOps

[kunobi @_kunobi_]

This walkthrough dives into how kache approaches that problem with content-addressed storage, normalized

Watch the video:
https://t.co/wQwQsNLOPN

#RustLang #OpenSource #BuildTools #DevTools #Programming #SoftwareEngineering #CICD #Cargo

[kunobi @_kunobi_]

We built kache because Kunobi is a Tauri app with a large Rust dependency tree.

Here's technical walkthrough of what kache actually caches https://t.co/HrSknLfcHw

#RustLang #DeveloperTools #BuildTools #OpenSource

[Juan Leni @jleni]

https://t.co/C0b4LylHJ2

great work guys! https://t.co/AhDQNBLYDK is soo cool!