* Buttplug: An open-source software suite for teledildonics (https://buttplug.io/) 5 years ago | 249 comments
* Empathy for the user having sex with your software (https://docs.buttplug.io/docs/dev-guide/intro/buttplug-ethic...) 10 months ago | 127 comments
* T-code – A protocol for implementing UART serial communications to an adult toy (https://stpihkal.docs.buttplug.io/protocols/tcode.html) 2 years ago | 74 comments
* An open-source standards and software project for intimate hardware (maybe NSFW) (https://buttplug.io/) 7 years ago | 39 comments
* Buttplug Sex Toy Control Project Implemented in Rust (https://buttplug.io/) 2 years ago | 3 comments
Then again, it might raise uncomfortable questions about the pen testing I have on there. Something something something backdoor.
Penetration testing (especially with red and blue teams). Agile. Continuous delivery. "Move fast and break things". Application firewall. Protection at rest. Injection attacks. Man in the middle. Load balancing. And so on.
There's one phrase I'm too fond of, that I thought of the other day:
Enterprise Teledildonics
Someone please make it become a thing.
'Packet sniffing', while not sexual, is also something a lot of men in Britain do.
>Someone please make it become a thing
Why stop there? How about "Global Teledildonics". I think the world would be a better place with that.
man date
man wait
man yes
man unzip
man touch
man expand
man mount
man glob
man unmount
man zip
man nano
man sleep
Hot swap. Hardening the system. Spoofing. Release pipeline. Uptime guarantee. Burst capacity. Stand-up. Forking the repo. Detached HEAD.
Why ask LLM for puns anyway? Do you delegate all the fun or activities in your life?
Man... maybe I just like to have fun at scale.
not sure what spoofing would be in a sexual context, but it does sounds like something potentially illegal, or at least morally gray :D
Maybe because Spoof sounds simiar to Snuff...
Spoofing may be the act of pretending to blowing coke up someone's butt, but then "accidentally" snorting it yourself.
Samantha: Woah, easy now. It's my turn!
Dave: Alright, alright, I'll do it! [prepares straw; fakes choking, coughing]
Samantha: WTF, Dave?! Freeloading as always, now you fucking spoofed me???
* Deldo is a sex toy control and teledildonics mode for Emacs (github.com/qdot) (2021) https://news.ycombinator.com/item?id=29207607 | 126 comments
« We were vibe coding before it was cool. »
><
Until I saw this post, I thought the e-bike community was the largest "hacker" community in regards to tampering with your electronics, but I imagine it too is dwarfed by sextoy hackers. Anyway, here in Europe there are a lot of hacks for e-bike computers. Part of this is because many people want to increase the software restraints on speed limits. Which is illegal, and, at least in larger Danish cities also very likely to get caught. Many people do it for statistics though, my e-bike computer as an example resets my "current" milage every 500km and then store the total in another place (something which gets reset everytime it's in the shop). It also didn't have a clock option for any of it's standard screens. My primary reason for hacking it was getting a clock on the display, but I now also back-up my milage + I have some added statistics for fun. When it needs to go into the store, I re-flash it to the factory settings or whatever you'd call it. I'm by no means a device hacker, but it wasn't hard to search engine my brand and find the tools I needed to do what I wanted.
Anyway, I don't think there is a lot of "secuirty" in any of our daily devices. Maybe it's because I'm European and a lot of people wouldn't want the NSA watching in through a Google Camera, and therefor buy non-major-tech-company brand stuff, but even things from large brands like Bosch are very hackable. Again, I'm not a device hacker as such, but isn't everything rather hackable once you have the hardware?
Not really. People in the space are to used bending over backwards to please their customers.
Some of them, like Lovense, have said they had intention to publish APIs, but they just have some empty repositories in Github. (Lovense is a weird company, everything points to just one or two persons in [IIRC] Taiwan. They're very opaque.)
And some have been fishy too. There have been class actions against brands like Hytto / Lush [0] or We-Vibe [1]
--
0: https://www.courthousenews.com/judge-forwards-class-action-s... 1: https://topclassactions.com/lawsuit-settlements/lawsuit-news...
Assumption based on connectivity experience, since the Bluetooth connection is usually rather unreliable and weird, and obviously not as well engineered as even cheap Bluetooth in-ear headphones, or game controlers. Ironically very susceptible to being blocked by body parts (which means vibe no more). Seems, like it's some dead simple serial transmission, which isn't fault tolerant at all. Those controllers are not bothering with any buffering, or much any computation at all really. Seems like they just straight stream signals to the motors.
> Intimate Haptics Control Standard and Library
From https://buttplug.io/. You get better explanations here https://buttplug-spec.docs.buttplug.io/docs/spec
I'm qDot, creator and project lead of https://buttplug.io!
We're already well off the front page but feel free to AMA. :)
I will state that this specific MCP Server is pretty useless and certainly not how one would want sexual interaction, I try to indicate this in the README. But, a beginning has to start somewhere and good-giving-game is how we roll so it's on GitHub.
[Ironically two years before, my project was Buttplug-integration in a Charm-powered SSH chatroom with BubbleTea TUI. That navigated aspects of digital consent via SSH keys, making an anonymous graph of what entities could do what to other entities' devices. I think some of that is needed in an Agent-Controlled MCP future.]
I'm not the Buttplug.io maintainer, but did chat with them about this for a while on Discord. While I have your eyeballs, they are looking for additional maintainers for their project if any Rustaceans are interested. This MCP server is written in Golang but would be better in the Buttplug ecosystem if it was Rust.
My early career was in haptics research and I have several patents in it via Immersion. My master's thesis was writing a 3D haptic renderer and integrating haptics into VRML, if you remember that! I have worked on NIH grants for Sexual Dysfunction diagnostic devices and created homemade toys. Now that I just received my Neurable EEG headset, I am working on Biaerolar Beats research [1].
On the topic of vibe coding, yes I vibrated my LELO F1 with this, but this project was truly a hand job. I did try to vibe code `a2a4a2a` (A2A protocol for A2A fun) a few weeks ago, with both Claude and Gemini, but A2A protocol was too new and it was too hard for me to teach it A2A. I'd be interested in seeing how people handle this in general.
All in all, it was fun and I learned a lot about tool-calling LLMs. That week I made three MCP servers (thanks `mark3labs/mcp-go`), one for money [2], this one for sex [3], and one for drugs [4].
Although I haven't followed up on that last AgentDank [4] yet, it's probably the coolest in terms of open data and actual AI results -- just watch the video there. Bringing custom data plus SQL endpoint to a tool-calling LLM is ridiculously powerful.
[1] https://github.com/ConAcademy/biareolar-beats [2] https://github.com/NimbleMarkets/dbn-go/blob/main/cmd/dbn-go... [3] https://github.com/ConAcademy/buttplug-mcp [4] https://github.com/AgentDank/dank-mcp
I remember some people have wired their vibrators intensity and vibration pattern to their vi(m) configuration, e.g. current indentation depth.
It's unfortunate just how stigmatized such software (and the associated devices) still are because it's a very, very interesting field. I myself started what I thought was going to be a small haptic feedback side project and have fallen down a rabbithole I never could have imagined existing.
The sex toy/haptic feedback world has, if I'm honest, reignited my love for development.
Like many things, there can be stigma e.g what Masters&Johnson faced, but if you are serious you can get past it pretty easily. We've done serious psychophysical studies and tried to make tools that helped people medically and emotionally.
But it's also OK to be playful too. More than anything about intimacy, this specific project was a quirky response to the "MCP All The Things" zeitgeist at the time.
Like writing science fiction, by working with these things early in any way, you earn an appreciation for the problems. After a week of MCP, it became abundantly clear about the Security and Observability problems. User configuration was rough too. I spent the next weeks working on sandboxing tech, MCP observability tech, and other ideas. None of that got to a good-enough-to-publish level, but my understanding/capability was increased.
Other issues are how you model consent of personal devices and maintain that with LLMs or other users. How do you define what the boundaries and shared capabilities are? Do you incorporate reputation? How do you distribute or federate that? How do you maintain anonymity but keep it useful? How do ephemeral agents get access to that data? [I don't explore any of that in this project.] These are general problems with MCP/A2A servers that will need to be solved. It's not just about buttplugs, but a slew of data and services, if we allow these AIs to become part of our daily life.
It truly is a beautiful thing. Even when it's butt stuff.
I do mind degradation of language and the normalisation of what is plainly an obscene concept like this.
I bet there would even be some software framework that forces a particular response, but I would also not recommend calling that project 'rape'. Probably most would agree in that case, but I don't know.
I wouldn’t worry about this project becoming overly mainstream or changing everyday speech.
I disagree - I think the word is already frequently used; the unnecessary use by this project is just another example.
I've no problem with the software or anything like that. Although, I could say that even in the context of the software its a bad name as it is too specific - as you say, it is for intimate toys in general, not specific ones. I also don't think it is going to be valuable for search purposes.
Yes, I mean we should ban all abbrev with M in it /s
Is it valuable? Maybe for someone it is.