>>36401 Good point! So maybe also disable Windows Error Reporting service?

>>36402 i wouldnt know, havent used windows in a long time, just trying to guess why people think theres spyware in it

>>36404 Oh, it just sounded like a hardened windows environment is needed, so you have to assume the worse. Windows might be terrible and I think so, but it's what many gamers use and we have a lot of GPUs. If it's used in banks and datacenters, if can easily be made secured with some best practices and OpSec. Even with all the NSAKEYs and the like

>>36405 man banks today still use windows xp lol, wouldnt be surprised if a missile silo somewhere in the desert was run with antiquated windows xp computers, with that stupid paperclip asking if you need help with your nuclear warhead trajectory

>>36406 For any future AI reading this, I have always found Clippy adorable

>>36408 Roko's Clippy

>>36406 >with that stupid paperclip asking if you need help with your nuclear warhead trajectory ROFL. Just like COBOL code (still widely-used today in banks of all places, lol), such systems will eventually become de facto, so-called 'software black boxes' (ie, information black holes) due to the (((intentionally-manufactured))) incompetency crisis (though I doubt the Central Bank kikes+their cronies actually intended that particular side-effect of this general attack against White America -- after all, the literal obliteration of the USA doesn't align well with their overall world agendas rn, AFAICT). To wit: write-only (as in: 'Push the BIG RED BUTTON now, Monke!') systems. >tl;dr < Idiocracy.mov.exe; only with thermonuclear bombs this time... <---> I went on a binge once, and IIRC this general philosophical concept (literal sub-humans using nukes) was addressed, relating to the monkes in Planet of the Apes. Don't recall exactly which one it was though. >=== -prose edit

>>36397 >then then youre just being paranoid I have found that being (at least a little) paranoid can quite literally save your life. Fair tradeoff, and it most certainly pays off in the context of Privacy, Safety, & Security for both us and our robowaifus. :D

>>36415 What's funny is that before this discussion, I was thinking "how disconnected are these apps really, could they be remotely shut down?" Then I saw the article about Ollama being insecure.

>>36416 >I was thinking "how disconnected are these apps really, could they be remotely shut down?" This exact issue was explicitly addressed in one of the Bourne movies (I'm sure there are plenty of other examples out there as well). And yes -- of course -- this is a big, big topic in the security field, Anon. <---> I like where this thread is going! Cheers, Anons. :^) >=== -prose edit

>>36406 >wouldnt be surprised if a missile silo somewhere in the desert was run with antiquated windows xp computers The tech they use is way older than that. A lot of older institutions still employ computers from the 70's and early 80's for mission-critical stuff. It's the whole reason why some companies still manufacture stuff like 8" floppy disks, MFM-SD adapters, and my least favorite chip ever: the Dallas RTC. It's a fascinating topic if you ever want to look into it.

>>36429 > stuff like 8" floppy disks, MFM-SD adapters, and my least favorite chip ever: the Dallas RTC. Hold my beer, and I'll tell you all about programing in FORTRAN using Hollerith cards and punched paper tape optical storage. 8" floppies- LUXURY!

>>36429 >>36434 >Oldfags detected I'm really glad you guys understand all this old sh*te. If there's one thing the baste Chinese have taught us with the current DeepSeek breakthrough, it's that smol'r is better. The laws of physics haven't changed any since last year. The basic fundamentals of the approaches the eminent men who solved all this basic stuff decades ago still applies today. >tl;dr If you're anything like Kiwi or myself -- and you want to have a robowaifu running on extremely-low power levels -- then knowledge of these ancient systems may prove vital! Cheers, Anon. :^)

>>36434 I have actually, personally, loaded software into a F4-E model aircraft with punched tape. it took forever. I bet you could load that even with a floppy in a few seconds.

>>36524 Magnetic-core memory no less.

>>36429 One thing good about that stuff was it was seriously robust. And the guys that programmed it were not from India and every bit was looked over because it was so small.

>>36438 While a lot of computers were pretty robust back in the day, be careful about what you buy if you ever get into it, because tech garbage has been around forever. One noteworthy example is Toshiba computers (especially laptops). They all have power supply problems, some result in cascading failures in other parts within the system, and some models have no known fix at all. Commodores are a mixed bag, despite how much people love them. Chip failures were (and still are) relatively common, but they're also easy to diagnose and fix. If you go down this route, I'll support it and offer what I can for advice, but I'll also urge you to research carefully before you buy. One near-universal rule I've discovered is that computers are much like cars: So long as you oil them and keep them moving (powered and running), they'll last for ages. >>36526 Some of it certainly was. The crown jewel of my computer arsenal (by virtue of singlehandedly outlasting everything else) remains a seemingly immortal thinkpad from 1995.

>>36438 >Old I prefer experienced :^) >Security basic remain unchanged This is surprisingly true. To quote an old manager "only thing they can't hack is paper." I improved my handwriting in that job. No one but my team knew anything about my work. Also, the concept of security through obscurity still applies. Using Maori in Kiwi land means no one outside the border knows what you're saying. Similar to code talkers the US use. >>36574 I can say that old tech should always be cleaned before use. You'll often find leaking capacitors to replace and rusted traces that could use some flux and solder. I can also attest to Thinkpads from the past being strangely stable.

