Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Buttplug: An open-source software suite for teledildonics

buttplug.io

Post reply on HN
Print view View original

171–180 of 265 posts

Re: Buttplug: An open-source software suite for teledildonics

#171

Post by qdot76367 »

throwaway56936 wrote: post #156
qdot76367 wrote: post #40

Hi! Buttplug Project Lead here! AMA!

Python support seems to be really lacking on your project. Why is that, lack of interest?

There's lots of interest in support for many languages. It's more that the codebase is 99% one developer (me), and there was a ton of fragmentation early on that I'm still working to clean up, that both makes it hard to implement new systems as well as hard for others to contribute. We're getting there.

I'm hoping to stop cranking out code and actually write the developers guide soon, which I think will help immensely.

Re: Buttplug: An open-source software suite for teledildonics

#172

Post by qdot76367 »

pacamara619 wrote: post #152
qdot76367 wrote: post #40

Hi! Buttplug Project Lead here! AMA!

Is there a list of supported devices I might have missed in my extensive 10 second search?

There's a few lists around the front page of our website, but the most comprehensive is:

https://iostindex.com/?filter0ButtplugSupport=3

Re: Buttplug: An open-source software suite for teledildonics

#173

Post by qdot76367 »

FeepingCreature wrote: post #155
the8472 wrote: post #125

Earlier quoted context omitted.

perhaps the audio port (6.35mm) providing a data channel?

That is correct. (Though usually 3.5mm.)

The only places we usually see RS-232 (either swing or TTL) over TRS is estim, funny enough.

Re: Buttplug: An open-source software suite for teledildonics

#175

Post by justapassenger »

qdot76367 wrote: post #105
Thomas_Lord wrote: post #93

Earlier quoted context omitted.

I have one more line of questions. I have, um, observed that "cam" sex workers use teledildonics as a kind of "proof of life". The idea is that paying customers send signals to a sex toy in use by the performer, whose reaction reassures the customer that he is paying for a live show. It affords a way of (apparently) "doing stuff" to the performer in spite of the virtualized nature of the show. Two part question: 1. A…

1. This is a topic that actually, seriously comes up often on cam model forums, and verification of authenticity is, to me, something that is just completely fucked in terms of even being an idea. Do these same customers get angry when they find out the movie they just paid to see was fiction? 2. Are you familiar with findom? Cause that's like, just straight up what findom is. Literally unbalanced trade of capital as…

1. If you buy a ticket to a live theatre show you don't expect to see a movie.

Re: Buttplug: An open-source software suite for teledildonics

#176

Post by somestag »

qdot76367 wrote: post #105
Thomas_Lord wrote: post #93

Earlier quoted context omitted.

I have one more line of questions. I have, um, observed that "cam" sex workers use teledildonics as a kind of "proof of life". The idea is that paying customers send signals to a sex toy in use by the performer, whose reaction reassures the customer that he is paying for a live show. It affords a way of (apparently) "doing stuff" to the performer in spite of the virtualized nature of the show. Two part question: 1. A…

1. This is a topic that actually, seriously comes up often on cam model forums, and verification of authenticity is, to me, something that is just completely fucked in terms of even being an idea. Do these same customers get angry when they find out the movie they just paid to see was fiction? 2. Are you familiar with findom? Cause that's like, just straight up what findom is. Literally unbalanced trade of capital as…

> verification of authenticity is, to me, something that is just completely fucked in terms of even being an idea. Do these same customers get angry when they find out the movie they just paid to see was fiction?

I mean, I think they would if they were told it was a live broadcast.

Of all the fetishes out there, I think wanting to view a person in real-time is one of the more easily understandable ones. I am positive that there are plenty of people out there who prefer watching a live cam over uploaded VODs, even if they never actually interact with the model.

I'm sure that cam models are exceptionally concerned about privacy for very good reasons, and I don't think anyone should be obligated to provide live verification if they don't want to. But it's not like it's an irrational request.

Re: Buttplug: An open-source software suite for teledildonics

#177

Post by Thomas_Lord »

andrepd wrote: post #135
qdot76367 wrote: post #105

Earlier quoted context omitted.

1. This is a topic that actually, seriously comes up often on cam model forums, and verification of authenticity is, to me, something that is just completely fucked in terms of even being an idea. Do these same customers get angry when they find out the movie they just paid to see was fiction? 2. Are you familiar with findom? Cause that's like, just straight up what findom is. Literally unbalanced trade of capital as…

Not to be confused with Commodity Fetishism? :p

How is this not an example of commodity fetishism?

Re: Buttplug: An open-source software suite for teledildonics

#178

Post by smichel17 »

qdot76367 wrote: post #83
Endlessly wrote: post #70

Earlier quoted context omitted.

Is there a public roadmap for the project? What aspects of the project currently have the most traction? Are there any plans to remove any existing parts of the project?

There have been a few (tried Trello and ZenHub), and they've all turned into a mess, so I recently hit the reset button again and am just trying a github project now: https://github.com/orgs/buttplugio/projects/1 tl;dr - Right now I'm trying to standardize our logic on Rust (I'm also the ex-device interfaces lead on firefox at Mozilla, so I love some rust :) ), then extend back out to other languages and platforms th…

> There have been a few (tried Trello and ZenHub), and they've all turned into a mess, so I recently hit the reset button again and am just trying a github project now

In my experience, this is mainly caused by planning in too much detail, too far ahead. And then your plans change and it's a bunch of cl noise you have to clean up or live with.

The only system I've stuck with for my FLO projects is the following:

- One tag (or milestone) named "someday/maybe". This is for things that are reasonable to do (you'd accept patches), but not worth the time/effort for you to implement personally. It exists so you can filter them out without closing. - One milestone called "next release". Only add issues to this milestone when you've competed them. Note: don't close these issues yet; keeping them open results in more visibility and fewer duplicate bug reports.

When it's time to do a release, rename the "next release" milestone to the version of the release (ex: v2.4.1), close all the associated issues (making sure they're in the changelog as you go), and replace it with a fresh "next release" milestone.

---

In the past I also had a "planned" milestone, but it's redundant with someday/maybe; anything open and not assigned to a milestone is planned.

Red Moon has the same order of magnitude of open issues as Buttplug, and not much of a community.

- If there were a larger community, I'd probably write a high-level roadmap, describing my vision and areas where it currently falls short.

- If there were other contributors or significantly more open issues, I'd add a "high priority" tag, limited to ~10 issues at a time, so there's a way to engage with less noise.

Re: Buttplug: An open-source software suite for teledildonics

#179

Post by frob »

DonHopkins wrote: post #124
qdot76367 wrote: post #106

Earlier quoted context omitted.

Hi Don. :)

Hi Kyle: I did know the answer but I just had to ask! ;) Come drop in on the epic Emacs -vs- VI battle going on in the Bill Joy thread. VI can't hold a candle to Emacs when it comes to teledildonics. You testimony might be able to convince a few lost souls to cross over. Emacs is ALWAYS in insert mode. The way you insightfully psychoanalyzed the personalities of programmers of different languages in your deldo demo s…

> Emacs is ALWAYS in insert mode.

You, sir, have won the internet today.

Post reply on HN