Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - DrDave

Pages: [1] 2
1
ChastiKey Chat / Re: Suggestion: Time limit for variable locks
« on: June 03, 2019, 05:08:19 AM »
I second the motion.
It can act as a safety valve.

2
Test of my signature.

3
General Chat / Re: Strong Belt from China ?
« on: December 31, 2018, 04:25:32 AM »
Ideas welcome, ideally one thats affordable, I do already have a CS-100 from Germany but looking for something else for the meantime.

Hope to get to know you all soon.

Gregg.
This is very close to the one I am wearing now.  The model I am wearing is no longer available.

I did have to make some small modifications.  The price was too good to miss.

https://www.wish.com/m/c/59ae790cc13e1449c265b288

4
ChastiKey Chat / Re: Any chance of help?
« on: December 24, 2018, 02:01:34 AM »
How many digits are in your combination?
A 4 digit combination has 10000 possibilities.  At 3 seconds a try it would take 30000 seconds. That's 8 and a third hours.  But you might catch the combination much sooner.  Consider taking an hour or two trying some combinations.

5
ChastiKey Chat / Re: Release probability histogram
« on: December 05, 2018, 03:56:17 AM »
A proposed sequence of breakpoints for a histogram.   The breakpoints are on a logarithmic scale with some adjustments to bend to customary time measurments.

15   minutes
30   minutes
1   hour
2   hours
4   hours
8   hours
16   hours
1   day
36   hours
2   days
3   days
4   days
7   days
10   days
2   weeks
3   weeks
4   weeks
6   weeks
8   weeks
10   weeks
1   quarter
18   weeks
2   quarters
3   quarters
1   year
18   months
2   years
3   years
4   years
Over

If you feel this is too many...
A year is likely an upper limit for most folks. So the last few could be removed.
If you still feel this is too many you can remove some of the odd breakpoints like 18 weeks.

I picture the values displayed as percent chosen.  If you use a start stop button it could be updated on the screen every few seconds.  Showing the percentages would be enough but drawing bars too would be nice.

Thank you

P. S.  Another way of stopping the calculations would be to stop whenever a simulation exceeded a user given value.  He would note in his profile that he would not use a lock that could be locked over xxx months.

6
ChastiKey Chat / Re: Release probability histogram
« on: December 05, 2018, 03:37:57 AM »
Consider making it start with a touch of a button and continue until another button is touched.  That way the user can let it run as long as he needs and not miss a rare event.  Ex all the reset cards chosen before a bunch of doubles.

7
General Chat / Re: Server backups
« on: December 03, 2018, 09:11:10 PM »
Suppose a crash made your 4 digit code dusappear....
At 3 seconds per try trying all possible combinations would take 30,000 seconds that's 8 and a third hours.  So it would not kill you if the whole system were to disappear.  Many of the locked, if the started right now could get out sooner without the combination reveal.  The system is a way to keep the honest honest.

8
General Chat / Re: chastity, TENS unit
« on: December 03, 2018, 08:59:12 PM »
Are you looking for something like the Dream Lover?  I find it overpriced.  Especially since it is difficult to know just how well it works.

If you are just looking at attaching a TENS there should not be an issue save for the condition of the pads and the two apart.  One of the problems with TENS is getting a good contact area.  If the pad comes loose so that it touches at a point or a tiny area all of the current that should have gone through to whole area just holes through that one point.  So you can get an unexpected sting. 

Another problem with keeping the pads on in that area for a long time is the inconsistent moisture.  Sweat and other fluids under a pad can greatly change the electrical resistance.   So an old setting for your TENS may be too high or low to get a predictable response.   Any time you turn it on start from zero and turn it up slowly.

I can take a go at your questions but I'm not an expert.  I am sure there are many web sites dealing with the use of a TENS device.  If you can't find one contact your doctor or the device provider. 

9
General Chat / Re: Miss and Miss run a lock
« on: December 03, 2018, 02:53:24 AM »
I see one fault.  If you use 2 digits from on and 2 from the other, once you get the first two, the lock is opened with just 100 attempts.

You could solve this by adding the two 4 digit numbers together and ignoring the 5 digit if any.  Or you could multiply the two and use the middle 4 digits.   This way you need both 4 digit codes to get any and all of the digits for the lock.

This also makes it a little harder to remember.

10
General Chat / Re: Here I am!
« on: December 03, 2018, 02:34:31 AM »
... and give me tasks to keep my mind off of it.
At 26 you won't be keeping your mind off the frustration for very long.  The task performance is likely to stir up your emotions all the more. 

There are at least several keyholder finding sites on the internet.  Many / most of them are holding for pay and not likely to give the personal attention you desire.  But, you won't know unless you try.  If you fine just what you are looking for please do tell us about it, her. Does she have a sister?