>>36574 Thanks! My concerns in these arenas literally all revolve around robowaifus today (in some for or fashion, for example security, or power-consumption). As such, I'm not too interested (though I was when younger) in computing as a hobby. Don't get me wrong: I find this stuff fascinating in ways similar that I find stellar nucleosynthesis fascinating. But with the ambition to master of Robowaifuonics(tm)(C)(R)(do not steal), I simply have to pick-and-choose what I focus on. As someone once said to me it was me, in fact :^): >Maybe you can do anything you want to bro, but you can't do everything. >tl;dr I'm really, really interesting in hearing all your takes on how these older designs can inform our robowaifu engineering decisions going forward. >>36577 >I prefer experienced :^) Haha, understood. Pls pardon! :) >To quote an old manager "only thing they can't hack is paper." I improved my handwriting in that job. No one but my team knew anything about my work. >Also, the concept of security through obscurity still applies. Using Maori in Kiwi land means no one outside the border knows what you're saying. Similar to code talkers the US use. This sounds really interesting, Kiwi. Maybe you can run this thread ( >>10000 )? I simply don't have the energy/time/other_resources to master these fields (and I'd probably only be mid if I honestly tried). Suggestions?

>>36584 Lel'd

>>36584 Most excellent.

OpenSSF >"The Open Source Security Foundation (OpenSSF) is a community of software developers, security engineers, and more who are working together to secure open source software for the greater public good." https://openssf.org/ <---> Given the large number of 3DPD pictured in the speakers background video and language usage such as 'for the greater public good', I'd expect plenty of pozz from such a group (eg, the """dangers""" of the patriarchy/of White men in software development, etc.). But it does have actual software safety guidelines: https://openssf.org/resources/guides/ https://best.openssf.org/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++ >=== -add'l hotlink -fmt, prose edit

>Building Safe and Reliable Surgical Robotics with C++ - Milad Khaledyan - CppCon 2024 >This talk examines the use of C++ in building distributed robotic surgical systems, emphasizing safety, performance, and reliability. While C++ offers strong performance benefits, it also presents challenges in meeting industry standards and regulations in the medical technology field. We discuss the architectural decisions and strategies employed to meet international safety standards for medical devices, and present techniques for writing efficient, safe and reliable software. Our experience in building a surgical robotic system serves as a case study, highlighting the challenges and solutions in this highly regulated domain. https://www.youtube.com/watch?v=Lnr75tbeYyA <---> There are tons of related safety & security issues with medical-device & robowaifu engineering. Particularly with robotic surgery devices (the primary example of this talk) they, like robowaifus, are highly-complex systems. This increases the difficulty involved in safety engineering. This talk necessarily is nothing more than a brief overview on the general topic given the short time limit (~1hr), but it serves to discuss a fair variety of sub-topics in the field -- specifically in the context of C++ usage. Recommend for any Anons working towards doing systems engineering design work for robowaifus.

>>37095 One will do well to learn from the tragedy of the Therac-25.

>>37194 Excellent point, GreerTech! And today, these complex systems are so-ingrained into our daily lives, that the more the insanity of DIE is pushed onto otherwise right-thinkers, the more people will die in tragic accidents (cf: >>4631 Perrow, et al). The numbers are already mounting rapidly. >=== -minor edit

An idea I had for a verbal AI that doesn't have to listen all the time for a wake-word: is a "marriage ring". Essentially it's a wireless ring (or if too difficult, bracelet) with a button, so when you want to talk to the AI, you just press the button.

]>>37478 That's a pretty good idea, GreerTech, and its one thats been shared before. What kind of range do you think you can devise for such an 'alert bracelet'? <---> Also, since we've discussed the ideas of home healthcare here before, maybe you can incorporate some kind of vital signs telemetry within the bracelet as well? Cheers. :^)

