schrodingersket

Quite so! I'm sure I could have fiddled with ffmpeg commands, set up a custom Steam launcher, etc. I probably would have if OBS Studio's preview performance introduced too much overhead.

I also discovered that OBS Studio can be installed directly from the Steam store, which makes makes the whole thing feel just a little more seamless (I'm streaming to the Steam Frame). I don't mind trading the extra install space for that feeling, especially since OBS is OSS. It was really pleasant to have this all "just work" end-to-end on both Linux and Windows stacks.

It was very heartening to have this experience! I tried to refrain from harboring overly positive or negative expectations while setting this up and am quite content with how it turned out (especially since every part of this stack can run on Linux; this morning, I swapped out the gaming desktop part of this setup out for my Linux dev laptop + eGPU just for fun, and it all works identically).

Surprisingly low. Steam reports about 12-15ms latency over the 6GHz dongle, and the Internet seems to think that the capture card preview adds about 49 ms; I haven't tested the latter claim myself, but ~65ms feels like a reasonable number. I don't usually seem to notice <100ms latency when I play games (which could be a skill issue on my part), and indeed I don't notice delay between the VR headset image and the direct HDMI passthrough that goes to my desktop monitor (the non-dummy display)

I had initially only planned to use this setup for turn-based games, but after this pleasant surprise, it looks like I get to explore some other kinds of games :D

I haven't spent much time in the video processing/streaming space, but I was delighted to discover OBS Studio this week while putting together what has turned out to be an incredibly cozy little entertainment setup by feeding the two gaming consoles and geriatric gaming desktop I've acquired over the years into an HDMI switcher and USB HDMI capture box that in turn streams the feed into an OBS Studio preview (launched from Steam) running on a dummy display.

Launching OBS Studio through Steam lets me stream that preview to my VR headset over a 6GHz WiFi dongle and play games wirelessly in what feels like my own little private theatre. OBS Studio was the puzzle piece I hadn't figured out when the headset showed up last weekend, and I've been really impressed by its performance so far... I think this setup even shaved some latency off when playing online, since consolidating the consoles next to the router let me hardwire them.

Many many thanks to the OBS Studio team for making software that's helping me live out a small part of what I remember hoping technology could be like back in the 90s. I am grateful (:

Not at all in my anecdotal experience! My Prusa Mini just connected to my old Pi via MicroUSB and it all "just worked" for me. Ended up adding a Pi camera to the setup and installed the OctoLapse plugin to automatically generate timelapse videos of my prints; been very happy with it all so far.

I keep one of my keys in a fireproof safe at home, and the other on my keychain as my daily driver. If a site allows me to enroll multiple U2F keys, I just bring the backup to work (my home office, currently) with me the next day and enroll it then. For sites that only allow a single key (looking at you, AWS), I will usually enroll the key I have on me, and then when I have both, I write the same TOTP seed to both keys (usually by scanning the QR code with each key plugged into my phone before entering the one-time code used to verify and finalize TOTP enrollment) and use that instead so that there's effectively a TOTP duplicate.

This gives me a pretty convenient list of sites I've set up the Yubikey with (at least for TOTP), since Yubico's OTP app lists all the sites I've used it for.

If a site only allows a single U2F key to be registered, I'd rather have a backup with TOTP over the better security of a single U2F key, so this arrangement works reasonably well for me.

I do the same thing, but I use the Twilio CLI to send me a text so that I can get up and walk around if the process is blocking other work. (:

FIPS-ready in the sense that a FIPS-compliant SSL lib can relatively easily be dropped in. I'm bad at marketing things, so I won't try too hard - this project uses CentOS to use an Ansible deployment to lay down a replicated Consul deployment that runs the backend for a Traefik reverse proxy, all of which runs behind behind an opportunisticallly-encrypted LibreSwan network to get both a) TCP packet-level encryption and b) easy scalability. New services can be registered either from a REST request, or a CVS-trackable YAML file.

I'm looking to move it to Docker images soon (the code is set up to be fully Compose/K8/etc. ready), but haven't had the the time yet and if any Go gurus have the time to spare to inform me how bad my code smells, I'd love it.

I hope this is useful to someone (:

Forgive the use of Vagrant - I've had to work in many bare-metal enterprises. I'm looking at ansible-docker to modernize this project a bit more.

Links aside, it seems there's another out there with a kindred username!

Also, great write-up. That article is awesome!

Ha! You beat me to my comment. I have the same lock. It's really great (:

I got a Samsung NFC lock recently so I could unlock my house with an NFC chip I had implanted in my hand about a year ago. Awesomeness of having my house key in my hand aside, the lock itself is very capable, and I'm quite happy with it as a standalone device. It comes with 5 NFC FOBs which will unlock the door, and each one is tied to a unique PIN combination. If you can't find your FOB, you can still use the PIN. It's been really effective at my house and for house guests.

jQuery itself is rarely a problem. It's a tool, just like any other library, and it's very effective at solving the problems it sets out to. But at the end of the day, it's still just a tool - and tools aren't solutions by themselves. Good application architecture usually points to the right tool for the job. I've developed on projects where jQuery, requireJS, AngularJS, Angular 2+, and React have each provided the best tool (and sometimes in conjunction with each other!) for what we needed.