Mauve 👁💜 @mauve@mastodon.mauve.moe

If I eveer get a brain scan it'd be cool to do two where I meditate to get full awareness of my body and another where I detach from it to just be in my mind's eye and do a diff on the states.

I should really commit my dotfiles before the next time my pooter gets borked.

Finally got around to updating my waybar config to have a thingie to show the current phase of the moon. 🥰

Been playin a lot of no mans sky to unwind lately

@yosh I'm just too addicted to mutable references on the heap being trivial in JS >:P

@yosh I think my issue is that I am trying to reuse it both in a closure and later in some other code.

I think I just need to rewrite this using channels and treat the two simulated peers as fully separate peers + have them listen on incoming events generated from a third thread doing the networking.

Coding in rust makes me feel so stupid :P

It seems I need to place the mutex into an arc after all?

`Mutex<Option<TunnelManager>>`

is a lot more reasonable. :P

```
{
let mut tunnels1 = tunnels1.lock().await.unwrap();
tunnels1.open_tunnel(route_id).await?
}
```

Ain't it funky

Here I thought I was some rust hotshot but then I need to share a mutable value between threads.

`Arc<Option<Mutex<TunnelManager>>>` is one hell of a type. :P

This post brought to you by the Minima blockchain whitepaper. But honestly it seems every single neat protocol is doing this. https://docs.minima.global/minima_pdfs/Minima_Whitepaper_v11.pdf