A thread to discuss topics such as, potential products, marketing, consumer demand, customer bases, robowaifus on the market, etc...

9th Birthday Edition greeting here: ( >>43098 ) --- >original (albeit a bit edited) OP follows: Well it's Thanksgiving time again and that means it's /robowaifu/s birthday time too. It's been 3 full years since we began, and this last one has been a bit of a ride tbh. With the deplatforming of 8ch all of us who had communities there were mostly left out in the cold. Thankfully we've been given a new home here in our bunkerhome at JulaynuJulay, and a few of us have found our way back together here. Hopefully the rest of us will find Julay, and /robowaifu/ again as well. We've also made some new friends since we've been here, and I think we're in pretty good shape all things considered. On the topic of deplatforming, we have a new archival system in action that keeps a copy of the board up to date on my machine. Note that my original intent was to fully automate the archive.today archives, but it hasn't worked properly (they seem to be fighting against bots pretty hard now). I hope at least one other of you will also join in for the approach that's actually working, and use BUMP to keep at least one other copy of /robowaifu/ safe in addition to my own. You never know what might happen to my gear (or even to me), and it's just smart thinking to have at least two of us keeping this board safe. My intent is to finish up the system for board migrations (along with Robi), and then bring over other things from the old files and get this board in shape again. Then we can keep it fully backed up together. As you regulars know, /robowaifu/ is basically unique among imageboards and well-deserves preservation IMO. Any other takers for doing backups as well? I just use a cronjob and it's all fully automatic daily I never have to touch it. I'll explain everything in detail how to do it if anyone else wants to participate. One other thing; should anything ever happen to Julay, just regroup on Fatchan Anoncafe Trashchan in our bunker there. Actually, I'm pretty upbeat about both the world of IB communities in general, and our own /robowaifu/ in particular. We all took a hard knock a few months ago, but we're back on our feet and in the fight again. Kudos in particular to both Julay and Smug for their innovations with the webring introduction. It's lent a resilience to the underlying systems for all our various communities that we've never had before afaict. This alone should help to ensure we have a long future of shitposting together anons. Anyway moving on, I hope this coming year will also see a resurgence in everyone's posts here about their personal projects. I intend to do so myself. It's always a pleasure to see Anon's efforts and blog-posts about their current attempts and ideas, regardless whether they are successes or failures. Persistence is really the single most important factor for eventual success--even more than innate talent--and so just don't quit anon! Don't be afraid to get back in the game even if you met with failure before. Try something different this time, right?

Power & Energy Robots require some form of energy to power them. We need to understand how to store energy in a way that will provide her with all the power she’ll need. To clarify, “energy” is a system's capacity to do work over time. This is measured by Wh, or Watt hour. Closely related is “power” the rate at which work is done. This is measured as W, or watts. As an example, we could have a robot with a 80Wh Lithium Ion battery and two DC gear motors that consume 10W when working. You do not need to rely solely on batteries and motors. We can use other methods of storing energy. This can include compressed fluids, thermal energy, and light, among other things. For instance, glow in the dark paint is useful for storing energy to use at night for safety. Solar panels or a generator can provide power through the energy of long distance nuclear fusion or extracting energy from some reaction. Being part of a robot means we need to consider safety, mass, and volume. How will her energy and power system fit inside her? How will she deal with the mass? What happens when she runs out of energy? How can you minimize her energy use? What alternatives can be used to lower her cost of production and ownership? These rhetorical questions are all important when contemplating how to build a robot.

I think we need to figure out how to fit a womb onto a waifubot. Where's the fun in having sex if you can't procreate?

Repost from a thread on /b/;
>"If you're like me and want to fuck a qt battlebot and get her pregnant, the best place to put an artificial womb is where a normal womb would be on a normal girl. The metal exterior could simply be a bunch of metal plates that unfold to allow space for the womb pod inside. The baby is probably safest inside the battlebot, and if she has good calibration then there shouldn't be problems with her falling and hurting the baby. After giving birth the metal plates could automatically fold back up again, shrinking the womb pod inside so she is combat effective again."

Well /robowaifu/? Feasible?

This thread is for the sharing of robo waifu banners. As per the rules, fallow these requirements: >banner requirements: File size must be lower than 500 KB and dimensions are 300x100 exactly. Allowed file formats are .jpg, .png, and .gif. >=== -fmt cleanup

