Toying With This Week (Apr 18 - Apr 24)

Completed This Past Week

• Per block visibility and control permissions + Tools and scripts now are synced in online sessions - This was just awful to implement. Every tool and script now syncs its state across all clients which should make the user experience much friendlier. And per block permissions should offer up some new use cases particularly with online streamers.
• Stroker toy bugs - Toys like the Keon and Launch were not performing well at all and had issues with not reacting to speed patterns, moving way too fast with positional patterns, and not working at all if you set the lower stroke position above 0. Most of that is hopefully resolved now.
• Other bug fixes - The pattern selector would sometimes fail to open until you reloaded the website, and the Beacon Detector wasn't sending its state to scripts and thus wasn't usable.
• Affiliate link updates - I added a full per toy shopping page with all the toys that are supported by XToys
• Custom toy support - I got the most basic use case of a serial port controlled vibrator working, including a new page for setting up custom toys. But there's still tons of work to be done before I can publish anything.

Plans For This Week

Probably only one of these, as they're all going to be frustrating to implement:

• Continuing work on custom toy support
• Adding Bluetooth support for The Handy - The complexity of implementing their protocol is going to be fun, and I also need to figure out how I'm supporting a toy that has two connection methods. And I need to start showing an error when XToys has hit an API limit for The Handy.
• Audio sensor - I realized that it's possible on both Windows and Android to detect audio coming from a different app. So I'm thinking about adding support for having toys react to any active audio (music player, Chrome tab, etc). However it doesn't make sense for the audio sensor to be a separate tool and hook up to a script because it's going to be sending data faster than an XToys script will process it. So I might make it a full custom pattern that can be selected...which brings up its own pile of UI issues.
• Master intensity controls - I'm also thinking about adding main screen controls/script access to adjust the intensity limits for toys, or at least for e-stim units. E-stim really needs a way of setting a limit and then slowly allowing it to increase (as your body gets used to the current limit). But I need to still ensure guests can't mess with limits.