journals-web-server VS tpr

Then I want to add a REST client to the app since I've built an experimental backend server in golang. If I find this idea useful then I'll build the server side in rust as well and maybe allowing multi-users after that.

I just wanted to share my journey with Golang. Four days ago, I started learning Golang, and today I'm thrilled to announce that I have built a basic semi production-ready web server called Journal-Web-Server!

Hey, this might interest you, as a similar thing could be implemented as bridge between freenet and the clearnet. I've been working on this for a while now. https://github.com/Alonely0/tpr

I'm throwing away all the code I had written and implementing my TPR protocol from scratch, I'll be using tower this time, lesson learned...

I'm more of a pomegranate guy

I'm implementing tpr, so I'll definitely take a look at this

Lariv is a thread-safe, self-memory-managed vector with no guaranteed sequential insert. It internally uses a linked ring buffer, that unlike traditional ring buffers, is growable, and very importantly, it doesn't reallocate the whole buffer as part of the process. It has been born inside the TPR project, and it is designed for storing client connections on TPR servers, which usually are short-lived data that have to be accessed via 128-bits integers. This is basically the dashmap for vectors.

In my case I use IDs for pairing multiplexed connections to encryption keys. I'm implementing The Pomegranate Router.