apitman

Awesome thanks

One way I like to think of it is that Fabrice creates prototypes interesting enough that other people choose to spend their entire careers maintaining them.

Maybe pi is a spec. Just not written by man.

Is there no annual fee on all IPv4 blocks, or just legacy ones, which I'm assuming means blocks that haven't changed hands in a very long time?

I discovered p2claw the other day and it's really cool. I'm a little surprised you're running Iroh as well. Why not just use WebRTC for everything once you're forced to for the browser anyway?

IPv6 solves a lot of it, and maybe in another 20 years we can rely on it.

Similar on the technical level (though QUIC vs WireGuard), but that would make your app dependent on Tailscale, and require your users to have Tailscale accounts. You'd also be limited to Golang currently.

In theory you could run Headscale, but you're really working against Tailscale's intended design at that point, and Iroh was built for this from the ground up, so what is Tailscale buying you?

If you're new to Iroh, my mental model is roughly "Tailscale at the application layer instead of the network layer".

If your question is, "why not just use Tailscale?", look at it from an app developer's perspective. If you want to release an app and have instances of your app be able to easily connect to each other, you could theoretically embeded Tailscale functionality into your app, but then the users of your app need Tailscale accounts, and your app is dependent on Tailscale.

Iroh lets you embed this functionality directly, and provides public fallback relays. If your app gets too big for the public relays, using your own relays is the flip of a switch.

You'll get a direct connection in most cases, but sometimes it will need to fall back to relays. n0 provides free relays, but ultimately that can get rather expensive. You can also run your own relays for your app.

I'm sure everyone has seen this by now but just in case: https://www.destroyallsoftware.com/talks/the-birth-and-death...

> Getting screwed by browsers though because their WebRTC implementations completely ignore Yggdrasil addresses.

How does that work, exactly? How does the browser differentiate between Yggdrasil addresses and others?

Technically WASI 0.1, but I used it (via Extism[0]) to implement a simple library[1] that's written in Rust, but lets you easily add login to backends in Rust, Go, and Node. Would be trivial to add other lanugages supported by Extism.

Overall I loved the dev experience. It's sort of like writing a C library that can be dynamically linked in other languages, but with much better security and much easier distribution because you don't need to worry about the OS or CPU architecture. Literally the same .wasm file everywhere.

[0]: https://extism.org/

[1]: https://github.com/lastlogin-net/DecentAuth

I think the next frontier for competition is speed. Instead of constantly context-switching between multiple agents that I have working on various tasks, I want a single agent that can rip through any prompt in a few seconds, so I can stay in flow on a single task.

OMP is a fork of Pi[0], which is my preferred harness. Feels solid and minimal. I don't even use any extensions, skills, or modifications. Usually don't even use an AGENTS.md. Just create a small spec.md and/or plan.md for most experiments.

[0]: https://pi.dev/

That looks pretty nice. How does it compare cost-wise to just using OpenRouter?

Rainbows End

Been playing with this lately. Definitely worth checking out. Makes really nice tradeoffs IMO.

I actually just found microsandbox this morning and it looks really solid. One thing it's lacking is GPU support. With smolmachines you can use Vulkan through virtio-gpu/Venus which is quite nice. Can you give more details on what you prefer about microsandbox?

One area this is desirable is AI agents. Often you just need to spin them up for quick ephemeral tasks, but you want more isolation than containers give you. I'm still looking for a good solution here. A cool one I've been playing with recently is https://smolmachines.com/

> The fact that neither STUN nor TURN contain any way whatsoever to accomplish any kind of rendezvous without yet another signaling path boggles my mind

Interesting. Can you expound on this a bit? How does ZeroTier do it?

I've recently been exploring options for allowing web apps to access LAN services. For example, a WebDAV server so you can watch local videos in the app without streaming them through a server.

You can actually achieve a form of discovery if your service registers itself using mDNS for something like `service.local`. Browsers will allow direct navigation/redirection to `http://service.local`, but they'll block any fetch/XHR requests due to mixed content rules, even if you have CORS configured. And of course you can't get a cert for `.local` domains.

Newer things like Chrome's LNA[0] are actually really helpful, because (for now at least) if the user grants the permission, fetch/XHR will go through, but you'll get a bunch of mixed content warnings in the console.

It seems like the only way to fully support this use case currently is with WebRTC, which is pretty sad.

[0]: https://developer.chrome.com/blog/local-network-access

Any idea if Safari is on board?

Dang would love to have both in the same chip.

Thanks Ethan!

IndexedDB

If your agent has access to the internet at any point it may read something that convinces it to try breaking out of its sandbox.

Containers are not security boundaries. Vulnerabilities in containers are much more common than in VMs.

Personally I just ask the AI to put everything into index.html.

Perfect, thanks!

I think GP meant that ham is a mesh in the sense that individual operators will communicate and spread information.