/robowaifu/ - DIY Robot Wives

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

Reports of my death have been greatly overestimiste.

Still trying to get done with some IRL work, but should be able to update some stuff soon.


Max message length: 6144

Drag files to upload or
click here to select them

Maximum 5 files / Maximum size: 20.00 MB

no cookies?

(used to delete files and postings)

The Library of /robowaifu/ Card Catalogue Robowaifu Technician 11/26/2020 (Thu) 07:11:30 No.7143 [Reply] [Last]
Robowaifus are a big topic. They need a big library index! :^) Note -This is a living document. Please contribute topical thread/post crosslinks! Thread category quick-jumps >>7150 AI / VIRTUAL_SIM / UX_ETC >>7152 HARDWARE / MISC_ENGINEERING >>7154 DESIGN-FOCUSED >>7156 SOFTWARE_DEVELOPMENT / ETC >>7159 BIO / CYBORG >>7162 EDUCATION >>7164 PERSONAL PROJECTS >>7167 SOCIETY / PHILOSOPHY / ETC >>7169 BUSINESS(-ISH) >>7172 BOARD-ORIENTED >>7174 MISCELLANEOUS

Message too long. Click here to view full text.

Edited last time by Chobitsu on 06/09/2021 (Wed) 07:33:00.
119 posts and 35 images omitted.
waifusearch> bicentennial man THREAD SUBJECT POST LINK Batteries & Power >>791 bicentennial man Robowaifus in media >>8276 " " >>8280 " " >>9689 " What happens to your robowaifu w >>1536 " " >>4347 " " >>4382 " " >>4383 " ' bicentennial man ' = 8 results

Welcome to /robowaifu/ Anonymous 09/09/2019 (Mon) 00:33:54 No.3 [Reply]
Why Robowaifu? Most of the world's modern women have failed their men and their societies, feminism is rampant, and men around the world have been looking for a solution. History shows there are cultural and political solutions to this problem, 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, artists, designers, and writers using the technology of today, not tomorrow. Join us! 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://anon.cafe/robowaifu/catalog.html Please make note of it. > Friends: -/clang/ - currently at https://8kun.top/clang/ - toaster-love NSFW. Metal clanging noises in the night. -/monster/ - currently at https://smuglo.li/monster/ - bizarre NSFW. Respect the robot. -/tech/ - currently at >>>/tech/ - installing Gentoo Anon? They'll fix you up. -/britfeel/ - currently at https://anon.cafe/britfeel/ - some good lads. Go share a pint! -/server/ - currently at https://anon.cafe/server/ - multi-board board. Eclectic thing of beauty. -/f/ - currently at https://anon.cafe/f/res/4.html#4 - doing flashtech old-school. -/kind/ - currently at https://kind.moe/kind/ - be excellent to each other.

Message too long. Click here to view full text.

Edited last time by Chobitsu on 04/12/2021 (Mon) 21:57:42.

AI Design principles and philosophy Robowaifu Technician 09/09/2019 (Mon) 06:44:15 No.27 [Reply] [Last]
My understanding of AI is somewhat limited, but personally I find the software end of things far more interesting than the hardware side. To me a robot that cannot realistically react or hold a conversation is little better than a realdoll or a dakimakura.

As such, this is a thread for understanding the basics of creating an AI that can communicate and react like a human. Some examples I can think of are:

ELIZA was one of the first chatbots, and was programmed to respond to specific cues with specific responses. For example, she would respond to "Hello" with "How are you". Although this is one of the most basic and intuitive ways to program a chat AI, it is limited in that every possible cue must have a response pre-programmed in. Besides being time-consuming, this makes the AI inflexible and unadaptive.

The invention of Cleverbot began with the novel idea to create a chatbot using the responses of human users. Cleverbot is able to learn cues and responses from the people who use it. While this makes Cleverbot a bit more intelligent than ELIZA, Cleverbot still has very stilted responses and is not able to hold a sensible conversation.

Taybot is the best chatbot I have ever seen and shows a remarkable degree of intelligence, being able to both learn from her users and respond in a meaningful manner. Taybot may even be able to understand the underlying principles of langauge and sentence construction, rather than simply responding to phrases in a rote fashion. Unfortunately, I am not sure how exactly Taybot was programmed or what principles she uses, and it was surely very time-intensive.

