I caught myself watching an AI video on youtube a few days ago where the narrator's AI voice had deliberate instances of stammering and stuttering. It's definitely simple to have these introduce idiosyncrasies just through specific prompting.
I came here to post this one. For about 25 years of my life I was tying my knots the wrong way and I just thought shoelaces just had to be re-tied periodically. I don't remember where I learnt to just tie the loop the other way. Now strain on the laces just serves to tighten the knot.
I like the board UI and it's a cool project idea. Did you find any good resources on programming the board representation and identifying legal moves? There doesn't seem to be a standard library or algo reference that I've seen for such a common problem.
That's right -- Duplicati constructs the giant house-of-cards DB). I sometimes need to run a $> ps -ax to remember which one I'm using when it comes time to change the config.
They have some major differences. Enough so that I first tried Duplicati and ran into corruption issues so frequently that I sought out an alternative and luckily found Duplicacy.
Duplicacy has been stable for years now and I gladly pay the commercial license. It seemed like Duplicacy constructs a giant DB of all the files and manages everything that way, whereas Duplicacy's approach is much simpler and is less prone to corruption. The large DB approach seems to fail when the backup set contains a large number of files that many users manage.
I suspect you're using the rtsp protocol to get the A/V streams from the camera, in which case I would consider your software another front-end for an IP CCTV system-- is that right?
There are plenty of IP CCTV solutions that use any number of manufacturer's cameras because of standard protocols, and that sort software should be fine to publish. However, if you're spawning the streams because the camera mfg. has a closed protocol and you're exploiting some bug, then maybe give it some more thought.