Changes between Initial Version and Version 2 of Ticket #1450


Ignore:
Timestamp:
Feb 5, 2015 4:53:00 AM (4 years ago)
Author:
str4d
Comment:

Great ideas, but too many in one ticket, and a duplicate. I have moved your Part B comment to #1360, and created #1462 for your third idea.

In future, please open separate tickets for separate ideas. If you have an idea that has several sub-ideas, please create a parent ticket and then make subtickets for each sub-idea.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1450

    • Property Parent Tickets changed from to 1359
    • Property Type changed from defect to enhancement
    • Property Summary changed from i2pbote delay: per ID and pre message [0.02 BTC] to i2pbote delay: per-identity and per-message [0.01 BTC]
  • Ticket #1450 – Description

    initial v2  
    2323Security: delay at each hop: [x] use default for selected sender,
    2424... or deselect above checkbox and select value here: min [...] max [...] minutes
    25 
    26 --------------------------------------------------------------------------------------
    27 
    28 PART B, additional 0.01 BTC:
    29 
    30 
    31 ALSO, few details about delay of "cronjobs" - especially the "check email" action:
    32 For each account, where T is the configured time of action, e.g. 10 minutes for "check email each 10 minutes":
    33 and L option:
    34 Sometimes pretend to be offline for up to .... hours to make others confused about when your computer is online.
    35 
    36 1) At start, job should delay random(T*0 to T*2)
    37 2) After running the check, job should schedule next run, to be randomly between time from now
    38   sleeptime = random(T*0.5 to T*1.5)
    39   if random(0..100) is < 30 then sleeptime += randomGauss(0 to L/5)
    40   if random(0..100) is < 10 then sleeptime += randomGauss(0 to L)
    41 
    42 choose the scheduled time: ID.nextrun = now() + sleeptime
    43 
    44 
    45 
    46 
    47 3)
    48 OTHER IDEA (for future)
    49 
    50 Add options
    51 [ ] fake random timezone (can delay actions like message check or send for up to 1 day)
    52 
    53 on ID creation set ID.timezone
    54 choose a random timezone, based on amount of darknet users in given timezone, including at least:
    55 all USA time zones separately, USA Eastern, USA Pacific, .... , Timezones for Europea, Timezones for Russia
    56 at least 10 timezones, with weighted probability correlating to say number of tor users or something.
    57 
    58 Now look at ID.nextrun scheduled in previous points.
    59 Convert it to a day, in the ID.timezone.
    60 
    61 If (ID.behaviour == type1) then
    62 start = hour 8:00 of that day // wake up
    63 end = hour 23:00 of that day // go to sleep
    64 
    65 If ID.nextrun < start, then ID.nextrun = start; // wait until user "wakes up"
    66 if ID.nextrun > end, then change to next day, and run algorightm again // user sleeps already
    67 
    68 if time was changed as above, then add random(0,T*0.1) + randomGauss(0.5,1.5)
    69 
    70 (Future idea: take into account: other pattern (only in morning and evening, not "in work"),
    71 and randomly based on ID.skipwork chance (e.g. 1%) use other behaviour)
    72 
    73 Make above scheduling be used for checking messages, but also to sending messages (otherwise they are placed in a queue, with a checkbox to bypass fake timezone on message composing)
    74 
    75 
    76 
    77 
    78 
    79 
    80