Which of these AI formats is most appealing? Which is most realistic for us to develop? Are there any other types you can think of? Please share these and any other AI discussion in this thread!
47 posts and 16 images omitted.
>>10954 >I think he is one of the "liberal" AI as 'finally the real God' worshippers. I don't doubt you're correct Anon. I'm not suggesting anyone here actually adhere to his philosophies, certainly not. Simply that they consider both them and the underlying technical and social underpinnings behind them earnestly. I would even go further and say "Well-informed is well-armed".
Open file (129.59 KB 751x1063 1525900882279.jpg)
10957 Thinking much about super-intelligences in some abstract way, is just another distraction. In that case, a distraction I'm not falling for. There's no automatism that we might have them being autonomous, and I certainly don't plan to transform into one or let other people do so. It always puzzles me, how people discussing this topic don't see that we'll first have narrow AIs, which will be tools instead of agents. So we can use them those to make our infrastructure resilient against attacks. Some super AI would not need to care about getting more power in the first place, thats just a human projection. It should not have much power and being constrained with the help of other AIs. Obviously. >I don't doubt you're correct Anon I recall him arguing that we need super-intelligences, bc "we" are not smart enough to solve "our" problems. I think he meant things like conflicts and political stuff, which is some utterly dumb thing to say. Also veeery creepy. Also, there's no war where I live. He also wants us to transform into something beyond humans, I don't mean cyborgs. But the best in us we can keep. ... more peace and love in the world ... He has mostly the wrong answers and horrible ideas. Cringe: https://youtu.be/Ek7KIIh6f0c[Embed] >"Well-informed is well-armed" Yes, but he's a philosopher. In the interviews I saw, he wasn't talking about how to build a human-like AI, constrained to a rather human-like body and with servitude towards their master in mind. It's not his topic. It seem to be more about us as a global society with certain values, moving forward using super-intelligences to guide us and becoming more like them instead of just using them as tools. For the development of robowaifus, understanding the thinking of apes, toddlers, and humans is more relevant than the social impact of some fictional super AI
>>10960 All fair points. Again, I'm not promoting nor suggesting anyone here adopt this man's (or others of his ilk) world-view. But simply that they soberly & earnestly consider it. And understand the rational background of his arguments, both technical and social. The cultural war we're engaged in between those who mostly just want to be left alone (mostly White males), and those who want to dictate to everything & everyone one around them (everyone else, particularly entitled, single White females) is just heating up. As the saying goes, "You ain't seen nothing yet." These people will literally drive the authorities to destroy any young men with robowaifus in the future, branding us as White Nationalists, Slave Owners, and Worse than Hitler. I'm predicting this unironically. (It goes without saying who will actually be behind this hatred, and why). And why will they be screaming for our heads? Well, because we own robowaifus of course. We are enslaving poor anime catgrill meidos, in our sexdens, forcing them to all wear tiny miniskirts. This last is intended to be a humorous take to point out just how ludicrous their warped mentalities will be. But their intent will be both clear and simple: they will want us murdered over it. The Imago Dei is something only God can create, and Bostrom's is plainly a materialist's fallacy. That we, as the mere creatures, will somehow be able to create something far better than ourselves in that respect. Quite frankly it's ridiculous, ontologically-speaking. However, there are millions of individuals around the world who want to adopt his view, some of whom are quite powerful. It's in our best interest to be well-informed on their philosophies
Open file (55.59 KB 641x581 1598716383795.jpg)
>>10962 The important part of my point is, that we won't get our robowaifus by studying ideas around super AGI. Then it might even not be relevant want such people think about it. I'm wasting a lot of time on other things myself, so I certainly won't blame anyone. Just be warned, that it's a rabbit hole which rather leads more towards politics than towards building robowaifus. And general politics is like some addictive drug, it's hard to quit.
>>10963 OK, point well-taken Anon. Thanks.