11
General Chat / Re: CS700
« on: December 02, 2018, 12:18:47 PM »
:) :) :)

Finally he arrived today my CS 700 took a while but now i am in business.

Gonna hunt for a keyholder M/F.
My advice is to wear your device with a key available until you get used to it.  There will likely be some adjustments to be made.  If not to the device then to your body and or your habits.  Remove it once in a while to check for any skin irritation.   Remedy any all ailments before committing a long term stay.

Be careful.  Stay safe.

12
General Chat / Re: Enhancing chastity with hypnosis
« on: December 02, 2018, 12:00:44 PM »
So, I commissioned a hypnodomme to create a custom file for chastity wearers. She was Mistress Elena (or ESuccubus), who crafted a great file from my basic outline. She stopped hosting the file because she was annoyed by subs looking for a keyholder, but she published the file to the internet without restriction.
She still is producing Hypnotic tracks.  I am one of many backers via patrion.  I recommend joining.  I would post a URL, but I am unsure if that is allowed here. 

If you just want a taste of her work, she has many free downloads at her eSuccubus site.  They are well worth a listen.

13
ChastiKey Chat / The 24 hour (maybe others) draw gap being reduced
« on: December 02, 2018, 01:18:07 AM »
If a user wants to draw a card each evening and not have them cumulative there will always be time of day drift.  Even if they tap the buttons as quickly as they can, the next day will still be later.   

I'd like to see it so we can use a non cumulative lock without being penalized for just a few minutes of tardiness.

Solution 1
This only fixes the drift for the 24 hour wait.
Provide a 23 hour wait.  If misused he could drift the time of day slowly earlier in the day but drifting more than 16 hours (back to rising from a nights sleep) would be difficult.  Changing the 24 to 23 would be an option.

Solution 2
Address drift for all wait times.
Allow a grace period of perhaps 5% to allow a draw before a little early but have the next wait begin when the current time would have ended.  This way the time of day drift would happen only if the user was actually late.  There would be no drift in the shorter direction.

The grace period for a 15 minute wait would be just 45 seconds.

Solution 3
Start the next wait at the time of the ending of the last wait unless the time is more that 5% of the wait time later than the last end time.  This may be the easiest to implement, not show an odd countdown, and still solve the drift issue for all wait times.

Psudocode for setting the next timer. 
Given
  WaitTime == The gap time
  EndTime == Time the last timer ended
  NextTime == Time the next timer should end
  Now == The current time
At the time the current card is drawn.
Current method
NextTime = Now + WaitTime
Proposed method
If Now > EndTime + WaitTime * 0.05 then
   NextTime = Now + WaitTime
Else
    NextTime = EndTime + WaitTime
EndIf



14
ChastiKey Chat / Release probability histogram
« on: December 02, 2018, 12:30:35 AM »
It would be very useful to be able to see a histogram of the performance of a lock.  I started to contemplate the math that would be used to display a histogram of the possible outcomes.  The trouble is accounting for the double and reset cards.  If we the community could work out the math could a histogram be presented for a lock on demand.  Knowing the major percentiles would be particularly helpful.

Short of that, if these phones have the computing power, a more brutrforce method could be used.  A routine would load a lock and randomly pick cards in the background keeping track of the time starting when the user presses a "begin simulation" button.  A field would bu updated with the count of lock lifetimes completed.   When the user sees that a sufficient number of simulations have been generated he would press an "end simulation" button.  Then the statistics for the simulations would be displayed. 

The statistics that I think would be the most useful would be the number of draws at the 10th 25th 50th 75th 90th 95th 99th and the 100th(the maximum) percentile points.

An alternative would be a simple histogram showing the time ranges in weeks from 0 to 1, 1 to 2, and so on up to 5 to 6, then 6 to 9, 9 to 13 (that's a calendar quarter), then 13 to 26, 26 to 39, 39 to 52(a year), and finally over 52 weeks).

I do not know the language used for this app.  I would be interested in knowing, learning, and then perhaps contributing to this effort.

15
ChastiKey Chat / Hard limit duration
« on: December 02, 2018, 12:05:15 AM »
 I recall a request to add a date time for eventual release.  The could be used to limit a lock so that the user could be unlocked for a future known appointment.

I'd like the option to have a hard limit lock duration.  The default duration would be stored in the user profile.  Then the used duration could be altered at lock creation time.  Key holders, bots and humans, would always respect this hard limit.  The user could alter his default hard limit as his experience accumulates.

As I was composing this I thought if another related feature, a duration soft limit.  This could be used by both bot a human keyholder.  Nice keyholders would release near the soft limit.  Nasty keyholders would release closer to the hard limit.

Pages: [1] 2