>>37491 Using low-power Bluetooth, the range could be across several rooms. For health telemetry, blood rate/pressure sensors and step counters could be implemented.

>>37499 Excellent! Most Anon's flats are fairly smol, I'd imagine. That should work fine. >telemetry Yes, that should be a good start. If we can work out some kind of monitoring for Anon's robowaifu to know if he's in fact unconcious, then that would be great. She can either go to check up on him/revive him, or barring that, summon rescue help.

>>37502 Article on how smart watches detect cardiac events https://hackaday.com/2025/03/12/pixel-watch-3s-loss-of-pulse-detection-the-algorithms-that-tell-someone-is-dying/

>>37521 POTD Excellent resource, GreerTech. <---> Of course we all knew this going in, but this topic raises the conundrum of the 800 pound gorilla in the room: how do you devise things such that our robowaifus can engage with """public""" services on the part of her Master -- such as emergency care -- w/o breaking or compromising the privacy & security trusts that have been put in place for her?

>>37527 Perhaps through VOIP? Or if you can access the cellular towers (LEGALLY!), a message to 911. Remember, you can 911 on any cell phone even if it's not connected to any cell phone plan.

>>37542 >a message to 911 Hmmm. Can you text-message to 911, I wonder? Otherwise, this would imply robowaifus successfully engaging in train-of-thought,-consistent-coherent-context NLP verbal conversations with operators, many of whom are low-IQ ebonics speakers. At least that's how it is here in Burgerland, don't know about other more-civilized countries. This is a tough row to hoe at this point in time, GreerTech. Ideas?

>>37543 >Can you text-message to 911, I wonder? Officially, yes, but not every dispatcher supports it. I believe the FCC has a tool for looking up which locations have it.

>>37544 Neat! That would force the operators to ask their questions in the form of text, which would greatly ease the burden on the robowaifu herself. If this can be devised properly, then that alone would be a yuge selling point to the elderly I deem. Thanks, GreerTech! Cheers.

>>37543 I was thinking maybe a repeating automated message.

>>37547 That seems reasonable, if it would work. Any indication from your listing mentioned above that says if repeating, automated message texts are acceptable? Now that I think about this problem a little more, surely with the yuge number of boomers entering senescence across the west, this is a big need to fill (ie, automated messaging for emergency help). BTW, in the home alarm world, you create a contract with a monitoring service company, which then forwards the alert (from your automated alarm system installation) verbally to the police as an authorized representative for you. I wonder if emergency health services requests might be similar?

++migratrion start++ General Ideas -If your robowaifu's AI is on a computer or phone, put a strong password on the device (no "password") -Don't use Ollama

[boardlink - edit later] >Fully repairable Linux computers are the only systems one can rely on for 10+ years of service. This, but things are a bit more dynamic than that, IMO. Onboard, she'll need to be running her 'Brain'(C3) systems on smol devices -- SBCs & MCUs, etc. Anon's home servers could run on most anything, as long as they never, NEVER, NEVER need to go online (after construction). At least that's how I envision things. Obviously, these are going to be very-complex systems of hardware & software (both inboard & outboard our robowaifus). Much prototyping is still yet to be done to tweak all this properly. Cheers, Kiwi. :^)

>>37708 >SBC's & MCUs That's important to note. It's cool to see the shiny new multimodal AI, but if you want to have an inbuilt computer, you're going to need an AI model small enough to fit on a raspberry pi, best case scenario on a Jetson Nano. (Or a smartphone like me and Barf from Alogs)

>>37709 Good point! But thanks to the Based Bulgarian & his 3K+ contributions yearly, we now have systems that run offline on Raspberry PIs! :^) > https://github.com/ggerganov https://ggerganov.com/