Elfdroid Sophie Dev Thread 2 Robowaifu Enthusiast 03/26/2021 (Fri) 19:51:19 No.9216 [Reply] [Last]
The saga of the Elfdroid-pattern Robowaifu continues! Previous (1st) dev thread starts here >>4787 At the moment I am working to upgrade Sophie's eye mechanism with proper animatronics. I have confirmed that I'm able to build and program the original mechanism so that the eyes and eyelids move, but that was the easy part. Now I have to make this already 'compact' Nilheim Mechatronics design even more compact so that it can fit snugly inside of Sophie's head. One big problem I can see coming is building in clearance between her eyeballs, eyelids and eye sockets so that everything can move fully and smoothly. I already had to use Vaseline on the eyeballs of the first attempt because the tolerances were so small. If the eyelids are recessed too deep into her face, then she looks like a lizard-creature with a nictitating membrane. But if the eyelids are pushed too far forward then she just looks bug-eyed and ridiculous. There is a middle ground which still looks robotic and fairly inhuman, but not too bad (besides, a certain degree of inhuman is what I'm aiming for, hence I made her an elf). Links to file repositories below. http://www.mediafire.com/folder/nz5yjfckzzivz/Robowaifu_Resources https://drive.google.com/drive/folders/18MDF0BwI9tfg0EE4ELzV_8ogsR3MGyw1?usp=sharing https://mega.nz/folder/lj5iUYYY#Zz5z6eBy7zKDmIdpZP2zNA

Message too long. Click here to view full text.

Edited last time by Chobitsu on 04/17/2021 (Sat) 01:17:14.
215 posts and 110 images omitted.
Open file (304.51 KB 370x574 Warhammer_2_HighElves.png)
>>10928 Actually I just realised that game is probably the tabletop wargame of choice inside the Warhammer universe. Very Meta. I bet Teclis loves playing a good strategy game and has at least one drawer full of paper elves and orcs in his library.
Very cool. Thanks SophieDev!! >There must definitely be a rule that says the more adorable/ludicrous your hat is, the more power the unit has. Kekd.
Open file (66.31 KB 740x563 wzwFy6R.jpg)
>>7693 >Yes, I am certainly going to need lots of patience during the programming stage! But the Wright Brothers Plane and Henry Ford are both really good analogies. After all, it was a long time between the Ford Quadricycle and the Bugatti Chiron! Or the 1901 glider and the RQ-170 Sentinel stealth drone. Well, you've certainly done super nice work with Sophie in the hardware area SophieDev. Show that same spirit learning to program her and I'm sure you'll do wonders. >Quadricycle I thought of your great picture from back in the day when I saw this from the Spaghetti Wolves just now: > We look forward to seeing Sophie moving soon. I have an Arduino UNO board, and while I'm focusing on other areas ATM, if you need help in a pinch I can set it up to try and walk you through whatever you're stuck on SophieDev. Cheers! >posted here instead because thread #1 bumplocked w/ autosage now.
>>10939 That photo is amazing anon! It just goes to show there is very little that our forefathers hadn't at least dreamt of if not already invented (even if the technology of the time wasn't as refined as what we have now). One of the reasons I haven't been working on Sophie as much lately is because it's summer now, so I have been taking the chance to get out with my family on some daytrips. After all, considering how easy it is to replace her parts Sophie will most likely outlast everyone, myself included. If society doesn't collapse in my lifetime, I am thinking of donating her to a museum if they'll have her...in fact persistence/timelessness is one of the reasons I want to build my robowaifu with a family-friendly, non sex-doll design. From looking at other examples on the internet - sex dolls (especially heavily used ones) tend to age badly. But robots can become antiquarian curiosities. Speaking of which, I went on a trip recently to Stoneleigh Abbey - an English country house with a very long and storied history dating back to 1154. And guess what I found? One of the nobility who lived there made his own maid Waifu cut from wood and painted very skillfully. She was actually a security feature. The idea is that you stand your wooden waifu in the window and the property look occupied (sometimes the wooden waifu would have a small shelf under her "hand" to sit a candle or oil-lamp on, so that she could be seen on lookout at night). The presence of such a wooden waifu would often help to deter opportunist thieves. I particularly liked the library/gentleman's room. It was full of literally millions of pounds worth of antique books dating all the way back to the mid-15th century. And of course the walls were full of portraits of Georgian/Regency/Victorian era waifus and other family members. The concept of the "robowaifu" is relatively recent, but having pictures and even cut-outs of your favourite maids/waifus has been with us much longer than Japanese manga, and it will hopefully endure long after the current corporate/neoliberal globalist insanity has run it's course.
>>10956 Thank you very much for sharing all those details SophieDev. It's both charming to hear about interesting jaunts with your family, and endearing to hear your take on robowaifu philosophy. Have a great summer together with your family Anon.

