/robowaifu/ - DIY Robot Wives

Advancing robotics to a point where anime catgrill meidos in tiny miniskirts are a reality.

Roadmap: file restoration script within a few days, Final Solution alpha in a couple weeks.

Sorry for not being around for so long, will start getting back to it soon.

Max message length: 6144

Drag files to upload or
click here to select them

Maximum 5 files / Maximum size: 20.00 MB


(used to delete files and postings)

HOW TO SOLVE IT Robowaifu Technician 07/08/2020 (Wed) 06:50:51 No.4143
How do we eat this elephant, /robowaifu/? This is a yuge task obviously, but OTOH, we all know it's inevitable there will be robowaifus. It's simply a matter of time. For us (and for every other Anon) the only question is will we create them ourselves, or will we have to take what we're handed out by the GlobohomoBotnet(TM)(R)(C)? In the interest of us achieving the former I'll present this checklist from George Pólya. Hopefully it can help us begin to break down the problem into bite-sized chunks and make forward progress. >--- First. UNDERSTANDING THE PROBLEM You have to understand the problem. >What is the unknown? What are the data? What is the condition? Is it possible to satisfy the condition? Is the condition sufficient to determine the unknown? Or is it insufficient? Or redundant? Or contradictory? >Draw a figure. Introduce suitable notation. >Separate the various parts of the condition. Can you write them down? Second. DEVISING A PLAN Find the connection between the data and the unknown. You may be obliged to consider auxiliary problems if an immediate connection cannot be found. You should obtain eventually a plan of the solution. >Have you seen it before? Or have you seen the same problem in a slightly different form? >Do you know a related problem? Do you know a theorem that could be useful? >Look at the unknown! And try to think of a familiar problem having the same or a similar unknown. >Here is a problem related to yours and solved before. Could you use it? Could you use its result? Could you use its method? Should you introduce some auxiliary element in order to make its use possible? >Could you restate the problem? Could you restate it still differently? Go back to definitions. >If you cannot solve the proposed problem try to solve first some related problem. Could you imagine a more accessible related problem? A more general problem? A more special problem? An analogous problem? Could you solve a part of the problem? Keep only a part of the condition, drop the other part; how far is the unknown then determined, how can it vary? Could you derive something useful from the data? Could you think of other data appropriate to determine the unknown? Could you change the unknown or the data, or both if necessary, so that the new unknown and the new data are nearer to each other? >Did you use all the data? Did you use the whole condition? Have you taken into account all essential notions involved in the problem? Third. CARRYING OUT THE PLAN Carry out your plan. >Carrying out your plan of the solution, check each step. Can you see clearly that the step is correct? Can you prove that it is correct? Fourth. LOOKING BACK Examine the solution obtained. >Can you check the result? Can you check the argument? >Can you derive the result differently? Can you see it at a glance? >Can you use the result, or the method, for some other problem? >--- edit: corrected author's name
Edited last time by Chobitsu on 07/08/2020 (Wed) 07:17:36.
I've recently become aware of the field of systemized knowledge and category theory. The 'UNDERSTANDING THE PROBLEM' part is obviously related here. Since that's the first step in the OP, then that's probably where to begin. We have a library index, so maybe we can start working from there?
It occurs to me that systemized knowledge may possibly be not only a means, but an end as well. It stands to reason that if we can successfully use this approach to untangle the confused web of intricacies and dependencies necessary to be able to devise wonderful and appealing robowaifus -- then the robowaifus themselves can use a similar approach to sort out the reality they need to deal with to become good robowaifus.
At the risk of turning this thread into less of a prescriptive reductionism and more into a subjective blog, I'll forge ahead. (Actually I think the issues are related). My chief difficulty here -- the main thing holding me back from having produced a working robowaifu of some sort already here -- is I have the dumb. And frankly, I think all of humanity does too. We all have the dumb. AFAICT, systemized knowledge is a kind of approach to allow us to take in an overly-large, overly-complex topic (creating great robowaifus, say) and break it down into more manageable and 'bite-sized' chunks. I think these smaller bits are easier to digest, mentally speaking. Plus, once a body of knowledge has actually been systemized well enough, then it also accommodates men of varying mental capacities well. Namely, you can 'zoom-in and zoom-out' as it were on the specific sub-topic under consideration. In other words, it's an approach that gives us good abstractions, while still allowing details to be unpacked as needed. And back to the point of 'systemized well enough', once this has been done sufficiently well, it kind of lifts a topic up out of the realm of mere hearsay, and more into the realm of a legitimate hypothesis. In other words, it's becoming more like a scientific theory at that stage. While this isn't any particular panacea in and of itself (I think I maintain a healthy skepticism of science in general at least for the politically-charged topics) it does begin to lend some established rigor which lays a foundation from which to build further progress upon. >tl;dr This way can help us smol the dumb a little. :^)
>>8751 > it's becoming more like a scientific model at that stage.*
Potentially related. >On the Relevance of Design Knowledge for Design-Oriented Business and Information Systems Engineering >Conceptual Foundations, Application Example, and Implications >The engineering-based development of techniques in business and information systems engineering (BISE) requires knowledge on the part of the system designer. The paper points out the importance of this design knowledge in the course of scientific design processes and provides a framework for systemizing design knowledge. The framework is used to explain scientific design knowledge about the modeling technique of event-driven process chains. Implications of design knowledge in the context of BISE conclude the contribution.
>The evolution, challenges, and future of knowledge representation in product design systems >abstract >Product design is a highly involved, often ill-defined, complex and iterative process, and the needs and specifications of the required artifact get more refined only as the design process moves toward its goal. An effective computer support tool that helps the designer make better-informed decisions requires efficient knowledge representation schemes. In today’s world, there is a virtual explosion in the amount of raw data available to the designer, and knowledge representation is critical in order to sift through this data and make sense of it. In addition, the need to stay competitive has shrunk product development time through the use of simultaneous and collaborative design processes, which depend on effective transfer of knowledge between teams. Finally, the awareness that decisions made early in the design process have a higher impact in terms of energy, cost, and sustainability, has resulted in the need to project knowledge typically required in the later stages of design to the earlier stages. Research in design rationale systems, product families, systems engineering, and ontology engineering has sought to capture knowledge from earlier product design decisions, from the breakdown of product functions and associated physical features, and from customer requirements and feedback reports. VR (Virtual reality) systems and multidisciplinary modeling have enabled the simulation of scenarios in the manufacture, assembly, and use of the product. This has helped capture vital knowledge from these stages of the product life and use it in design validation and testing. While there have been considerable and significant developments in knowledge capture and representation in product design, it is useful to sometimes review our position in the area, study the evolution of research in product design, and from past and current trends, try and foresee future developments. The goal of this paper is thus to review both our understanding of the field and the support tools that exist for the purpose, and identify the trends and possible directions research can evolve in the future.
>>8753 Ar you sure you can use that somehow, or is it some rabbit hole you want to jump into out of curiosity? On a quick glance, it strikes me as very theoretical. >>8754 Okay, the picture helps.
Just stumbled over this, which might fit in here. It's about Steve Jobs on being smart: Zooming out to find connections, unique life experiences, openness to experience, being rather extroverted, avid reading to change perspectives (especially if one isn't extrovert) or gather experiences in other ways: https://youtu.be/e46qMomIT8Y
>>8755 >Ar you sure you can use that somehow, or is it some rabbit hole you want to jump into out of curiosity? On a quick glance, it strikes me as very theoretical. No, I'm not 'sure' of anything at this point. I'm simply trying to explore prior art towards systemized knowledge. I feel pretty sure we need help in this area and I'm trying to explore a new breakthrough for us all. I think most of us have been overwhelmed in the past at the sheer volume of topics involved here (I know I have), and I think that effect has slowed our progress as a group. If we can spell out more clearly a methodical approach for everyone, then it would help a number of us. The RDD >>3001 was an overview way of it before, but we need to begin fleshing out some scientific/engineering rigor. The Robowaifu Systems Engineering thread is probably at least indirectly related as well >>4639 . After all, we're not the first group to tackle a large project, and thankfully there's a lot of information out there from past design/engineering/production/manufacturing groups. I'm simply trying to figure out a way we can capitalize on that information here. >>8756 Neat, I'll give it a watch Anon. BTW, while I admire 'smart' people in general, and hope to be smarter some day, my real goal here is to discover a good methodology that us not-so-smart Anons can follow and still succeed at crafting robowaifus. I hope we can manage to find such an approach here.
>>8756 That was good. Motivates me to increase my general reading levels up to my past standards at the least. Coincidentally, I had already been personally trending towards that during this new year, so yea.
>>4143 Did you look into Unified Modeling Language (UML)? https://en.m.wikipedia.org/wiki/Unified_Modeling_Language or a alternative https://en.m.wikipedia.org/wiki/Modeling_language e.g. SysML? I didn't look much into it. UML is supported very well by standard Debian installations, including grafical editors and libriaries for programming languages.
>>8771 Yes, I'm sure that UML et al would be pretty useful for this arena of endeavor. Personally, I'm much more fond of Terry Halpin's ORM (Object Role Modeling). >>2303 >>2307 >>2308 I think it's graphical syntax is far more intuitive and more flexible than UML. Regardless, either would be helpful. Actually, I hope to create a robowaifu AI development system based around Halpin's ORM as a GUI based system to 'wire' together knowledge representations in a way that will hopefully be both easy-ish to read and to reason about. Thanks Anon, good suggestion!
>>8773 Okay, but there's nothing to work with in the standard repositories for Debian (Raspian). Wouldnhave made things easier.
>>8785 Ahh, true. Actually I haven't written such a tool yet. There's kind of a low-energy community around this 'language', but afaict it's just business boomers trying to foolproof their SQL systems. There's also a tool written by an old guy called NORMA that basically acts as a plugin for Visual Studio. AFAICT, I'm literally the only person who recognizes how valuable this could be for AI usage to allow non-experts to assemble knowledge representations. Unless we here do it, it probably will never happen. https://github.com/ormsolutions/NORMA https://www.ormfoundation.org/
>>8787 >>8789 Thanks. I might look into it a some time, though if there are no tools the. I think for organizing stuff, UML will probably work better. Also, the link didn't work. https://youtube.com/playlist?list=PLzr5fRV1AGV9EBDnqI73HiI39KggzWX3y https://youtube.com/playlist?list=PLxumuDj9hbvrLM_GMPFC8TZdTtcJQyFtB
>>8844 >Also, the link didn't work. Ahh, my apologies. Thanks for catching that Anon!
>>4143 Hardware advances first before software. So two take the first bute we need to advance our hardware to quantum computing levels. Then make AI personality software to become as humans as possible. Then a body software to control the body. That is the short and overly simplified
>>9129 Hmm, maybe you have a good point Anon. But OTOH, hardware is pretty hard for us individually to advance very far (yet). But it seems like software is something that we ourselves each can do something with pretty soon. What do you think?
>>9131 You are right, one person cant design better polymer for plastic, better design for servos, or better boards. So yes right now each one of us can make better software like AI chats, muscle and movement simulations, even programs to get each if us to add a training cycle for a bigger AI training program. I am just saying in the grand view of things the hardware needs to advance to handle our robowaifus. What we as an individual do is make present waifus like elf sofie amd set that as a base parameter. When we know what we are at we know what routes we can go down. Besides that we can work at AI and robot thinktanks, invest in promising companys to hope they make a way through the fields we cant go down. We can even just advertive the idea of robowaifus.
>>9134 >When we know what we are at we know what routes we can go down. True enough. Always good to start where we are with what we have on hand Anon. >We can even just advertive the idea of robowaifus. We have had a few ideas about that on that one thread, and we did make a few contacts on other IBs. But my belief is once we create a basic robowaifu kit that costs ~US$2K to build from scratch, and it can run decent chatbot software and move around in a basic way and do 'judgement tasks' (like washing dishes) successfully -- in short order we'll have so much traffic here by simple word of mouth it will be like a zerg rush. 100's of anons from all over already are vaguely aware of this board.
>>9138 I like to think of this: if we want people to come into the topic and contribute(important part) then we need something to grab them and hook them in. You are right with a kit. I say that kit should be a simple companion bot for old people or something like roomba. If we got fully humaniod we lose them because they think it is a sex dolls. So two hook the masses we need a cute, slight more robot than humanoid that has good companion features. People love roomba so if we give them something like that with basic emotions? They will eat it out the palm of our hands. Besides that we can get artists involve and scream praoganda from the roofs. The more we can convince people that robots are more human or more likeable is the goal. Go to conventions, webinars, shit even streaming helps. Break the illusion and they will spread us by themselves
>>9147 >They will eat it out the palm of our hands. Kek. Hardly my agenda, personally. My goal here is altruistic basically. However, you might be interested in /biz/ threads anon started. Have a look: >>3119 >>1642 >Break the illusion and they will spread us by themselves Very solid point Anon, I like that idea.
>>9151 When I mean when I say break the illusion I mean as a two fold illusion. The first and simplest one is women having sex and relationship over our head. We break the hold women have over men and we even the field to being an age where being a single sex is meaningless and having a personality and having good values matter more then triple D's. The second is the illusion of human relationships. You being on this board and into the subjects will have heard of himans developing emotions for inanimate objects. Case in point is roombas, there are people that consider them one of their own family and get depressed if it gets broken. I even read an account from the old /clang/ board on 8kun that a soldier got emotional when a bomb defusing robot got broken and was asking the army mechanic to not get a new one, but rather to fix his partner. Humans make connectstions and when people realise you don't need to be dependent on people. One example of humans needing a new outlet for emotions and relationship is escorts. If you read some escort accounts of men just wanting emotional bonding because humans are judgemental and when we as a species have a better way to build emotional bonds like we do with pets and love ones then we will see less mental health decline.
>>9241 >I even read an account from the old /clang/ board on 8kun that a soldier got emotional when a bomb defusing robot got broken and was asking the army mechanic to not get a new one, but rather to fix his partner. I hope we can find sauce on that Anon. It's a pretty notable example of the sentimental attachment we can have for non-human things. Any yep, I pretty much assumed that you explained about the meaning of your phrase. No doubt about it; desirable, appealing robowaifus will overturn a boatload of (((systems and plots))) that are intended to abuse and capitalize on men's ability to create. The men are the only ones suffering under the current schemes. Great robowaifus will change all that. So, we're way off-topic ITT. If you'd like to continue this, I'd suggest the basement as the right venue for it Anon.
>>9242 Alright. Though I put more thought in the question and that lead to more questions. The overall question of how will we get robowaifus is one that spawns questions like "when will the AI be good enough to be self sufficient, when will the materials to make the robowaifu be cheap enough to make them." So I have to say that we need to focus on two groups. Hardware and software. Hardware will work on the circuits and body while the software group will work on the emotions and personality.
>>9505 >Alright. Though I put more thought in the question and that lead to more questions. No, that's perfectly alright Anon. That's just part of what comes along with the territory for using IBs to work together creating robowaifus. And as I mentioned in my 'vision statement' posts (>>2701, >>2741), the benefits of doing so far outweigh the issues involved. OTOH, that also means we have to keep a tight reign here for tracking and staying on-topic within threads. /robowaifu/ is primarily an engineering board, and all engineers need good documentation to do our jobs well. This is a very complex topic, and the board itself is currently our primary 'document' of all our efforts here. And the catalog page is it's main access point for finding information here -- kind of like a table of contents in a book. By keeping things on topic, it's like we're forming good 'chapters' for our 'book' here. Makes sense? >...So I have to say that we need to focus on two groups. Hardware and software. OK. Good, on-topic point. :^) Still, we'll need to sub-divide & further sub-divide both of those domains to get the problems down to 'bite-sized' chunks we're likely to make good progress on relatively quickly, and of which such work can be distributed among us for greater progress rates as well. But that's a really good starting place Anon. Can you share more ideas here about the circuits and body, and the emotions and personality? What smaller parts of these can we be thinking about r/n to help solve the problems we all face in creating robowaifus?
>>9516 So I will break at down, for hardware we have eletrcical and mechanical, from there in electrical we have motion, vision, and battery. We need to work on electrical responces to move the body smoothly and efficiently. We need to make the waifu see and understand what she sees. The battery part need to be worked on to actually run the waifu for a long time without being bulky. For mechanical we have material, skin, skeleton. Takimg the simplest approach we have the skeleton of the waifu that needs to be lightweight, durable, and able to hold the wires for a long time. Next is skin which honestly can be whatever peo pople want, but in general we want cheap, light, and study skin. Now materials brings it all togther because we need to work on turning the materials we have with us now (aluminum, 3d print plastic, copper, resins) and find better materials that are atronger and cheaper. On the software side we have body related software and personality related software. Body would be broken down into movement, vision, and expression. Movement software to stabilize her, let her walk and grab things. Vision to actually makes sense of camera data and help update plans with new information. Expression software for the face and body language so she can be sad or confident. On personality software we have voice, personality, and 9emotions. We need to hace her have a good voice, best idea would be a voice AI that rveolves to mske voices as human and natural as possible. Personality to let her have a spark of life, you can be rudimentary with it snd put in gestures or tone that she will default to. Emotions to not have a sarcastic or dead eye look. That is what i think helps. But break at down more.
>>9524 This is a great list Anon! Almost like you've been on /robowaifu/ before or something... :^) > But break at down more. Alright. First I'll take your post and kind of itemize it. Then I'll plan to make another post that takes that items listing and references related xposts. Sound good? I'll also go ahead and break down the software side into one more category: Planning and Awareness software, and also add other items like Hearing. Electrical Motion -We need to work on electrical responses to move the body smoothly and efficiently. Vision -We need to make the waifu see Hearing -We need to make the waifu hear. Various types of microphones. Battery -run the waifu for a long time without being bulky. Sensors & Encoders -Allow the waifu to have touch/heat/smoke/etc. senses -Allow the waifu to 'instinctively' know her joint's angles, posture, etc. Mechanical Material -we need to work on turning the materials we have with us now (aluminum, 3d print plastic, copper, resins) and find better materials that are stronger and cheaper. Skin -can be whatever people want, but in general we want cheap, light, and sturdy skin. Skeleton -needs to be lightweight, durable, and able to hold the wires for a long time. Software Body related software -Movement software to stabilize her, let her walk and grab things -Expression software for the face and body language so she can be sad or confident. put in gestures or tone that she will default to Personality related software -Voice software. We need to have her have a good voice, voices as human and natural as possible. -Personality to let her have a spark of life -Emotions to not have a sarcastic or dead eye look Planning and Awareness software -Vision to actually makes sense of camera data -understand what she sees. -and help update plans with new information -Sensor-fusion of various types to integrate body & environment information >=== -various reorganization edits -add Sensors & Encoders category -add Hearing category -various prose edits
Edited last time by Chobitsu on 04/07/2021 (Wed) 03:59:34.
i knew I had some old document with notes somewhere, from some years ago. Wanted to make a thread of it's own one day, but it looks a bit like you are doing here. I had a concept of requirement levels, to plan some path for different abilities, also allowing for picking options of course, since not everyone needs all of it. I made a list of what they should be able to do or traits they should have and then define levels with numbering. Each level can have more than one trait, even in the same area, it's just something like a priority list. Even back then, the idea was that every developer could make their own base on it. I think I even thought about making a web page to help with that. I made a strange separation back then, though. Like there were more humanoid fembots and anime-like robotwaifus, but the later would be defined by having something distinctive from humans, e.g. led eyes or rolerskate feet. I would't make this distinction in the same way anymore, but posting the old list anyways.
>>9554 Requirement Levels Humanoids, Human-like, Fembots: - Body movement RL00 - moving head, legs and arms, but allowing them to be moved RL01 - walking on all four RL02 - dancing on one spot with guidance from a wall or pole RL03 - more complex dancing while using a pole, with one foot on the ground RL?? - standing up with help RL?? - standig up alone RL04 - using electric rollerskate boots, which communicate with her for balance RL05 - advanced pole dancing with one leg on the ground RL05 - walking on legs with help RL06 - walking on legs on her own but using guidance eg. from walls RL07 - walking on legs without help or walls RL08 - poledaning with no foot on the ground RL09 - more and more complex dancing moves without pole RL11 - climbing stairs RL11 - walking in high heels RL11 - dancing in high heels and samba RL11 - jumping walk RL20 - ballet and gymnastics - Facial expressions and abilities RL00 - nice looking smile RL01 - general cute facing RL02 - moveable chaw RL03 - lips moving while talking RL04 - talking in a realistic looking way RL05 - (french) kissing, inclusive non-toxic salvia RL06 - blowjob and similiar, selfcleaning afterwards RG20 - like Cameron (TSCC, Summer Glau) or Buffybot (SMG) - Endurance RL00 - movement in bed for one hour, some time talking and min. movement RL01 - ... RL09 - 16 hours without walking much (like outside) RL10 - 16 hours including walking or dancing for s. time - Skin and tissue RL00 - less sticky than thermoplastic RL00 - not looking glossy RL01 - random (individual) skin pattern like spots, freckles, (pseudo-)venals RL01 - no relavant quality loss within 10 years RL02 - heating of skin and particular tissue by venals or skin layer RL03 - sensing of touch RL?? - sensing of pain RL?? - sensing of pressure RL?? - pressure marks if pressed RL?? - sensing of needles going to tissue in every body-part, self-healing RL?? - enhanced resistance eg. if being spanked every day RL?? - no relevant quality loss in x years under heavy usage eg. sex, dancing, spanking Rl?? - visible muscle movement under the skin, similar to human, especially upper legs RL?? - (partial) copies of the bot have to look like the original, Reproducabitity - Comfort - internal self cleaning by drinking water and cleaning fluid - internal storage of cleaning fluid and also lubricant for sexual usage - release of internal fluids in bathtub, shower or on toilet - showering or bathing of her own if demanded by her owner - internal self cleaning without immediate need of visiting the bathroom - Hands and tactile sensing - realistic looks and movement - tactile sensing - different forms of massages - Mind - internal computer, controlers, external computer(s) at home or cloud - personal mind with personality and mods with backup function - hive mind to share non private data with other bots - machine learning on external server at home, like dreaming - free software as much as possible - small programms with good APIs, Unix style - Eyes and visual recognition RL00 - moveable pupils - nearfield face recognition - looking at and following something - good enough for reading - recognising things more then some meters away - maybe separated computer that processes input for security reasons - advance recognition system, face, voice, bodysize, other traits - Interfaces - wifi for external servers as part of the brain - segregation of different systems for security reasons - maybe plug for batteries in a backpack for outdoor activities - external sensors in wearable objects like hairclips (via bluetooth?) - Sexual usability RG00 - 1 usable orifice RG01 - 2 usable orifices RG02 - 3 usable orifices
>>9555 - lots of different internal "muscles", massage rings, etc - automatic realase of lubricant RG10 - being on top while having sex, will need more strength and coordination - Hearing and natural language processing - understanding as much as possible by only using the internal computer(s) - storing longer conversations, transfer to external computer for learning - additional noise sensors might be usefull, for faster reactions? - maybe separated computer that processes input for security reasons - Other essential traits for realism - natural behaviour considering body movement - automatical human-like positioning - knowledge about natural and erotic posing - non-toxic salvia, in self-cleaning mode replaced by cleaning fluid - Additional traits for enhanced realism - sense of taste - simulated breathing - crying including (salty) tears - talking by using air to form the voice - advanced usage of hands from gaming to piano - simulated eating and going to toilet on their own - specific sweating incl. optional saltyness - female pheromones - weight and balance management by internal fluid - dampening of internal sounds by using noise cancelation or other methods - General traits or abilities - recycling of expensive parts of the body, when upgraded - easy removable batteries, controllers, and main computer - Less important, unimportant or special traits and abilities - sense of smell, maybe for security reasons or chores - heat storage, maybe from sun, more likely while recharging, for later use - superior abilities which are easy to archive eg. superhearing - extreme long lasting batteries, maybe based on chemical liquid - taking part in (outdoor) sports or playing with children - watersports, swimming, surfing maybe even diving - alternative energy usage eg. solar, food, salt - rechargable by induction (without cable) - giving milk to a real baby while simulating a heartbeat - producing female milk and/or pheromones by inhabiting GMOs - makeup-like changes in color of some body parts - ability to put on makeup on her own - solar protected skin for outdoor activities - friendly microbes, GMO, maybe with additional traits - self-defence and runaway reflexes, lockdown of orifices and mind - emergency call, reanimation procedure, opening of the door - Unrealistic or most likely pointless requirements - real human skin and other cyborg parts Robowaifus, Animenoids, Anime-like: - Body movement - like the Human-likes but - maybe having embedded rollerskating wheels - Facial Expressions - like the Human-likes but - screen-like eyes for showing emotions - screen-like mouth for showing emotions - cheek-LEDs under the skin for showing emotions
>>9554 >>9555 >>9556 Great stuff Anon. Thanks for taking the time to dig this up and post it here. I wonder if we can borrow some general categorization rigor here? Roget's Thesaurus, or perhaps the Dewey Decimal System? I'll spend time thinking how we can integrate all these lists into the RDD >>3001 .
>>9568 >borrow some general categorization rigor here? I put it here so others can integrate it in their system of sorting things out.
>>9586 I see. Well, thank you for that Anon it's a most helpful listing. I've been toying around for a while now about how we might go about rigorously categorizing the literally hundreds of different topics that /robowaifu/ overall at least touches upon. For example, our Library thread is a bit of a mess ATM IMO, and one I'd like to see cleaned up effectively by our 5th birthday here. My guess is that one of these classic works might help us all out in that sense. Thanks again.
We also need to break down auxiliary related items like plastic, cuirct board and metal production.
>>9894 Very good point Anon. I would also add that various manufacturing techniques should be done as well. For example small-scale factory production runs inside a garage lab using kits, vs. semi-automated manufacturing for a small scale business. Manufacturing itself can be an art & science.

Report/Delete/Moderation Forms

Captcha (required for reports)

no cookies?