digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

823
active users

#iroh

1 post1 participant0 posts today

Now I have to develop a protocol for exchanging data between peers. The protocol is bidi, and I will use #iroh as a basis. I think I am going to use JSON messages for now, but maybe go over to use msgpack later. It really does not matter.

What matters more is the actual protocol and what kind of messages are exchanged and the behavior. I guess I have to think really hard to make this nice.

While yours truly has been head deep into the 1.0 work on QUIC Multipath rather than keeping you entertained with posts here, a lot of cool things happen that haven't been mentioned. Here are 11 projects from the awesome list today, using #iroh to make cool #p2p applications.
github.com/n0-computer/awesome
1/x

GitHubGitHub - n0-computer/awesome-iroh: Curated list of awesome stuff built on & with irohCurated list of awesome stuff built on & with iroh - n0-computer/awesome-iroh

😏 Ah, the age-old quest for peer-to-peer connections without the digital equivalent of a Rube Goldberg machine. 📠 Introducing 'Iroh'—because who knew connecting two computers was as mythical as finding a #unicorn that writes perfect code with GitHub Copilot? 🦄💻
github.com/n0-computer/iroh #peer2peer #Iroh #GitHubCopilot #techinnovation #mythicalconnections #HackerNews #ngated

GitHubGitHub - n0-computer/iroh: peer-2-peer that just workspeer-2-peer that just works. Contribute to n0-computer/iroh development by creating an account on GitHub.

Because I didn't learn enough today, I decided to try out #iroh to develop a custom P2P protocol.

Works great, and is surprisingly fast!

Only sad thing that it is one of these projects that want to nudge me into Discord to join the community 😞 .

@n0iroh

Replied in thread

@joxean

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

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

Iroh's programming language used is #Rust though, but via the #WebAssembly 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

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 💥 🧠

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
Replied to iroh

@n0iroh

#Iroh is a super fascinating project in the #LocalFirst 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.

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.
Replied in thread

@silverpill @smallcircles #iroh which is implementing the willowprotocol.org/ does all those things I want from a storage, connectivity, and replication standpoint.

If I were to implement the network that I'm imagining, I think I would probably still need Iroh, even if I supported ActivityPub.

But instead of supporting ActivityPub immediately, I'm trying to understand the smallest specification that I need to accomplish my goals.

2/3

willowprotocol.orgWillow Specifications - WillowProtocols for synchronisable data stores. The best parts? Fine-grained permissions, a keen approach to privacy, destructive edits, and a dainty bandwidth and memory footprint.