Here we share the ideas of how to help the development of robowaifus. You can look for tasks to improve the board, or ones which would help to move the development forward. You could also come up with a task that needs to be worked on and ask for help, use the pattern on top of OP for that, replace the part in <brackets> with your own text and post it. >Pattern to copy and adjust for adding a task to the thread: Task: <Description, general or very specific and target thread for the results> Tips: <Link additional information and add tips of how to achieve it.> Constraints and preferences: <Things to avoid> Results: Post your results in the prototypes thread if you designed something >>18800, or into an on-topic thread from the catalog if you found something or created a summary or diagram. General Disclaimer: Don't discuss your work on tasks in this thread, make a posting in another thread, or several of them, and then another one here linking to it. We do have a thread for prototypes >>18800, current meta >>18173 and many others in the catalog https://alogs.space/robowaifu/catalog.html - the thread for posting the result might also be the best place to discuss things. >General suggestions where you might be able to help: - Go through threads in the catalog here https://alogs.space/robowaifu/catalog.html and make summaries and diagrams like pointed out starting here >>10428 - Work on parts instead of trying to develop and build a whole robowaifu - Work on processes you find in some thread in the catalog https://alogs.space/robowaifu/catalog.html - Test existing mechanisms shared on this board, prototypes >>18800 - Try to work on sensors in some kind of rubber skin and in parts >>95 >>242 >>419 - Keep track of other sites and similar projects, for example on YouTube, Twitter or Hackaday. - Copy useful pieces of information from threads on other sites and boards talking about "sexbots", "chatbots", AI or something similar. Pick the right thread here: https://alogs.space/robowaifu/catalog.html

Why Robowaifu? Men's mental health regarding the sexes has been rapidly-deteriorating today, and men around the world have been looking for a solution. History shows there are cultural and political solutions to this general problem's causes, but we believe that technology is the best way forward at present – specifically the technology of robotics. We are technologists, dreamers, hobbyists, geeks and robots looking forward to a day when any man can build the ideal companion he desires in his own home. However, not content to wait for the future; we are bringing that day forward. We are creating an active hobbyist scene of builders, programmers, musicians, artists, designers, and writers using the technology of today, not tomorrow. Join us! >tl;dr This is a place for men who want to live peacefully with beautiful feminine robowaifus. Simple as. <---> NOTES & FRIENDS > Notes: -This is generally a SFW board, given our engineering focus primarily. On-topic NSFW content is OK, but please spoiler it. -Our bunker is located at: https://trashchan.xyz/robowaifu/catalog.html Please make note of it. -Webring's mustering point: https://junkuchan.org/shelter/index.html -Library thread (good for locating terms/topics) (>>7143)

So far I have plans to build Adam, Eve, and Abel robots. All of these are Bible characters. This thread will cover the Eve robot. Eve will have no "love holes" because adding those would be sinful and evil. It is a robot, not a biological woman after all and I will view her with all purity of heart and mind instead of using her to fulfill my lusts of my body. Instead I will walk by the Spirit no longer fulfilling the lusts of the flesh as the Bible commands. Eve will be beautiful because making her beautiful is not a sinful thing to do. However, I will dress her modestly as God commands of all women everywhere. This would obviously include robot women because otherwise the robot woman would be a stumbling block to men which could cause them to lust after her which would be a sin. To tempt someone to sin is not loving and is evil and so my robot will not do this. To dress her in a miniskirt, for example, would be sinful and evil and all people who engage in sinfullness knowingly are presently on their way to hell. I don't wish this for anyone. My robot will dress in a way that is a good example to all women and is aimed toward not causing anybody to lust as a goal. My robot will have a human bone structure. It will use either a PVC medical skeleton or fiberglass fabricated hollow bones. My robot will look realistic and move realistic. It will be able to talk, walk, run, do chores, play sports, dance, rock climb, and do gymnastics. It will also be able to build more robots just like itself and manufacture other products and inventions. I realized with just a head and arm, a robot can build the rest of its own body so that is my intention. My robot will use BLDC motors for drones, RC, and scooters that are high speed and low-ish torque but I will downgear those motors with a archimedes pulley system that will be custom made from custom fabricated pulleys that will be bearings based. By downgearing with pulleys, instead of gears, I will cut down the noise the robot makes so it will be as silent as possible for indoor use. By downgearing, I convert the high speed motors into moderate speeds with great torque. BLDC motors with large torque generally are too large in diameter for a human form factor and take up too much volumetric area to be useful which is why I go with the high speed smaller diameter type motors but just heavily downgear them 32:1 and 64:1. My robot will have realistic silicone skin. Thom Floutz -LA based painter, sculptor, make-up artist is my inspiration as it pertains to realistic skin. The skin for my robots has to be at his level to be acceptable. It must be nearly impossible to tell the robot is not human to be acceptable. I will have a wireframe mesh exoskeleton that simulates the volumes and movements of muscle underneath the skin which will give the skin its volumetric form like muscles do. Within these hollow wireframe mesh frameworks will be all the electronics and their cooling systems. All of my motor controllers will be custom made since I need them VERY small to fit into the confined spaces I have to work with. I need LOADS of motors to replace every pertinent muscle of the human body in such a way that the robot can move in all the ways humans move and have near human level of strength and speed.

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 ) > #5 ( >>34233 )

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?