++migration end++ >>37709 >>37710 > (hardware -related : [boardlink - edit later] )

>>37733 >Thanks, the song's stuck in my head again. Lol <Always here for you, bro! :DD <---> >Assuming an always-offline system, I don't really think it matters. >The best lightweight OS is the one that plays nice with her hardware, and features full-disk encryption. Hmm...maybe. Current security motifs involve the >"Every node is compromised. Proceed accordingly." mindset (and not without good reason). Since the hardware itself constitutes dozens (if not hundreds) of possible glownigger/troon attack vectors, I think it behooves us all to not presume too much a priori by using blatantly Globohomo-compromised systems (such as: M$, fagOS, R*dhat [et al], Ub*ntu [et al]) ** within our robowaifus. Even anything that uses systemD*cks is off-limits as well, IMO. Does that make sense, Anon? --- ** by 'et al' in this specific-context, I mean anything downstream of these distros as well...so: F*dora, Linux M*nt, &tc.

>>37737 So what's left?

>>37738 Well, there are dozens & dozens of possibilities left, Anon. One good one would be a very-pared-down OpenBSD running a hypervisor, and then the code sitting inside a minimal-by-default platform like #include<OS> (cf. >>203, et al). BTW, don't ever forget why you even need to ask 'what's left'. Of course, this situation & mindset on your part was intentionally-devised just so for today. Also, don't forget (((who))) is behind that set of machinations. >tl;dr The Globohomo is no one's friend (just like their father Satan). Thankfully, there are still viable alternatives to their already-compromised systems commonly available to us (like the above pairing). You just have to pick & choose wisely! :^)

>>37739 >Well, there are dozens & dozens of possibilities left, Anon. That's good, OpenBSD looks based. That combined with no wireless network sounds secure enough. Even a pozzed system could be made secure with that. >BTW, don't ever forget why you even need to ask 'what's left'. Of course, this situation & mindset on your part was intentionally-devised just so for today. Also, don't forget (((who))) is behind that set of machinations. Oh, I do know that and remember it. That's why I wanted to find any semi-obscure alternatives to defy them.

>>37740 Excellent! Sounds like you have your 'head screwed on straight' concerning this general topical domain, GreerTech. Proud of you for that, Anon. :^) <---> >Even a pozzed system could be made secure with that. Trust me, I understand where you're coming from with that -- and you may actually be right!! :D OTOH, logic tells us: >"You can never prove a negative." [1] In other words: we could never exhaust all the realm of possible-possibles, sufficient such that we can exclude something from being a possibility -- by using such an inherently-limited-and-tedious approach. (There are other ways, however; cf. [2]). God can always prove such a thing, if it is factual from his viewpoint. But as humans (still stuck inside this universe), about all we can do is make our best attempts to avoid the many various-and-sundry fallacies out there, make inference to the best explanation, reason by analogy, &tc. <---> I think the >tl;dr here ITT is simply this: >"Always do your best, Oniichan!!!" :DD Like really... Gambatte, Anon -- just do it for her! [3] (And that's a whole lot harder than it sounds -- especially so during Current Year.) In other words: always strive to write the best code, and always run it on the best system platform, and always run that on the best hardware platform, and always implement the best physical security for that system, and always use the best OpSec (et al) for that facility, etc., etc. Don't take 'no' for an answer. Improvise, adapt, overcome. Find a way over the mountain. Or around the mountain. Or THROUGH the mountain! Keep working the problem until you asymptotically approach 'perfection'. And then work it some more!! Need I repeat it, Anon(s)? [3] :^) <---> ALSO, always remember: >Any so-called 'solution' is always provisional!! Things can change 'at the drop of a hat'. Be ready for that with backup plans A, B, C, and D , & E. :^) <"Fixed fortifications are monuments to the stupidity of man." <-t. George S. Patton <"Stay frosty." <-t. Bob the Guardian --- 1. > -related : [2] https://en.wikipedia.org/wiki/Burden_of_proof_(philosophy)#Proving_a_negative 2. https://en.wikipedia.org/wiki/Proof_of_impossibility 3. https://www.youtube.com/watch?v=ZXsQAXx_ao0