Actyx compatibility

[rklaehn]

Actyx is now a well funded research org for resilient software.

It would be nice if they would use iroh-embed instead of ipfs-embed.

Here is a list of things that we would need to support their use case:

• mdns
• advanced peer manager
• private swarms
• raw block read and write
• purely local store api, preferably syncronous
• gossipsub access
• broadcast to local peers

Not everything has to be exactly like it is in ipfs-embed. @rkuhn will be able to adapt it a bit and maybe even help a bit with things like the peer manager. But at least there needs to be a functional equivalent for each of the features.

[dignifiedquire]

We already support MDNS and Gossipsub access. (Under the hood at leaset)

[rklaehn]

At least for gossipsub, this also needs to be exposed in the api.

[rkuhn]

Thanks for opening this @rklaehn! The list looks mostly correct, with the lone exception that you care more about synchronous storage than I do — as far as I’m concerned asking sqlite is almost as “bad” (better: demanding) as sending a network request to some Oracle instance, lots of stuff can go wrong and it will take lots of CPU cycles.

As for lifetimes: “I don’t see the code anymore, I only see blondes, brunettes, red heads … ” (and I’m not the one, just as Neo wasn’t)

Regarding the peer manager: Actyx is currently maximally greedy, using the ipfs-embed address book to stay connected to every node that we can find an address for. This will eventually need to be refined, of course, but for now it is not complicated.