Chii Cogito Ergo Chii Chii thinks, therefore Chii is. Cognitive architecture is the study of the building blocks which lead to cognition. The structures from which thought emerges. Let's start with the three main aspects of mind; Sentience: Ability to experience sensations and feelings. Her sensors communicate states to her. She senses your hand holding hers and can react. Feelings, having emotions. Her hand being held bring her happiness. This builds on her capacity for subjective experience, related to qualia. Self-awareness: Capacity to differentiate the self from external actors and objects. When presented with a mirror, echo, or other self referential sensory input is recognized as the self. She sees herself in your eyes reflection and recognizes that is her, that she is being held by you. Sapience: Perception of knowledge. Linking concepts and meanings. Able to discern correlations congruent with having wisdom. She sees you collapse into your chair. She infers your state of exhaustion and brings you something to drink. These building blocks integrate and allow her to be. She doesn't just feel, she has qualia. She doesn't see her reflection, she sees herself reflected, she acknowledges her own existence. She doesn't just find relevant data, she works with concepts and integrates her feelings and personality when forming a response. Cognition, subjective thought reliant on a conscious separation of the self and external reality that integrates knowledge of the latter. A state beyond current AI, a true intellect. This thread is dedicated to all the steps on the long journey towards a waifu that truly thinks and feels.

This thread is for discussion, warnings, tips & tricks all related to robowaifu privacy, safety & security. Or even just general computing safety, particularly if it's related to home networks/servers/other systems that our robowaifus will be interacting with in the home. <---> /robowaifu/ 's standard regarding a robowaifu's physical safety : ( >>38561 ). --- > thread-related (>>1671) >=== -update OP -broaden thread subject -add crosslink -add safety-standard crosslink

C++ Resources general The C++ programming language is currently the primary AI-engine language in use. >browsable copy of the latest C++ standard draft: https://eel.is/c++draft/ >where to learn C++: ( >>35657 ) isocpp.org/get-started https://archive.is/hp4JR stackoverflow.com/questions/388242/the-definitive-c-book-guide-and-list https://archive.is/OHw9L en.cppreference.com/w/

I realize it's a bit grandiose (though probably no more than the whole idea of creating a irl robowaifu in the first place) but I want to begin thinking about how to create a working robowaifu 'brain', and how to create a special operating system to run on her so she will have the best chance of remaining an open, safe & secure platform. OS Language Choice C is by far the single largest source of security holes in software history, so it's out more or less automatically by default. I'm sure that causes many C developers to sneer at the very thought of a non-C-based operating system, but the unavoidable cost of fixing the large numbers of bugs and security holes that are inevitable for a large C project is simply more than can be borne by a small team. There is much else to do besides writing code here, and C hooks can be generated wherever deemed necessary as well. C++ is the best candidate for me personally, since it's the language I know best (I also know C too). It's also basically as low level as C but with far better abstractions and much better type-checking. And just like C, you can inline Assembler code wherever needed in C++. Although poorly-written C++ can be as bad as C code in terms of safety due to the necessity of it being compatible with C, it also has many facilities to not go there for the sane coder who adheres to simple, tried-and-true guidelines. There is also a good C++ project already ongoing that could be used for a clustered unikernel OS approach for speed and safety. This approach could save drastic amounts of time for many reasons, not the least of which is tightly constrained debugging. Every 'process' is literally it's own single-threaded kernel, and mountains of old-style cruft (and thinking) typical with OS development simply vanishes. FORTRAN is a very well-established language for the sciences, but a) there aren't a lot of FORTRAN coders, and b) it's probably not the greatest at being a general-purpose language anyway. I'm sure it could be made to run robotics hardware, but would probably be a challenge to turn into an OS. There are plenty of dujour SJW & coffee languages out there, but quite apart from the rampant faggotry & SJWtardism plainly evident in most of their communities, none of them have the kind of industrial experience and pure backbone that C, C++, or FORTRAN have. D and Ada are special cases and possibly bear due consideration in some year's time, but for now C++ is the obvious choice to me for a Robowaifu OS foundation, Python probably being the best scripting language for it. (1 of 2) >=== -fmt cleanup

Anything related to robowaifus, robotics, the AI industry, and any social/economic issues thereof. and /pol/ funposting containment bread! :D -previous threads: > #1 ( >>404 ) > #2 ( >>16732 ) > #3 ( >>21140 ) > #4 ( >>24081 ) >=== -funposting edit