One of the things I've been horrible about is archiving my past presentation work. Now that I've got a youtube channel, I'm aiming to both fix that and also get easy content together that doesn't require much new work on my end. With that in mind, here's a remaster of a sex tech overview presentation I did in 2007. This youtube version is censored in a few places because this is back when I thought it was edgy to throw porn in my slides, but I may have an uncensored version up elsewhere soon.

Burnt out, apparently.Not a lot to update on at the moment. I seem to have hit a burnout wall pretty hard a couple of weeks ago and am working my way out of that now. My brain can't seem to make code come out for anything other than my dayjob, so Buttplug dev is going slow. I'm mostly resting (and playing Red Dead Redemption 2) and doing little things here and there, but I don't foresee any major development happening until Christmas week, when I've got lots of time off.

In the time when I am productive, I'm doing some video work at the moment to try and get more content on the Youtube channel, and I would really like to have at least 1 or 2 tutorial chapters of the Buttplug Developer Guide up by the end of the year.

The end of the maintenance period is in sight! I think! Maybe!buttplug-js 0.9.0 went out this weekend, putting the JS codebase in line with Buttplug C#, which now means I can hopefully start on a new version of the Buttplug Developer Guide (the document I'd like to be able to point new developers to on how to use this project) with reasonable expectations of the C#/JS APIs looking mostly the same. This also means I can move on to upgrading the C# and JS user applications (Server, GVR, Syncydink, Playground, etc...), and maybe, just maybe, working on something new.

Of course, I'm hemorrhaging Patreon members for reasons I'm not real sure of (I figure probably boredom at the months of my yak-shaving the library), so thanks to those of you still sticking with me. I'd really like to spend December getting more hardware support in, getting applications up to date, and figuring out some new small projects to work on that won't eat months.

Surviving. Barely.SLSA in Toronto went great. It was my first humanities conferences and I only barely embarrassed myself like, 3 or 4 times, max. I'll be doing a youtube version soon, not that the information will be new to anyone here.

Since I got back, I've mostly been back to patching software. Both Buttplug C# and JS got point releases this week to fix yet another schema issue that new versions of JSON schema parsers seem to be picking up now. Yay more strictness, boo having it wrong in the first place.

Well, after releasing Buttplug C# 0.3.0, someone found a bug, so I released 0.3.1 this week! Yay releases that take less than 5 months!I'm also talking to the author of ScriptPlayer about starting to port it to Buttplug C# 0.3 at some point. This would remove the Websocket requirement (as we now have other, more direct ways to connect. If you're wondering, it's IPC over Named Pipes), making connection much easier.

We've also identified a Bluetooth chipset that none of our software seems to work with. Qualcomm Atheros Bluetooth (usually built into motherboards on laptops) doesn't seem to work with Buttplug at all. I'm not sure what's up, but I've been doing a lot of support on that lately.

You ever see someone do something dumb and be all "oh yeah I'd never do that thing" then you totally do that thing?I did that thing.

Buttplug C# 0.3.0 has been 5 months in the making. For what is basically a one-person project now (I'm working on the core alone at this point, after realizing most of the design for this is in my head and I'm not real great at writing that design down yet so it's hard to ask for help), that is kinda ridiculous. It's been a massive overhaul that could've maybe been done in smaller chunks, but there comes that problem of "what if someone uses it in the middle and I break them with the constant changes". Going silent for 5 months isn't super helpful either though.

Being an old man that yells at clouds, mostly.For some reason I decided to go all "IT'S TIME FOR SOME GAME THEORY" on twitter this weekend which ended up as 2 threads about machine learning and blowjobs on twitter:

https://twitter.com/qDot/status/1055865846726152192

Yeah ok at this point it's just time to admit I didn't know what I was doing with C# a year ago and now I'm basically rewriting half of the project to make it actually work like actual C# programmers would actually expect.There. Done. Brutal honesty.

Finding all sorts of potential bugs in buttplug-c# as I continue on this deep scrubbing, which is good! There's been messages doing wrong things, unexpected ways to break the system, etc etc etc. It's all good cleanup that will hopefully lead to a glorious future with zero technical debt so I'll never have to do this again.

Well I've got one hell of a code katamari going on here.Buttplug C# 0.3.0 continues to trudge slowly toward release, gaining more features and fixes all the time. Last week was mostly spend hammering the Serial Port support into a better state, so we can support something other than the Erostek ET-312B. This will include:

• EStim System 2b

Wow. Completely flaked on an update last week. I blame Yakuza 0.The good news is, I have finished Yakuza 0 and resumed doing other things with my life. Buttplug related things even!

I just merged the new client examples into Buttplug C#'s mainline: