social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

487
active users

#iroh

1 post1 participant0 posts today
Replied in thread

@joxean

@n0iroh at iroh.computer may be an interesting case study for you. is in turn used by @delta for instance.

You can read more on how use iroh in their blog post at: delta.chat/en/2024-11-20-webxd

Iroh's programming language used is though, but via the support it may be usable in the languages you mention, but I am not sure.

iroh. less net work for networks
iroh.computerirohless net work for networks

Starting work on #kikai networking using #iroh as a messaging backend.

The idea is to keep it as simple as possible, sync ticks. Only the units position and hp is synced. Clients can subscribe to full syncs of #Uxn state for some units (like selected ones) in order for debugging and custom unit UIs to work well.

Continued thread

The coolest part is that it has a LAN working over #iroh real-time channels. Everyone can assign self an IP address and ping each other, telnet etc.

with e2e encrypted forward secrecy connection between machines! 🤯🤯🤯🤯

Currently playing around with github.com/MightyShadow702/v86 which leverages github.com/copy/v86 into DeltaChat. Effectively allowing you to run a 32 bit .iso file inside DeltaChat as a webxdc application.

Right now tcp/ip is wired up with realtime communication over iroh 💥 🧠

x86 emulator for Webxdc based on Copy's v86 emulator - MightyShadow702/v86Emu-webxdc
GitHubGitHub - MightyShadow702/v86Emu-webxdc: x86 emulator for Webxdc based on Copy's v86 emulatorx86 emulator for Webxdc based on Copy's v86 emulator - MightyShadow702/v86Emu-webxdc

Our #iroh relay servers are so blind to the traffic that they don't even know when #p2p #holepunching has succeeded for two nodes. Yet people keep asking what our hole punching rate is.

Honestly, we don't know! And we don't know how to find out without violating everyone's privacy. How to square this circle?

Some users of private centralised deployments tell us it is better than anything else they tried, hence they switched. But we don't have numbers, and who believes a claim like that?

Replied to iroh

@n0iroh

is a super fascinating project in the ecosystem. You always have incredible progress in roadmap briefings, and a very good codebase + docs to get folks going.

Local-first is a next-gen computing paradigm.. one of paradigms that threaten cloud and browser vendor hegemonies.

One thing is problematic in local-fist land. There are N pioneers and N sync mechanisms / protocols.

Until there's any form of common open standards track things remain too risky technology bets.

Well, that's a bit disappointing:

From the iroh-ffi commit log:
We found that in practice our support for go is just far too cumbersome. Go doesn't take well to CGO dependencies to begin with, and integrating such a thing at the networking layer just isn't worth it.

Go projects that want to interact with iroh should consider standing up a separate binary & communicating over a network-backed RPC protocol of their own design.

I was hoping to use #Iroh in a #Golang project. Is anyone trying to build an "Iroh daemon" like this? I might be willing to try and help out (though not knowing much #Rust could make this tricky).
We found that in practice our support for go is just far too cumbersome. Go doesn't take well to CGO dependencies to begin with, and integrating such a thing at the networking layer just isn&#3...
GitHubchore(go): remove go language support · n0-computer/iroh-ffi@6c4371cWe found that in practice our support for go is just far too cumbersome. Go doesn't take well to CGO dependencies to begin with, and integrating such a thing at the networking layer just isn&#3...

It's been a bit of a journey learning #rust and #veilid and #iroh but these last few functions were very satisfying to write. This code triggers a download of an Iroh-blobs based file from it's hash by establishing tunnels to peers in a group using a multiplexer I built using Veilid AppMessages over private routes. The code to get here was hella messy but these functions felt pretty elegant.

github.com/OpenArchive/save-dw

GitHubImplement iroh blobs by tripledoublev · Pull Request #9 · OpenArchive/save-dweb-backendImplemented VeilidIrohBlobs Reworked tests as part of hyphacoop/openarchive-dweb-backend#20

For the last several months I've been working on making a federated app.

I just finished migrating it to use the latest iteration of our new #leafprotocol data format on top of the #willowprotocol and so far it's going really well.

In this post I share some of the concepts and rational behind the Leaf Protocol:

zicklag.katharos.group/blog/in

zicklag.katharos.groupIntroducing The Leaf ProtocolAn overview of the experimental Leaf Protocol for federated, local-first app development.