To complete the memetic conjunction, HN will surely be abuzz at the fact that the underlying buttplug library is, in fact, written in Rust. For when memory safety really matters: https://github.com/buttplugio/buttplug
The underlying library being written in Rust is something of a relief (if you'll pardon the expression) as I am nervous about anything to do with my butt being written in something called C Sharp.
I get the joke but it's worth pointing out C# is actually memory safe and more flexible than Rust in that regard (with the downside of less control on GC).
A question about delivery channel;I don't like receiving chess moves in my butt. If I wanted to get my chess moves in my penis would buttplug's device support include a viable alternative?
Also, I might be interested in parallel chess cheating. If DP is on the table would multi-match support be viable through the API?! I might have to break my no-pegging rule.. But in the name of increased chess move bandwidth it might be on the table.
Yup! The library is named Buttplug just because I like making large media publications say "Buttplug". I even made a whole video about it: https://www.youtube.com/watch?v=c6bghuCy6d8
Buttplug.io actually works with 100s of different toys. There's a full list at iostindex:
In terms of multi-match API support, we're... getting there. One of the dreams after the next big feature (MOBILE APPS! Thank god for flutter and flutter-rust-bridge) is getting WebRTC connections going, which should make situations like this easier to support.
