@zackwhittaker Presumably none of this affects you if you throw out the cloud service and use #buttplugio instead? Paging @buttplugio ...

Just donated to @qdot as #buttplugio need funds as well as Wikipedia.

I finally bit in to the sour grape and created an NSFW alt GitHub https://github.com/drawnto

The first project PROVE.
A spin on the #buttplugio code base https://github.com/UncensorPat/prohe

instead of "haptics" it involves "voltaics" and uses PiShock for that.

I've already decided on the UX.
configureable random time interval the programmer will be juedged by whether they typed at all. Depending on that they will get rewarded or punished, which is a choice between shock, beep, vibrate for intensity & time.

Over the last 36 hours my feed has shown a sharp spike in threads that contain #buttplugio, #homeAssistant , #solarman and #NixOS integration.

This is pleasurable change.

SIGTERM works, i figured out a way to send it before starplug closes, and the audio stutter hasn't happened again yet. hooray! so i fixed a few user-friendliness issues, bumped up the default min and max APM, and published the first release of #StarPlug:

https://github.com/VyrCossont/StarPlug/releases/tag/v0.1.0

i am not responsible if Blizzard bans you, or responsible in general, tbh. have fun! porting to Windows is left as an exercise for the reader!

#StarCraft #BroodWar #ButtplugIO

https://github.com/VyrCossont/StarPlug

behold #StarPlug, an APM-based vibration mod for #StarCraft 1 and #BroodWar, using #ButtplugIO and #lldb. currently works only on macOS, but it works!

https://github.com/buttplugio/buttplug/pull/527

i made #ButtplugIO buzz a Dual Shock 4 gamepad on macOS today. gamepads are the vibrator everybody already has, but Buttplug's current gamepad support covers only XInput devices and only on Windows, a category that notably does not include Sony or Nintendo stuff.

since i used SDL2 for gamepad support in #Pinput, that part was easy, but Pinput's single-threaded. Buttplug isn't, instead using async code backed up by either a Tokio runtime or WASM threads, and most SDL types aren't thread-safe, which is where the actors in the previous posts came in: send gamepad control messages over mpsc channels to actors on a thread dedicated to SDL, get responses back using one-shot channels.

next challenge: figure out why the example vibe tester isn't exiting cleanly on Ctrl-C. something's still waiting to progress, i suspect. the JetBrains debugger is wildly inadequate for async stuff, where stack traces don't exist and threads are only vaguely relevant, but https://github.com/tokio-rs/console looks useful…

#Pinput now supports reading the touch/pressure sensors on the #Kiiroo Pearl 2.1 vibe (they get mapped to buttons and joystick axes), and in theory, also the sensors on the only other device that #ButtplugIO currently supports inputs from: the #kGoal Boost (although i don't have one to test with)

so if you wanted to make a #pico8 game but were holding out until you could control it with your pelvic muscles, now's the time 😄

(also, Pinput can now read the battery level of your haptic device, as it can already do for wireless gamepads on most platforms)

want to be able to do horny #gamedev with your fantasy console? here comes the 📳💓! i've just released binaries for #Pinput 0.1.4-alpha1, which adds #vibrator support alongside analog gamepad support for #pico8 and #wasm4 games, thanks to #ButtplugIO.

got questions? please ask me! i've written docs, of course, but i'd love if y'all tried it and let me know your use cases and any points of confusion.

hardware-wise, check the IoST Index to see if your toys are supported: anything marked as compatible with buttplug.io should work in theory, and i've been testing with BTLE toys from #Lovense and #Kiiroo and know them to work in practice.

#Pinput #ButtplugIO support now works in Chrome with either Web Bluetooth or a websocket connection to Intiface Central, and Firefox and Safari with Intiface Central only

edit: it actually works fine in Firefox. likely to be user error on my part.

slowly nudging the #WASM version of #ButtplugIO towards working for me, and now i'm getting Rust errors instead of JS errors, but wow… web dev is kind of a shitshow, huh…