Empathy for the user having sex with your software

Overall reception and tone

• Many commenters expected jokes but found the ethics and UX focus serious, thoughtful, and well-written.
• The thread is full of puns, but there’s consistent respect for treating intimate hardware/software with more care than typical consumer tech.
• Some compare this attitude favorably to high‑profile failures in mainstream infrastructure software.

Technical scope and complexity

• The core library supports hundreds of devices from dozens of manufacturers over BLE, USB, serial, and network protocols, across major OSes and WebAssembly.
• A commenter who replaced it with a tiny custom script is told the difference is scope: one-brand, one-transport, one-platform vs. a generalized, cross‑platform, multi‑device framework.
• The Bluetooth LE layer is described as a major burden due to divergent platform APIs and vendor quirks; the maintainer regrets having to own it but acknowledges it mostly works now.
• Some organizations reportedly avoid the library purely because of its suggestive naming, or wrap it to satisfy contracting constraints.

Bluetooth reliability debate

• Experiences with Bluetooth vary wildly: some say it’s very stable now; others describe it as consistently unreliable, especially with cars and mixed-vendor setups.
• Several note that the protocol stack is large and vendors frequently implement it poorly, causing erratic behavior.

Safety and hardware limitations

• Commenters stress that many sex devices are output-only with no safety sensors.
• Specific classes of machines (e.g., certain strokers) are described as genuine pinch or injury hazards; software empathy cannot compensate for unsafe mechanical design.
• There are anecdotal reports of severe injuries from poorly designed hardware.

Beyond sex toys: abstractions and reuse

• At its core, the system is described as a generic userland HID / device fleet manager with a sex‑toy‑specific command layer.
• Commenters speculate it could manage other device fleets (e‑scooters, etc.), and there was mention of a possible generalized “deviceplug” variant.

NSFW, platforms, and culture

• Debate around NSFW code on platforms like GitHub:
  • One side worries about oversexualization and youth exposure, preferring those platforms remain SFW.
  • Others counter that teens already know about sex, OSS code for sex tech is not inherently harmful, and platform ToS already restrict children.
  • Several argue society is simultaneously prudish about healthy sexuality and permissive about exploitative or sexualized contexts.
  • There’s disagreement over whether sex work and adult content are inherently exploitative or can be empowering, with some attributing current prudishness partly to US cultural influence and platform moderation norms.

VR and real‑world UX gaps

• A user describes VR headsets (specifically PC‑tethered setups) working poorly for porn and “gooning” use cases: intrusive low‑battery dialogs, fatal errors, unstable desktop overlays, and regressions across updates.
• This is framed as an example of companies ignoring very common but unofficial user scenarios, in contrast to the article’s explicit user‑empathy approach.