3 ms·

I have been working on a similar project here: https://github.com/inet256/inet256 https://github.com/inet256/inet256 The focus is more on establishing an upward

I have been working on a similar project here: https://github.com/inet256/inet256 https://github.com/inet256/inet256 The focus is more on establishing an upward facing API, to develop p2p applications against. You can write your p2p app in whatever language and just connect to the INET256 service. It makes it pretty easy to experiment with a new routing algorithm, and eliminates much of the peering and transport security boilerplate. Is Pinecone intended as a Go library, or will it eventually run as a separate process like Yggdrasil? How will this be exposed to the other matrix applications, which AFAIK are not written in Go?

neilalexander 5y ago
The current implementation is written in Go largely because it was the obvious choice for integration into Dendrite, the next-generation Matrix homeserver, which is embedded into the Element P2P demos. Pinecone currently exports a net.PacketConn, and for the sake of Matrix federation transport, we layer on uTP+TLS on top to give us encrypted stream-oriented connections for HTTP. If we are successful at achieving our goals then we will write a formal protocol specification and assist with the creation of other implementations.