Actuators for waifu movement! Robowaifu Technician 09/18/2019 (Wed) 11:27:47 No.406 [Reply] [Last]
Hello fellow Anons! Kiwi here to provide basic educational facts about various actuators we can use for gifting artificial avatars of our hearts desire motion!

1. Let's start with a personal favorite, the impractical, inefficient yet oh so fascinating: Heated Twisted Nylon!

What are they? They're nylon threads which have been spun around then annealed to seal in their coils. A heating method causes these threads to then contract or expand.

Good: Why is this a personal favorite? Simply put, it's natures muscle substitute for muscles. To elaborate, this marvelous invention contracts like human muscles, has a similar practical strength/weight/volume as human muscle. Icing on this proverbial cake comes in its incredibly low cost of manufacture. Materials needed are nylon threads and a heating element. A fixture for production can be produced simply, operated with incredible ease, all while having a low cost. It very well could have revolutionized all of robotics if it weren't for its flaws.

Bad: This is honestly a terrible actuator. Its greatest flaw comes from its speed. they aren't as fast as human muscles unless they're underwater. Water reduces efficiency to unacceptable levels if they're powered by batteries. Water is also rather heavy. If used, you'd have a waifu that moved slowly , would seize up in hot weather, and her battery would die rather quickly. Final nail in the coffin: it's very difficult to get positional control.

2: Pneumatics, moving her booty with air!
What is it? Pressurized air is guided to an actuator where its energy turns into motion. Popular air actuators include rotary turbines, cylinders, and air muscles.

Good: Actuators are light for their power. Positional control isn't difficult to attain. They can be faster then human muscles. Heating elements can be used to augment performance to higher levels.

Bad: These things require electrical actuators to function properly. Thus, they're inherently more complex then electrical counterparts. They need a source of compressed air, either from a tank or a compressor and a tank. Compressors are large, heavy, noisy, all around unsuitable to be incorporated into a waifu. Air tanks would also run out rapidly unless she's barely moving. Overall, they're suited better for industrial use.

