openmiko VS CppCoreGuidelines

Have a Wyze Cam V2 running openmiko. I can pull the feed via the camera's IP, but Klipper (Fluidd, Mainsail on BTT CB1) shows like below. Additionally, moonraker-timelapse throws an error. This was working fine until I tried Hyperlapse. Now I can't wrap my head around this

I'm running MainsailOS, and a Wyze cam v2 running openmiko. I have Tailscale installed on the Pi for remote access. In Mainsail config, I have the camera configured via private IP. When I access the web control panel externally, I do not get video output. Is there a way to get this to work? I do not think there's a way to connect the Wyze cam to my tailnet.If it's not possible, have any good recommendations for a good, cheap, wide-angle (110 degrees FOV or better) camera I can purchase? I wouldn't want to spend more than $25 for one. Quick search yielded this one, but don't know if there's a Klipper-community recommended one that everyone uses.

you wish lol. the mod allows you to get highest possible resolution video out of it without all the compression pixelation. its super easy to install. but it does take a little bit of linux knowledge to edit config files and stuff. heres the link if interested: https://github.com/openmiko/openmiko

I bought a used Wyze Cam V2 relatively cheap and installed OpenMiko on it for example.

I have a WyzeCamV2 running OpenMiko firmware, which supports (and I have configured for) H264 RTSP streaming. I can view the video stream through VLC with the url rtsp://192.168.1.199:8554/video3_unicast. I am executing the command docker run -p 8081:80 --name mycamera -e AGENT_CAPTURE_IPCAMERA_RTSP="rtsp://192.168.1.199:8554/video3_unicast" kerberos/agent:latest on my host. The agent seems to run fine and I can connect via browser. With our without AGENT_CAPTURE_IPCAMERA_RTSP... set, I cannot add the RTSP stream; no cameras show attached and when I try to connect one via dashboard->settings, it just spins. The logs aren't really helpful (see below).

OpenMiko is one example.

That's why I only use cameras flashed with open firmware: https://github.com/openmiko/openmiko

If all else fails, you can flash different firmware and use them locally. I'm using [OpenMiko](https://github.com/openmiko/openmiko) on my Wyze Cam v1 (I'd assume there's a similar open-source project for the v3), and Wyze themselves publishes an RTSP firmware. Without a bit of technical know-how and some supporting hardware (namely a router than supports OpenVPN) you won't have access to the stream off your local network, but you can stream locally with VLC Player.

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.