tpr VS rustypwneddownloader

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.

Just throwing in that the dollar value isn't the only cost. I've been using an automated release workflow tomanage signing, eg

https://github.com/technion/rustypwneddownloader/blob/main/....

This worfklow isn't usable with these new rules, and I'm having a hard time with the assertion that moving builds to my desktop to use a hardware signing key and uploading them in a non automated, non transparent fashion is an improvement on security.

I just grabbed my (very basic app)[https://github.com/technion/rustypwneddownloader] and ran a cargo vet init. Out of the box there were 145 dependencies found (ouch.. that already feels like a bad trajectory).

I've written and released a Rust port of the pwnedpasswordsdownloader: https://github.com/technion/rustypwneddownloader