buttplug
buttplug copied to clipboard
Rust Implementation of the Buttplug Sex Toy Control Protocol
**Feature Description** We should be able to tests the state machine pretty well, as it contains all of the logic and comm managers only handle i/o.
**Describe the bug** Buttplug-rs has no way to handle whether a bluetooth adapter was plugged in or removed while it is running **Additional context** buttplug-rs uses btleplug (https://github.com/deviceplug/btleplug), which doesn't...
**Feature Description** Should build no features, client only, server only, all runtime types, etc.
**Feature Description** We can have things like the xinput feature build for documentation by adding decorators about when to build it.
**Describe the bug** In relation to #147, the device list showed a Nora could handle a RotateCmd even though that wasn't implemented in the protocol yet. This will confuse users.
**Feature Description** Requires #36 to be done, but that's fairly close thanks to the Lovense Dongle Manager. After that, just figure out how to build buffers for static speeds to...
**Feature Description** There's only one serializer, so things like ButtplugRemoteClientConnector could default to that type, saving users some type specification.
BLE Battery service/characteristics are standardized, so we can just detect whether they exist on connect. Usually we require explicit definition in the device config for endpoint names and what not,...
Whenever a remote connector disconnects, it should fail all in-flight messages in its sorter in order to unblock any async execution that might be happening otherwise.
**Feature Description** The Lovense Dongle can connect to multiple toys, but we only allow connections from one in our state machine currently.