[l0rn]

From reading the docs I see a pretty generic device fleet management framework. What makes this software specific to sex toys besides the intention of the authors and the name? Couldn't you just as well manage - i dunno - a fleet of corporate e-scooters with it?

[l0rn]

Thinking this thought further made me giggle. Imagine devs deciding it's the best option for managing some enterprise device, onboarding would be so funny. "Yeah and now you need to enter the address of our buttplug server [..]"

[qdot76367]

You're absolutely correct! I mention this elsewhere in the documentation even. Buttplug really is just a userland HID manager at its core. The only specialized part is the context of commands we send to devices.

The original plan (and it may still happen, who knows) was to figure out a way to chop off that top message layer and create a generalized system for doing exactly what you've said. That was going to be called 'deviceplug', and it's why btleplug is under the 'deviceplug' org on github (https://github.com/deviceplug/btleplug). I've just never gotten around to it because I'm not quite ready for the additional support burden yet.

All that said, Buttplug is also a haptics experimentation project aimed at finding out what it's like to create a way to communicate about a very specific type of touch via technology and programming. There are specific goals within the project related to that, but the amount of tech required to actually pull that off means I end up with what basically amounts of a fleet management framework. :)