tpr VS tui-journal

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.

Still working on mt TUI app Tui-Journal After the big release the last weekend. Currently I'm working on integrating MakeFile the CI/CD pipelines and I'm contributing to other TUI projects to get familiar with other brilliant approaches for TUI applications in rust.

Here are links for the project on GitHub and on Crates.io

I'm working on new features for my app TUI-Journal, like enabling editing the journal via external editor which could be tricky on windows platform or if the user sets his default editor to be something external like vs-code.

As I wanted to build a robust back-end for my TUI-Journal app, I knew I needed the right tool for the job, and Golang proved to be the perfect choice for web servers.

I'm excited to introduce TUI-Journal, the go-to journaling and note-taking app for those who prefer living in the terminal like me. It offers a simple and intuitive interface for managing journal entries and notes (using a combination of VIM and Emacs motions), featuring two local back-ends to store your data: Plain JSON text and a SQLite database.

I'm working on a supposably simple journal app, which I want to over-complicate to explore as much as possible from rust echo-system. My plan to have three front-ends: (TUI, Desktop, Web) and three back-ends (simple json file, Database and micro-service). Still though with the very first stage (TUI front-end, with Json Backend)