Being in pain, mostly. But in a good way. But not in THAT good way.When I started working on Buttplug in earnest back in April 2017, I kinda figured that I'd get a little obsessed with working on it and maybe go slightly off my workout schedule.
I proceeded to basically not leave my computer chair for like 16 months.
An update! On time!If you guessed that I don't have much to say, congratulations, you're right!
This week has been more about fighting infrastructure than I would've liked. There's been some lingering breakage in how some of the Buttplug code is tested, and that ended up needing to be fixed and taking a non-trivial amount of time.
Well at least I have a good excuse for the first 2 week gap I've had in these updates, heh.As you are probably aware because I haven't (been allowed to) shut up about it for the past 2 weeks, the 268 teledildonics patent is now expired. So far this has meant LOTS of talking to press. A few examples:
I did a quick interview with BBC 5Live. At 3:45am UK time, heh. Luckily it was 7:45pm for me. Above link is my recording of it, please don't redistribute. Actual BBC archive is at https://www.bbc.co.uk/programmes/b0bfxpfy, I'm 2:43:00 in.
Don't expect to learn much here but you can at least listen to me be awkward!
I took a break from being productive on Buttplug to write a long, rambling blog post about the expiration of the 268 Teledildonics patent, which happens in about 7 minutes from now.I make bad choices sometimes.
It's been a week of me being angry at me from a year ago, mostly.Work on cleaning the Buttplug C# codebase continues. I'm currently trying to get all of the changes I've made over the past week finished enough to merge the code and figure out what all there is to do after this. This is hindered by me constantly running into something I did in the early months of the project and having to sit there for a while going "What was I thinking?".
The nice part of this is that I now have an updated perspective on the state of ALL of the code in Buttplug, which will hopefully mean I can write coherent documentation about it once I finish this overhaul. One of the major goals of this C# work is to make it so I can write one document for developers that has both C# and Typescript/Javascript in it, and that's pretty close to possible now.
When it rains, it pours.Even though no one may really notice. >.>
I spent all of Friday evening and most of Saturday completely rewriting our C# Client interface. The current version didn't really mesh with the Client code in our Javascript library, and I wanted similar architectures between the two so that I could write one set of documentation for both APIs. We're now much closer to that possibility.
I haven't sent out an official one of these in a while, so it's time to get started again as I try to vaguely adhere to my own tier rewards.Anyone got any burning questions for me? Ask in the comments!
As the weekly updates drift farther from the date they're supposed to be on...This week has mostly been working with some other developers on what may end up being our first full Unity integration! I'm not sure how this will look going forward, but I've got high hopes, since Unity support remains our #1 requested feature.
The work here was mostly adding some small features like the ability to inflate/deflate Lovense Max toys, and to run the Buttplug Server on windows without a GUI. Hopefully these features will prove useful for others too.
Videos and toy support!We had a couple of questions about toy support this week that we're now getting filled in. Turns out the Kiiroo Onyx 1 was never fully supported in our Kiiroo code, so one of our contributors took care of that. We also now support the WeVibe Classic, as requested by someone on the forums. Finally, I now have access to a Estim Systems 2B, meaning we can fill out a bit more of our estim support.
In Youtube land, I finally cranked out another Will It Buttplug video, covering Crimsonland, a twin stick shooter that also works as a surprisingly decent vibration pattern output. The big deal here is that I managed to get the video out in 2 hours start to finish, versus the usual 3-5 day filming/editing time of the hardware analysis videos. Hoping to get a better pace on video output now, and have a few more games lined up to test!