A few prior HN discussions on the Buttplug standard, including the inevitable "in Rust":

* 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

Is this the "vibe coding" I keep hearing about?

I've seen APIs for controlling those toys already a few times and it always surprises me that they're quite open. It's a thing I'd expect each device to come with a proprietary locked down app and nobody complaining about it publically, because that'd look.bad on them. Anyone can tell me why is that different? Is it because huge corporations are staying away from the market, thus they couldn't have ruined it?

> Buttplug is an open-source standards and software project for controlling intimate hardware, including sex toys, fucking machines, and more.

> Intimate Haptics Control Standard and Library

From https://buttplug.io/. You get better explanations here https://buttplug-spec.docs.buttplug.io/docs/spec

The .io top level domain is a perfect choice.

I once signed up fot a lecture on "consumer device security" (lawyer stuff). To my suprise, every example used by the presenter involved an internet-connected sex toy gone rouge. Either private information had leaked or the device had "entrapped" a user for ransom. I was at my desk laughing but couldnt explain why for fear of discussing the very nsfw content.

This plus ChatGPT scheduled tasks could make an interesting alarm clock

Keeping this in my bookmarks for the inevitable moment someone says big tech can shove unwanted AI features up their ass.

Woah! Hi!

I'm qDot, creator and project lead of https://buttplug.io!

We're already well off the front page but feel free to AMA. :)

Author here. What a Happy Friday to see this now, as I created it on April Fool's Day. I annually do silly personal projects on that day. That week I happened to be playing with MCP servers and thought it would be funny. ConAcademy is where I put weird ideas and implementations.

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

Curious how people here see the privacy implications of the various services out there. I suppose it was simpler in the old days where you could just buy a product and have no relationship whatsoever with the vendor and so nobody watching over your shoulder (as is the case with VR goggles nowadays and many other types of services).

Is there an llm that can dirty-talk? Would be amusing to tie the two together.

When Vibe Coding meets Headcrash (Bethke)[0]

[0] https://en.wikipedia.org/wiki/Headcrash

What a strange time we live in

Someone took the term vibe coding literally

I was hoping this was going to be a malicious MCP from the good old days of security tool naming.

Related to buttplugin' with teledildonics?

https://buttplug.io

I remember some people have wired their vibrators intensity and vibration pattern to their vi(m) configuration, e.g. current indentation depth.

I heard a story that these guys built one of the only high performing opensource Bluetooth stacks, and that it is a dependency for various SFW orgs… can anyone substantiate

I don't see the value to integrating this kind of thing with an LLM or find the presented use cases as compelling, but I'm always going to support more work related to Buttplug.io and I'm sure someone will find it useful.

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.

I’d like to say well, now I’ve seen it all, but I am sure the boundless curiosity and ingenuity of the human race will surprise me for a long while yet.

This is how the robot apocalypse will start

All right, that does it! I've had enough internet for today.

Finally something new and groundbreaking!

User-testing it was a pain in the ass.

How do hallucinations feel down there?

this has got to be the funniest thing i've seen from what an MCP could do this year LOL

please HN add some comments, I have no idea what to think about this.

How is the security?

backend engineer

sticky bit

floppy disk

lap top

big o

batch sorting

MCP is becoming a mature protocol.

I am going to let claude control the buttplug. Thats what she said before sh*t hit the fan. Literally.

Does this belong in hacker news?