Jonathan Rascher

Hmm, I wonder if the update didn't stick for some reason. (Still says `"stp": true` in the response.) The only other thing I can think of is that I may...

I think I understand part of the problem. It looks like this is how quitting normally vs. via "Close Content" differ: * "Quit RetroArch": `CMD_EVENT_QUIT` => `retroarch_main_quit` (calls `command_event_save_auto_state`) *...

A partial answer... it seems that despite the name, `CMD_EVENT_CLOSE_CONTENT` isn't fired when selecting "Close Content" in the menu. It appears to only be used for the "Close Content" hotkey...

I wonder if #16014 incidentally fixed this. Will update to 1.17.0 and retest soon.

Okay, I (finally) retested this in 1.19.1, and unfortunately the bug still exists. With "Quit on Close Content" enabled, the autosave state is still written twice on exit: once when...

I think this may be more impactful now that shared Tailscale nodes will have [different IPv4 addresses in different tailnets](https://tailscale.com/blog/choose-your-ip/#natural-solutions). Previously, one could just point an A record in public...

Thanks for this! I am using it on my Ender-3 Pro with a CR Touch, and it seems everything works well! I'll likely want to build my own firmware to...

Interesting. I poked around with that a bit. ``` site1.example.com { // no bind here } site2.example.com { bind tcp6/[::] tailscale/node } ``` still exits with `panic: connection already exists`...

Sorry, typo (fixed above). With `bind tcp4/0.0.0.0 tailscale/node`, it's not listening on _IPv6_, which I want for my setup. (With the default Debian dual-stack setup, binding on `[::]` listens on...

Hey, thank you for the thoughtful reply! > You can't just prepend this on the `body` before you send the message? > > How are you sending the messages to...