/meta, offtopic, & QTDDTOT <--- Mini-FAQ A few hand-picked posts on various /robowaifu/-related topics: --->Lurk less: Tasks to Tackle ( >>20037 ) --->Why is keeping mass (weight) low so important? ( >>4313 ) --->Why shouldn't we use Cloud AI? ( >>38090, >>22630, >>30049, >>30051 ) --->How to get started with AI/ML for beginners ( >>18306 ) --->"The Big 4" things we need to solve here ( >>15182 ) --->HOW TO SOLVE IT ( >>4143 ) --->Why we exist on an imageboard, and not some other forum platform ( >>15638, >>31158 ) --->This is madness! You can't possibly succeed, so why even bother? ( >>20208, >>23969 ) --->All AI programming is done in Python. So why are you using C & C++ here? ( >>21057, >>21091, >>27167, >>29994 ) --->How to learn to program in C++ for robowaifus? ( >>18749, >>19777, >>37647 )

Post about whatever media predominately features at least one fembot aka gynoid (female form of an android) as an important character, ideally a robowaifu or synthetic girlfriend. Some freedom with the topic is allowed, virtual waifus or bodiless AI might also qualify if she is female. Negative framing of the whole topic should be mentioned with negative sentiment. Cyborgs with a human brain or uploads of women don't really fit in, but if she's very nice (Alita) and maybe not a human based cyborg (catborg/netoborg) we can let it slide. Magical dolls have also been included in the past, especially when the guy had to hand-made them. Look through the old threads, it's worth it: >>82 >>18711 - Picrel shows some of the more well know shows from a few years ago. I made a long list with links to more info's on most known anime shows about fembots/robowaifus, without hentai but including some ecchi and posted it here in the old thread: >>7008 - It also features some live-action shows and movies. I repost the updated list here, not claiming that it is complete, especially when it comes to live action and shows/movies we don't really like. >In some cases I can only assume that the show includes robogirls, since the show is about various robots, but I haven't seen it yet. A.D. Police Files: https://www.anime-planet.com/anime/ad-police-files Andromeda Stories: https://www.anime-planet.com/anime/andromeda-stories Angelic Layer: https://www.anime-planet.com/anime/angelic-layer Armitage III: https://www.anime-planet.com/anime/armitage-iii Azusa will help: https://www.anime-planet.com/anime/azusa-will-help Blade Runner 2022: https://www.anime-planet.com/anime/blade-runner-black-out-2022 Busou Shinki: https://www.anime-planet.com/anime/busou-shinki-moon-angel Butobi CPU: https://www.anime-planet.com/anime/buttobi-cpu Casshern Sins: https://www.anime-planet.com/anime/casshern-sins Chobits: https://www.anime-planet.com/anime/chobits

