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.

Topics - DrDave

Pages: [1]
ChastiKey Chat / New Feature Request- Task Cards
« on: November 20, 2019, 03:54:19 AM »
I'd like to see a set of cards that would be numbered.  At the start the user would define a number of tasks that could be assigned.  These would be assigned to numbers. 

For example one task could be assigned to 1, another task to 2 through 4, yet another to 5.  Then the user would request 5 task cards. 

When a task card is drawn the number if the task card is revealed.   The user is obligated to perform the task. 

Task examples: Go commando for 5 days, no soft drinks until you draw a green card, be naked at home when you expect more than 10 minutes of privacy for the next 5 days, limit nonprofessional internet time to 30 minutes per day until you draw a green card, purchase $20 of sex toys before a green card is drawn; if a green card is drawn before the purchase the amount doubles...

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. 
  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
    NextTime = EndTime + WaitTime

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.

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.

ChastiKey Chat / Delayed Start of a lock idea
« on: December 01, 2018, 10:44:24 PM »
I wish to delay the start of the lock to a particular time.  It may not be known in advance.  For example when frustration builds to a particular level.

I still want to use cumulative card picking so I won't have to schedule each draw.  So can you make it so the very first draw NOT be cumulative?  This could be an option or just have it as the norm.

Pages: [1]
SMF spam blocked by CleanTalk