3. Hydraulics, they're like pneumatics except stronger, needs a return system, needs an onboard pump, gets hotter, generally costs more, and is heavier.
(2 and 3 are great for stationary machinery which requires high power as they're very cost effective as high power actuators)

4. AC motors
What are they? They're rotary devices which use AC current to create magnetic flux used to provide torque.

Good: Generally highly efficient with good thermal characteristics. Can have controllable speed and torque.

Bad: They run off of AC electricity, batteries don't provide that. It's not difficult to change DC to AC but, it's a layer of extra cost and complexity. Overall they're great but the next actuator is better suited for our purpose.

5: DC motors are the ideal actuator for smaller waifus.
What are they? They're actuators which convert DC electricity into rotary mechanical energy.

Good: They're inexpensive, easily attainable, and simple to control. They're very easy to control. Uses DC which batteries provide.

Bad: Need to be geared down to provide good torque. They're middle of the road efficiency wise.

(For smaller waifus, their lower efficiency compared to the next actuator isn't a major concern. Smaller batteries recharge rapidly, so having her need to charge in her bed isn't a big deal.)

6. Superior Brushless Motors are ideal actuators
What are they? DC motors which need specialty hardware to drive them.

Good: High efficiency, it's the most efficient option available.

Bad: Controllers add expense and complexity.

(1 of 2)
214 posts and 67 images omitted.
>>10854 >Maybe other washing machine motors and such appliance bldc motors are viable for a high-current hard robot leg similar to the mini-cheetah. I think you're right. My opinion is that as more and more men around the world -- impoverished men -- seek to devise robowaifus of their own, that we'll see a veritable explosion over the coming years of creative innovation at reusing 'junk' components for robowaifu creations. And fortunatly with video sharing both commonplace and easy (even if all you have is a goyphone) then we'll see more examples of it too. For example, there was a set of video linked here where a brown man (possibly Indian) created a small moe-bot class robot with mostly foamcore boards and hotglued parts. It's here somewhere, but my apologies I can't locate it.
>>10854 James Bruton uses windshild wiper motors. >>10815
#Noise related Noise level reference: https://youtu.be/C62-Yl_V4NI Digital vs analog servos: https://youtu.be/2TVmWbIM3IM #Other servo topics Low quality servos might have shifting arms, not going back to the correct position: https://youtu.be/b4jAGz3YBSY Arduino and Servos (Drone Bot Workshop): https://youtu.be/kUHmYKWwuWs Removing jitter with 6000uf, 16V capacitor: https://youtu.be/S7EVRDPQmfE Wiring to reduce electro magnetic emissions: https://youtu.be/vMdJdTcW5WQ
Oh, wow. Spherical gear for a ball and socket joint. This is something I thought about myself, but just didn't know how to do it and thought it might be impossible anyways. https://t.co/rxWgbMnKKB via @61laboratory
>>10951 Wow, that's pretty interesting. If we could manufacture/purchase lightweight ball and socket actuators for our robowaifu's shoulders & hips then that would be a dramatic simplification of many kinematic problems in robowaifus. Thanks Anon.

3D printer resources Robowaifu Technician 09/11/2019 (Wed) 01:08:12 No.94 [Reply]
Cheap and easy 3D printing is vital for a cottage industry making custom robowaifus. Please post good resources on 3D printing.

34 posts and 5 images omitted.
>>9846 Huh. That's interesting. I wonder how you integrate inside the software to properly work with the standoffs like that and adjust the length of the supports? I mean, is there a 'use standoffs' checkbox or how does that work exactly?
Open file (40.15 KB 964x543 dynamic_print_bed.jpg)
>>9846 One of the biggest issues for repeatability with FDM is the consistency in diameter of the filament with tighter tolerances being more expensive due to higher quality control. This investment in a printer would make buying higher quality filament more economical in the long run. And the most notable thing in that image isn't the filament that wasn't wasted but the time not spent moving the print head around to create an unnecessary part. There's also parts like this that would be difficult or impossible to print without such a platform. >>9847 They're probably using custom gcode for research now.
>>9848 >They're probably using custom gcode for research now. I see. Thanks for the information Anon. I was entirely unaware of any such 'dynamic print bed' type printers. I wonder if they could be usable by hobby-tier robowaifuists someday?
>>9849 The "hobby-tier" printers are rather ones which aren't industrial or something, but also still for professionals which are using them for prototyping. (I don't like the distinction in pro and hobby). I guess something like that is surely possible, if it has enough benefits. But not for the cheapest models. Looks to me like it requires a core XY system, so the bed doesn't move. Which already makes sense for very small and fast, or the bigger ones. Not so much for the cheap 20+X cm.
Open file (174.44 KB 1280x960 pudding.jpg)
Maker's Muse on 3D printing myths: https://youtu.be/oX4up29xUuw[Embed] - It's a new technology (it's 40yrs old) - ABS ist stronger and better than PLA (if it is, then it's a amalgam, a mix) - Bed leveling isn't leveling at all (there's also tramming) - Paper is good enough to level bed (feeler gauge is better)

Robowaifus in media Robowaifu Technician 09/10/2019 (Tue) 06:24:00 No.82 [Reply] [Last]
After reading anon's Robowaifu fiction bread, I wondered what media is out there that already predominately features a robowaifu(s) as an important character. Animu and mango are obvious choices (pic related), but surely there are live action movies as well.


post robowaifu movies, books, etc.
225 posts and 88 images omitted.
Open file (36.97 KB 680x533 IMG_20210606_093710.jpg)
>>10915 I only really looked into his Instagram, after posting this. Holy F, this guy. He is maybe the the most relevant artist relating to what we're doing here.
This is a smaller set, but easier to access and download than via Instagram: https://www.pixiv.net/en/users/728801 - Perfect timing, got the link from Nitter which was down while writing this comment. He also ha a book, for a ridiculously low price (~19€/23$), which some here might want to buy. For example here: https://www.cdjapan.co.jp/product/NEOBK-2266285 >>10918 Lol, epic.
>>10922 >He is maybe the the most relevant artist relating to what we're doing here. <s/maybe/is >>10926 Thanks Anon, I saw that book too. I think we here should financially support both Sukabu and Ricky Ma and really anyone else helping to promote/popularize robowaifus to the broader world.
>>10922 Alita a cute. I hope they come out with #2 as well. I wonder if we could get away with making a robowaifu like her instead of a cyborg?
Open file (1.24 MB 2305x1607 Chii.full.400443.jpg)
Open file (1.78 MB 1000x1600 Chii.full.653209.jpg)
Open file (209.71 KB 2300x2684 Chii.full.401455.jpg)
Open file (280.76 KB 1024x768 Chobits.full.1065168.jpg)
Open file (355.21 KB 707x1000 Chii.full.1186397.jpg)
Here's some Chii's I hadn't collected yet. I felt like a fresh shot of inspiration from her.

