mavdol04

7 ms·

1.
AIgnostic(lewiscampbell.tech)
3 points by mavdol04 15d ago|0 comments
2.
LLMs and self-referentiality(scottaaronson.blog)
83 points by mavdol04 15d ago|93 comments
3.
ChatGPT becomes first AI chatbot to face tougher EU rules(lemonde.fr)
6 points by mavdol04 16d ago|1 comments
4.
by mavdol04 3mo ago
It doesn't have browser support yet because it's WASI-based, so there are a few more steps compared to Emscripten (two different ways to build for WebAssembly). But networking is supposed to work, did you have trouble with it?
5.
by mavdol04 3mo ago
With RISC‑V emulation we get the virtual hardware components we need to boot Linux like MMU, registers etc. So a GCC WASM backend could definitely help, but I'm not sure it could replace the whole emulation layer.
6.
Show HN: Vpod – Tiny Linux sandbox running in WASM(github.com)
12 points by mavdol04 3mo ago|5 comments
7.
WASI 0.3(bytecodealliance.org)
260 points by mavdol04 3mo ago|98 comments
8.
by mavdol04 4mo ago
It's a bit of a cheat, but you can hit 0.00% every time. Just measure the bar length, then cross-multiply. :) Example: bar is 1250px, max is 2100, number is 376 → (1250 × 376) / 2100 ≈ 223.8px from the start, that's the 0.00%
9.
by mavdol04 4mo ago
Working on a RISC-V emulator targeting Wasm. Is RVV 1.0 stable enough to be worth implementing, or would Zve32f/Zve64d already cover most use cases ?
10.
by mavdol04 4mo ago
That's cool, i did exactly the same few years ago
11.
by mavdol04 5mo ago
Nice, what are you building exactly ?
12.
Show HN: Capsule Bash – Sandboxed Bash for Agents(github.com)
3 points by mavdol04 5mo ago|3 comments
13.
by mavdol04 5mo ago
I am in the EU timezone and had some minor issues recently with GitHub as well, but it never lasts very long.
14.
Reimagining Bash for Untrusted Contexts(capsulerun.github.io)
2 points by mavdol04 5mo ago|0 comments
15.
by mavdol04 5mo ago
The worst that could happen is having your credentials stolen. It’s an LLM architectural flaw, so it has to be at the tools level so the only way to prevent it is still sandboxing in my opinion. Or at least sandboxing the tools themselves
16.
One-time pad encryption with DNA (Paris to Tokyo)(arxiv.org)
1 points by mavdol04 6mo ago|0 comments
17.
by mavdol04 6mo ago
I think a shared array just avoids the copy, not the serialization which is the main problem as they showed with serde-wasm-bindgen test
18.
by mavdol04 6mo ago
Wait, you just invented a reverse CAPTCHA for AI agent
19.
by mavdol04 6mo ago
That’s great, but it can’t be used in production because it’s not available for Linux (so no AWS, no GCP, etc.) and requires Docker Desktop. Still nice for experimenting, though.
20.
by mavdol04 6mo ago
I mean standardizing on an x86 subset would replace wasm's native portability with a kind of 'emulated' compatibility, and this is one of wasm's strengths. If we do that, non-x86 hardware(mobile etc.) will pay the transl
21.
by mavdol04 7mo ago
It actually works a bit differently. The eval is executed by the interpreter running inside the isolated wasm sandbox (StarlingMonkey). You can think of it as each sandbox having its own dedicated JavaScript engine.
22.
by mavdol04 8mo ago
Thanks! Not yet, but that's a great idea. I could definitely add it to the roadmap.
23.
by mavdol04 8mo ago
yeah, the previous example was quite basic. I will write a complete example for that, but here is how you can run dynamic code: import { task } from "@capsule-run/sdk"; export default task({ name: "main&quo
24.
by mavdol04 8mo ago
I would love for the component model tooling to reach that level of maturity. Since the runtime uses standard WASI and not Emscripten, we don't have that seamless dynamic linking yet. It will be interesting to see how the WASI path eve
25.
by mavdol04 8mo ago
Thanks for the feedback! What do you think about running the separate file directly from the decorator?
26.
by mavdol04 8mo ago
Thanks! Got it, I will add more examples for that. Currently you can do both: run dynamically untrusted code with eval, or run fully encapsulated logic (like in the existing examples). I made a small example that might give you a better ide
27.
by mavdol04 8mo ago
I understand your point. I added native Python support because C extensions will eventually become compatible. Also, we might see more libraries built with Rust extensions appearing, which will be much easier to port to Wasm.
28.
by mavdol04 8mo ago
I recreated many Node.js built-ins so compatibility is actually quite extended. For Python, the main limitation is indeed C extensions. I'm looking for solutions. the move to WASI 0.3 will certainly help with that.
29.
Show HN: Sandboxing untrusted code using WebAssembly(github.com)
76 points by mavdol04 8mo ago|25 comments
30.
by mavdol04 9mo ago
Yep, exactly. We stick to JSON to make sure we pass data, not behavior. It avoids all that complexity.

More ›