This is something of a feature suggestion. It’s one you may or may not want to implement. I suspect it’s possible based on some assumptions I am making about the site architecture and how the device works based on reading the developer API.
I am going to make the assumption that external sites are using your js api to integrate and connecting to devices with the token via your servers, which act as a gateway. Both because it’s the only sensible architecture with how the devices work. And because I just looked over the device.ts in the SDK.
Given that, it feels like it would be possible to expose a vaccum maintenance option in the SDK, and I think probably importantly. Allow users while connected to set a default vaccum maintenance state for their session, for any media that doesn’t make an independent assertion. This would mean any site using the SDK that doesn’t update their UI, or that doesn’t adopt the latest version, would have a fallback state to an established value. Assuming someone hopped into fun.autoblow.com and set it. Would allow sites like faptap, SLR, etc to have a behavior people could adjust of the sites integrate that, or tune in fun, if they don’t.
Just a thought.
I’m not sure if you know, but we recently added a vacuum maintenance option within Video Sync on fun.autoblow.com. It appears on the player window itself now.
Under normal conditions, vacuum maintenance is only managed by the user, and no site that integrates with us, even ours, assumes anything and does anything to vacuum maintenance.It is only if you set it on fun.autoblow.com that you can turn it on at various levels during your session.
I’m not sure how this might or might not relate to what third-party sites can offer, but our technical team will see this and reply if they have any thoughts.
I tried it out on fun.autoblow.com the other night, which is what made me think third party integration would be worth considering. It’s nice that it’s there. That level of integration seems like it might be a stretch for third party sites unless they wanted to add it themselves. I have not dug into the SDK that deeply. I’m guessing the vacuum maintenance option is likely exposed there as well and the web site is just leveraging it. Pure conjecture on my part based on how I think it probably works. I might go read the SDK in more detail later tonight. Or while I am on my upcoming trip. Depending on what is there, I may be able to affect a change in state in the browser console by issuing a js command. Not sure without digging a little.
Turns out you can just do this. You can open the remote control page on fun and leave it paused and use the stroke + and - controls and set the vacuum automation level while another source actually controls the pump speed via a funscript, like faptap, etc. Seems to work just fine. So nothing needed.
It’s amazing what other people figure out about our stuff that we never thought about.