The original thread can be found here: https://trashchan.xyz/robowaifu/thread/595.html --- Welcome to the Lemon Cookie thread, The goal of Lemon Cookie is to create a framework where a synthetic "mind and soul" can emerge through a "LLM as cognitive architecture" approach. This thread exists to collect feedback, ask for help & to document my progress. First I am going to try to give a high level overview of how this cognitive architecture is envisioned and the ideas behind it. I have spent time looking at cognitive architecture work, in the field there is now a consensus on how the mind works at a high level. An important mechanism is a "whiteboard", basically a global temporary memory that all the other systems read in and out of. Then there is different long-term memory systems that react to and add content to the whiteboard. Along with memory pattern matcher(s)/rules work on the content of the whiteboard. A key thing to consider is the difference in philosophy that cognitive architecture projects have, the intelligence is considered to emerge from the entire system. Compare this to LLM agent work where it's considered the intelligence is the LLM. My feelings on the general LLM space are conflicted, I am both amazed and really disappointed. LLMs possess an incredible level of flexibility, world knowledge and coherence. But everything outside of the model is stagnant. It's endless API wrappers & redundant frameworks all slight permutations on RAG & basic tool calling. I will believe that LLMs are misused as chatbots, simply put their pattern matching and associative power is constrained by chat format and shallow tooling. In the Lemon Cookie Cognitive Architecture so far here are the important aspects: 1. Memory is difficult. I do not think there is a singular data structure or method that is able to handle it all, several distinct types of memory will be needed. So far I plan for a PathRAG like system and a "Triadic Memory" inspired system for external associations (this is missing in most LLM solutions). 2. LLM as Kernel, The LLM's context window is the Whiteboard and has a REPL like mechanism. It holds structured data and logic in scripting-like format so it's both LLM & Human readable while staying easy to parse & allows for expressive structured data. The LLM's role will be to decompose data and make patterns and associations explicit as executable statements. 3. The language has to be LLM/CogArch-centric. There is a thousand ""agents"" that give LLMs a python interpreter as a tool. The two need to be more tightly coupled. Scripted behavior via pattern matching, The whiteboard is a bag of objects, this allows for programmable pattern matching (think functional programming like Haskell). It's also important to allow the LLM to observe code execution and to be able to modify state and execution flow. Data in languages have scoping rules, so should LLM context. Etc... I will go into more depth about the language in another post. 4. Another important system is the "GSR" Generative Sparse Representation and it will be a first class language & runtime type, This also needs its own post. But in general I am inspired by two things, "Generative FrameNet" paper where an LLM & an embedding model is used to automatically construct new FrameNet frames. The second source is "Numenta's SDRs"/"Sparse distributed memory" this representation has a lot of useful properties for memory (Please watch the videos under the "What the hell is an SDR?" segment in my links list for an easy introduction.) I think SDR unions & SDR noise tolerance will be especially useful. 5. A custom model, For all of the above to work well, a model will need to be fine tuned with special behaviors. I do want input on this. Baking facts & behaviors into LLM weights is costly, creating bloated models that are hard to run or train (why memorize all the capitals?), while letting authors gatekeep truth and impose "safety" detached from context. Blocking role-play "violence" or intimacy isn't protection: it's authors hijacking your AI companion to preach at you. Externalizing behaviors via whiteboard pattern matching shifts control: stabbing you in-game can be funny, but a robot wielding a knife isn't. Maybe you want intimacy privately, but don't want your AI flirting back at your friends. When put together I think this will be able to host a kind of synthetic "soul", In a living being what we call a personality is the accumulated associations, learned behaviors, beliefs and quirks molded by a unique set of experiences. I hope this will be true for this system too.

This first post is to show the 5 big milestones in the development of SPUD, the Specially Programmed UwU Droid. You can see the old thread here: >>26306 The end goal of SPUD is to provide a fairly high-functioning robot platform at a relatively low cost (free code but a few bucks for 3d print files) that can be used for a variety of purposes such as promotional, educational or companionship. All AI used is hosted on local systems: no bowing to corporations any more than necessary, thank you. Various aspects of the code are/will be modular, meaning that adding a new voice command/expression/animation will be easy as making the file, naming it and placing it in the correct folder (no need to mess around with the base code unless you REALLY want to). While I'm researching more about bipedal walking I'll be making a companion for SPUD to ride on, so it might be a while before I return to the thread.

Thoughts on waifus which remain 2D but have their own dedicated hardware. This is more on the artistry side though ai is still involved. An example of an actual waifu product being the Gatebox.
gatebox.ai/sp/

My favorite example is Ritsu, she's a cute ai from assassination classroom who's body is a giant screen on wheels.