While filming the Buttplug Websocket tutorial, I realized how painful it is to do the first SSL setup in the websocket server. On top of that, we're still not signaling to users what toys actually work with their setup.These are things I get lots of questions about, yet we haven't really been addressing those questions lately.

I'm trying to do some development planning right now, and I'd like some feedback on what'd you'd like to see improved if you use Buttplug/Syncydink/ScriptPlayer/etc..., or if you can't, why not.

SEE I TOLD YOU I'D GET BACK TO MAKING VIDEOS.Even if they are pretty spectacularly boring.

This is a quick (well it still took me like 6-7 hours between scripts, editing, etc :| ) video showing how to use the Websocket server. We've got a lot of UI needs to clean up, but we're having to operate on so many fronts right now that prioritization is difficult, so instead I'm just making videos to act as a patch until our UX sucks less.

In lieu of video recording, I guess my brain decided it wasn't done futzing with web programming. I ended up making improvements to the syncydink haptics timeline viewer, and added a toy simulator with graphics by funjack (of golaunch/launchcontrol/funscript fame). Now you can see how a toy will react to a video or haptic script, even if you don't have the toy handy!Also, if you just want to play a script without a movie, that's doable. If you load a haptic script, then choose "Show timeline", there's now a play/pause button on the bottom of the timeline bar. This will play the script without needing a movie loaded. If you /do/ have a movie loaded, the playhead in the haptic timeline can now control movie position, and vice versa.

The other buttons there are for looping, and locking the timeline. Unlocking the timeline will let you edit/add/remove points, which will be part of the upcoming encoding feature. Right now, it's mostly for show.

Ok, time to make an "I'm not dead" update.I'm not dead.

There's lots of work happening on Buttplug right now, but most of it is fairly invisible. I've been spending lots of time learning about how to properly build web app dependencies so developers can start using the same components I used to make Syncydink and Playground. This has taken more time than planned (was a rather complex learning process to get typescript/vue.js/webpack to all play together nicely), but is finally done. The hope here is that people that want to write new webapps for buttplug can do so quickly and easily with these components.

https://buttplug.world/playgroundSo far, all of the applications for Buttplug has been about outside media. Movies, games, etc... 

Decided to go more minimal and just make a web app for testing toys and basic "manual" control. It's called Playground.

It's time for this month's Q&A! If you've got any questions for me about Metafetish, Buttplug, Sex Tech, Me, The Universe, etc..., post them in the comments to this post.(General project status post coming later this evening)

Our first emergency bugfix! Found an issue in the updater right after I released v0.1.1, fixed that and pushed out v0.1.2 shortly afterward last night. According to logs, only 5 people downloaded v0.1.1 before that, so if you're one of those 5, you should update to v0.1.2. :)

Buttplug C# 0.1.1 is out! Get it athttps://github.com/metafetish/buttplug-csharp/releases/tag/0.1.1

• Added auto update and update checking functionality
• Added support for the following hardware: WeVibe 4 Plus, Ditto, Nova, Pivot, Wish, Verge, Lovense Domi
• Added more product names for the Lovense Hush (LVS-Z36, LVS_Z001)
• Added Game Vibration Router application
• WebsocketServer now defaults to SSL

It's time for this month's Q&A post! I keep saying these are going to be videos, but has yet to happen, so this month I think I'll be a bit more realistic and just say post your questions about Metafetish/Buttplug/Me/Whatever in the comments to this post and I'll answer here like I normally do. :)