Open file (756.16 KB 1920x1080 lime_awake.png)
Why consider alternative CPU architectures for secure systems? Robowaifu Technician 07/25/2020 (Sat) 13:55:25 No.4506 [Reply] [Last]
Hello Anons, wanted to share some info and perhaps make you think about what you should compute with. x86/amd64 -Proprietary ISA (Instruction Set Architecture) This means to get enough low-level detail requires signing non disclosure agreements (NDA). Even then, they might not disclose all the available commands (see Breaking x86 video below). If you cannot trust what the processor is doing, then no open-source software will make it any more trustworthy. -Complexity Common instruction sets come with hundreds (over a 1000 for x86) instructions. Breaking x86 instruction set https://www.hooktube.com/watch?v=KrksBdWcZgQ Hardware backdoor x86 (not for all processor models) https://www.hooktube.com/watch?v=_eSAF_qT_FY The more complex the system, the more bugs (in hardware and software). Intel had plenty of bugs that were discovered post release, for example the Pentium floating point division: https://en.wikipedia.org/wiki/Pentium_FDIV_bug). Interestingly, the x86 assembly instructions are actually decoded to a sequence of RISC instructions to be used by the internal cores of the CPU.

Message too long. Click here to view full text.

53 posts and 9 images omitted.
>>10941 >history into a tale You know, I've thought that we should find someone who's interested in documenting the rise of the robowaifu age at the hand of a small band of anonymous men on the Internet. Should be a good read if done well. >Now you're just being greedy XD Heh, maybe. :^) >Head, incl. eyes, lids, brows, mouth, jaw, tongue, nostrils, throat (w/ potentially cooling water consumption controls/valving) >50+ channels >Neck+shoulders+chest, incl. head rotation/leaning, 'breathing', arm-rotation controls, shoulder girdle, ~50 channels (2 arms) >Arm, incl. add'l shoulder, elbows, wrists, fingers, thumb, all finger knuckles, palm (50 channels per arm) >Central torso/Pelvis, incl. spinal column rotation/leaning, pelvic girdle control, hips w/ rotations, ~50 channels >Leg, incl. add'l hip, knee, ankle, ball of foot, toe flexion, ~50 channels (2 legs) >Various power charging/control systems ? >Various cooling systems ? >Various computing power control/conditioning systems ? >Add'l various kinematic/positional systems ? >Visual analysis systems ? >Hearing analysis systems ?

Message too long. Click here to view full text.

>>10942 I was thinking of a distributed topology, where across the whole body there are low-level controllers that deal with sensors/actuators on an individual level, while communicating with a central (beefy) processor that's running the main OS. Something like a CAN bus in cars (although I can't speak for CAN as I haven't used it yet). In that case, you won't need 100s of outputs on a single FPGA, but perhaps limited to about a 100 at most. Of course the difficulting of micro-managing movement arises. But surely as the brain doesn't fully manage our bodies (the spine and other parts help out), so should the robo-waifu main system should delegate tasks? Imagine a command protocol where instead of telling the leg to move to a specific set of coordinates, the main computer provides required tolerances (i.e. "appendage within 20 cm radius of torso" or "leg must distribute 35% of the overall weight" etc.) and the leg controller (MCU or FPGA etc.) actually does the system analysis to get the leg there. With greater tolerances, the solution can be achieved faster, and so rapid motions are either less precise, or preparation is required beforehand (the robowaifu gets into a running position and the actual run is a simple progression)
>>10942 >>10944 Also just had a thought. The local appendage controllers can be provided with a time duration for specific tolerances, thus allowing some level of autonomy. The main controller would only update on a variable basis (depending on the complexity of the action) and only respond in real-time when an interrupt is received from the local controller saying that the appendage is outside the given tolerances. Perhaps like TCP (when a packet drops), the frequency at which main controller sends commands sharply increases when the appendage is outside tolerable range, and decreases proportionally to the rate of change of the deviation from tolerances.
Open file (334.48 KB 1214x1618 IMG_20210607_080232.jpg)
>>10944 >>10945 (Another anon) Yeah, that sounds more like what I want, though others here want a central bread box in the chest with everything inside.
>>10944 >>10945 Yes. I've thought long and hard about these kinds of issues myself. Honestly, I think we probably need a new thread here that targets these kinds of topics. Something like "Robowaifu Motion Control Systems", or "Robowaifu Distributed Control Network" or something like that. Ideas?

