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:

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:

• https://www.wired.co.uk/article/teledildonics-hacking-sex-toys
• https://arstechnica.com/tech-policy/2018/08/cybersex-toy-industry-heats-up-as-infamous-teledildonics-patent-climaxes/
• https://www.ozy.com/fast-forward/are-you-ready-for-a-sex-toy-revolution/88432
• https://www.geek.com/tech/whats-next-for-smart-sex-toys-post-teledildonics-1750177/
• https://motherboard.vice.com/en_us/article/ne55x8/teledildonics-patent-has-expired

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.