Jędrzej Stuczyński
Jędrzej Stuczyński
I will look at it as soon as I have some time. Please do not merge it before then.
Do you want to distinguish cover traffic from real messages? (for both sent and received)
it's definitely not in the scope for this feature, but I wonder if conceptually it would make sense for `AsyncRead` and `AsyncWrite` to completely bypass message reconstructing and operate on...
noise is dead. long live the noise
Hey! Can you elaborate a bit more about the "advanced use" you have in mind? Because it should be the case that a single application wanting to use the mixnet...
Yes, sorry. I've been pondering about this one, and I'm not entirely convinced whether broadcasting received messages to all websocket connections would be the best idea. While it might work...
For the context, the issue here is that our allow list doesn't correctly take ports into consideration, so: ```rust #[tokio::test] async fn test() { // this fails let mut filter...
@dependabot rebase
@dependabot rebase
> @jstuczyn - do you still see this being problematic now? yup, it's still very much a thing