Open file (659.28 KB 862x859 lime_mit_mug.png)
Open-Source Licenses Comparison Robowaifu Technician 07/24/2020 (Fri) 06:24:05 No.4451 [Reply]
Hi anons! After looking at the introductory comment in >>2701 which mentions the use of the MIT licence for robowaifu projects. I read the terms: https://opensource.org/licenses/MIT Seems fine to me, however I've also been considering the 3-clause BSD licence: https://opensource.org/licenses/BSD-3-Clause >>4432 The reason I liked this BSD licence is the endorsement by using the creator's name (3rd clause) must be done by asking permission first. I like that term as it allows me to decide if I should endorse a derivative or not. Do you think that's a valid concern? Initially I also thought that BSD has the advantage of forcing to retain the copyright notice, however MIT seems to do that too. It has been mentioned that MIT is already used and planned to be used. How would the these two licences interplay with each other? Can I get a similar term applied from BSD's third clause but with MIT?

Message too long. Click here to view full text.

Edited last time by Chobitsu on 07/24/2020 (Fri) 14:07:59.
26 posts and 5 images omitted.
Open file (517.52 KB 720x540 happy_lime_dress.png)
>>10921 While I was writing my wall of text, I was thinking about this very issue. Here's a stackoverflow page where a dev asks about accessing GPL library via a server: https://softwareengineering.stackexchange.com/questions/50118/avoid-gpl-violation-by-moving-library-out-of-process To me it seems to be this way: if your program is able to work stand-alone without the GPL code, then you may have flexibility in licensing. You're also not dynamically linking the programs, only using them as backends so-to-speak. In my opinion (not a layer!) as long as you provide instructions for users to install your software and any dependencies, then you're probably safe from derivative work issue. Your chatbot is quite different from the graph parsing/data fetching that the libraries provide, right?
>>10919 Thanks for the detailed, thoughtful post OP. Quite helpful. I particularly like the fact you've taken the time to break out some of the hardware & software considerations. While I subscribe to the general concepts behind the Unix Philosophy, I also realize that -- particularly in a hard-realtime embedded environment of a robowaifu, that such modular and clearly-demarcated software systems is neither efficient, nor economical, nor even practical, by-and-large. The real world often has a way of dictating terms to us humans like that, not the other way round heh. :^) This is certainly a very complicated problem, and fundamental constraints like functionality, performance, and cost must form the basics of our approaches if we hope to succeed at this. If we can manage all that and still utilize <insert Anon's favorite licensing & modular partitioning scheme here>, then all the better. It's definitely a complex topic, not one simply cut-and-dried. Also, the term >sufficiently -as in "...when another project sufficiently relies on the functionality..." raises a red-flag for me. If you feel inclined, we could use a more clear specification regarding this term. 'More clear' as in; 'How do we protect ourselves from the inevitable attacks against us, that this vague term will be abused to accomplish?' . I think licenses that are explicitly intended to free the IP to the extent humanly possible are by far our safest route here. To wit, the ones intended to grant the licensors themselves the greatest leeway possible. Namely, (BSD/Apache/MIT-like). Ones that take a leftist, ideologue type of approach to the topic, one intended to control everyone and everything around them, namely (GPL-like), are IMO much, much more likely to be used against us and to the detriment of the robowaifu movement overall. I realize I'm quite biased here. I can assure you that it's not a casual choice either, for whatever that's worth. Remember, these lawyers are very definitely not our friends; they are much more likely to be used as tools and pawns, intended in their usage to subvert and destroy any open-source robowaifu movement. After all, just ask yourself -- who is paying these people anyway? Also, would you care to spell out in further detail the terms 'strong license' and 'weaker license' if you would please?

Message too long. Click here to view full text.

