buttplug.io 🍑🔌 - Open Source Sex Tech

musclin' in on the squarepeg turf

this wouldn't have happened with a Free and Open Source hologram wife

If anyone wants to get in a social media fight with an open source project, our calendar is pretty open

Starting soon~

Lewd PEAK collab with
@itsrenrie.bsky.social
@itsvenyxia.bsky.social
@johnnyjellyjaw.bsky.social
@faesfables.bsky.social
@kittychanlewd.bsky.social

and some of us will have @buttplug.io hooked up!

Bluetooth: not even once

nani the fuck did you just fucking iimasu about watashi

HIGHWAY TO THE CUMZONE >>>

I booted up Ace Combat 7 and strapped on my toys, connecting it with @buttplug.io to turn the game vibes into toy sensations. Firing the afterburners, taking damage and shooting turned this into a moan-filled edge fest!

VOD is up on Fansly!
#inkysuss

Lovense: The Company That Lies to Security Researchers How Lovense has ignored the same critical vulnerabilities for 2+ years, lied about fixes, and manipulated bounty payouts while leaving 10s of millions of users exposed.

PSA: Lovense products leak your email from just your username. Reported in March, still broken.

Worse: Another Vulnerability was "fixed" in 2023 but wasn't. Company lied to researchers for 2+ years.

Full breakdown: bobdahacker.com/blog/lovense...

#cybersecurity #infosec #bugbounty #privacy

What's qDot Up To This Week? (2025-07-28 Edition) | qDot Get more from qDot on Patreon

Patreon and affiliate links are the only income the project receives at this point, so every bit helps!

If you're curious what updates look like, I just posted a new one open to everyone!

www.patreon.com/posts/whats-...

Get more from qDot on Patreon creating buttplug.io

Want to support @buttplug.io, as well as get detailed updates... I'm trying for weekly but at least once a month?

Join my patreon!

Tiers start from $1/month, $5/month gets your name on things I release, all the way to $500/month in case you really like giving me money.

patreon.com/qdot

ON TRACKS www.syncereai.com

Support coming soon to @buttplug.io

Yeah I'm not sure how sold I am on it. The actual constructed form factor looks *huge*, which, I mean, if they're using a hefty transducer to get hitachi-like rumble, could be interesting, but it comes off visually as being awkward/weighty.

Library support coming soon

That said, if you actually want to build *forms*, that is... not going to be very ergonomic since without javascript you'll require a button press for any update, and there's no way to receive events.

Yup, url-encoded form data has also been mentioned!

This is the kind of enforced chastity I'm here for.

lol spotted

Hmm form encoding is an interesting idea yeah. Will have to see what that looks like.

Yup that’s what I’m aiming for. The json pushed around should be part of (or very close to) our message spec, which already has serde impls.

I mean this is also my "learn axum" project so a bit of overengineering can't hurt :)

I'm expecting there's not really a situation where there should ever be both a body with anything in it AND a query param.

Yup, planning to put out an OpenAPI doc once I get things nailed down, only issue there is this uses SSE for event streams, which is hard to communicate through that if I understand correctly?

lol thanks totally forgot to put the query prefix in for that.

I don't think the precedence rules would be too bad? If you provide both params AND a body, it's an error, the end.

from masto: please-please-please pass parameters as url parameters PUT /devices/1/features/1?vibration=0.5&position=3&stuff=42 Query parameters are much easier to work with than building huuuge url (and memorizing the order along the way)

Ah, I think we have winner here. URLs with either bodies *or* query params!

I should point out: the goal here is not just ideological purity, it is SHITPOST ACCELERATION.

We need people to be able to go from zero to vibration for whatever stupid reason they came up with as quickly as possible. But there's two camps : bash script + curl, or actually knows how to use APIs.

who needs llms to hallucinate apis when you can just have real people hallucinate them for you :3

lol except we're all json already 'cause of bad choices made in 2017.

So you'd either be able to do

[url]/devices/1/features/1/outputs/vibrate/

with a json body for the value, or just

[url]/devices/1/features/1/outputs/vibrate/0.5

Which kinda violates formal rest but also means full control via URL formation alone.