Speaking of sex toy security, this reminds me of one of my favorite recent posts here:<p>Blowjob Injection Attack - <a href="https://news.ycombinator.com/item?id=24702282" rel="nofollow">https://news.ycombinator.com/item?id=24702282</a>
> When working on Buttplug applications, something that should be at the forefront of your design thinking is:<p>> Someone is going to fuck this.<p>I love this project.
This reminds me of a story an industrial designer told me: he worked on a dildo with a scripting system, so the ladies could set the number of milliseconds for each waveform profile on the haptic motor. The product was not a success.
Reminds me of an episode of MST3K where they played a '50s beer documentary that went in depth into all the science and engineering behind keeping the beer cold between the brewery and the store. Then one of the robots pops up and says - "Meanwhile, the Soviets were developing Sputnik."
I played a bit last year building my own sex toy controller, using a lightweight RPi Zero, an Erlang server, and a nanoKONTROL2 controller. It was quite fun and I hope to find some time soon to resume working on it :-) Bluetooth isn't a fun protocol to deal with, tho.
I checked the webpage and i must say that i am totally confused. First, it says buttplug is a library. Then, in architecture overview there are 'protocol' and 'client/server', which does not make sense for a library. So it is not a library, but a deamon handling these devices? Wh then call it library? If it is a deamon, is there any user configuration? Am i only one who is totally confused?<p>Perhaps some picture with components and relations between them would be helpful?
If curious see also<p><a href="https://news.ycombinator.com/item?id=23094477" rel="nofollow">https://news.ycombinator.com/item?id=23094477</a>
> 2013 - First Python implementation, known as “Fuck Everything”.<p>Amazing. Nice to see people dedicated to the fine arts of buttplug manipulation.<p>Just FYI:<p>> August 2017 - Kyle incorperates Nonpolynomial
What happened with python support? Is it coming back or just dropped?<p>> 2013 - First Python implementation, known as “Fuck Everything”.<p>> Buttplug v1.0.0 is available in the following flavors:<p>> Rust – Crates.io, Github<p>> C# – Nuget, Github<p>> JS/Typescript (via WASM, Web-only currently) – NPM, Github
Looks like the Github is here: <a href="https://github.com/buttplugio" rel="nofollow">https://github.com/buttplugio</a><p>I expect we'll see some interesting issues posted there eventually
I was curious and tried working with this an a device about a year ago and the whole thing felt like a mess. There are browser components, electron cancer, web-to-bluetooth pieces. I think I could get my device to register/pair but couldn't get anything past that.<p>I was looking through the docs and the only useful thing seemed to be the low-level code if I wanted o make my own applications on top of it.<p>The reverse engineering work is important, but the tooling/UI needed work. I actually want to contribute to this to help, but it's a bit far down on the backlog of life.