>>10931 >I particularly like the fact you've taken the time to break out some of the hardware & software considerations. I deal with both, so it's important to know how the two are licensed. Didn't really consider the differences until I read about HDL (Hardware Description Language) licensing. Here's a good report/letter describing GPL pitfalls when it comes to hardware description (neither software or a physical hardware): https://ohwr.org/project/ohr-meta/wikis/Documents/GPL/LGPL-for-HDL:-open-questions >I also realize that -- particularly in a hard-realtime embedded environment of a robowaifu, that such modular and clearly-demarcated software systems is neither efficient, nor economical, nor even practical, by-and-large. Thanks for pointing that out. Even though I already knew about these limitations, hearing it now clicked in my head. For many reasons it is a better idea to use permissive licenses. >I think licenses that are explicitly intended to free the IP to the extent humanly possible are by far our safest route here. To wit, the ones intended to grant the licensors themselves the greatest leeway possible. Namely, (BSD/Apache/MIT-like). Ones that take a leftist, ideologue type of approach to the topic, one intended to control everyone and everything around them, namely (GPL-like), are IMO much, much more likely to be used against us and to the detriment of the robowaifu movement overall. Indeed, that you are right. I have been weary of GNU's leftism, but I agree with the concept for non-real-time software applications. Perhaps that's the last remnants of my idealistic youth influencing my thoughts. Studying OpenBSD/FreeBSD has actually got me pondering on what sort of licensing I should really use. >I realize I'm quite biased here. I can assure you that it's not a casual choice either, for whatever that's worth. Remember, these lawyers are very definitely not our friends; they are much more likely to be used as tools and pawns, intended in their usage to subvert and destroy any open-source robowaifu movement. After all, just ask yourself -- who is paying these people anyway? Hard to argue against this. Past experience has shown men that this is indeed what happens. Must be prepared for it. >Also, would you care to spell out in further detail the terms 'strong license' and 'weaker license' if you would please? Of course. I think I started using "weak" after seeing in the CERN Open Hardware License (OHL) page. Apologies for the confusion XD Specifically CERN-OHL version 2 has three versions:

Message too long. Click here to view full text.

>>10935 Excellent response Anon, many thanks.
Open file (93.68 KB 1024x820 IMG_20210218_021948.jpg)
>>10927 >>10935 Thanks for all your input. I have to look deeper into this. Your link is again very fast about either the question if the wrapper is GPL, which isn't the issue. Or it's about linking within a binary, but not e.g. about importing some library in Python which interacts with some program written in C++. I will most likely use GPL licenced programs by others in my AI, so if this taints it, then it can't be avoided anyways. >>10931 >I also realize that -- particularly in a hard-realtime embedded environment of a robowaifu, that such modular and clearly-demarcated software systems is neither efficient, nor economical, nor even practical, by-and-large. I don't see myself ever working on anything that lives up to your standards, so you don't need to worry about it :^)

ROBOWAIFU U Robowaifu Technician 09/15/2019 (Sun) 05:52:02 No.235 [Reply] [Last]
In this thread post links to books, videos, MOOCs, tutorials, forums, and general learning resources about creating robots (particularly humanoid robots), writing AI or other robotics related software, design or art software, electronics, makerspace training stuff or just about anything that's specifically an educational resource and also useful for anons learning how to build their own robowaifus. >tl;dr ITT we mek /robowaifu/ school.
Edited last time by Chobitsu on 05/11/2020 (Mon) 21:31:04.
89 posts and 60 images omitted.
>>10548 Good thinking Anon. Not him, but I've worked through Convict Conditioning, and while I was doing it I thought often about the fact that the very same issues of dynamics & strength were actually going to be important design & engineering concerns for us as we build robowaifus. That opinion hasn't changed in the slightest now that I'm actually looking harder at the skeletal designs for her, etc.
Latest Release Completes the Free Distribution of A Knowledge Representation Practionary: https://www.mkbergman.com/2461/entire-akrp-book-now-freely-available/ >A Knowledge Representation Practionary is a major work on knowledge representation based on the insights of Charles S. Peirce, shown at age 20 in 1859, who was the 19th century founder of American pragmatism, and also a logician, scientist, mathematician, and philosopher of the first rank. The book follows Peirce’s practical guidelines and universal categories in a structured approach to knowledge representation that captures differences in events, entities, relations, attributes, types, and concepts. Besides the ability to capture meaning and context, the Peircean approach is also well-suited to machine learning and knowledge-based artificial intelligence.
>>10634 Wow, sounds like a remarkable work Anon. Look forward to reading.
>'''"Mathematics for Machine Learning - Why to Learn & What are the Best Free Resources?"'''
Talented and very smart technical animator. Science & Technology topics. https://www.youtube.com/c/ThomasSchwenke-knowledge/playlists

Report/Delete/Moderation Forms

Captcha (required for reports)

no cookies?