Option to fake a timezone when checking emails (Trac #1462)

[str4d]

Add options [ ] fake random timezone (can delay actions like message check or send for up to 1 day)

on ID creation set ID.timezone choose a random timezone, based on amount of darknet users in given timezone, including at least: all USA time zones separately, USA Eastern, USA Pacific, .... , Timezones for Europea, Timezones for Russia at least 10 timezones, with weighted probability correlating to say number of tor users or something.

Now look at ID.nextrun scheduled in previous points. Convert it to a day, in the ID.timezone.

If (ID.behaviour == type1) then start = hour 8:00 of that day // wake up end = hour 23:00 of that day // go to sleep

If ID.nextrun < start, then ID.nextrun = start; // wait until user "wakes up" if ID.nextrun > end, then change to next day, and run algorightm again // user sleeps already

if time was changed as above, then add random(0,T*0.1) + randomGauss(0.5,1.5)

(Future idea: take into account: other pattern (only in morning and evening, not "in work"), and randomly based on ID.skipwork chance (e.g. 1%) use other behaviour)

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)

Migrated from https://trac.i2p2.de/ticket/1462

{
    "status": "assigned", 
    "changetime": "2017-01-15T15:26:53", 
    "description": "Add options \n[ ] fake random timezone (can delay actions like message check or send for up to 1 day)\n\non ID creation set ID.timezone \nchoose a random timezone, based on amount of darknet users in given timezone, including at least:\nall USA time zones separately, USA Eastern, USA Pacific, .... , Timezones for Europea, Timezones for Russia \nat least 10 timezones, with weighted probability correlating to say number of tor users or something.\n\nNow look at ID.nextrun scheduled in previous points.\nConvert it to a day, in the ID.timezone.\n\nIf (ID.behaviour == type1) then\nstart = hour 8:00 of that day // wake up\nend = hour 23:00 of that day // go to sleep\n\nIf ID.nextrun < start, then ID.nextrun = start; // wait until user \"wakes up\"\nif ID.nextrun > end, then change to next day, and run algorightm again // user sleeps already\n\nif time was changed as above, then add random(0,T*0.1) + randomGauss(0.5,1.5)\n\n(Future idea: take into account: other pattern (only in morning and evening, not \"in work\"),\nand randomly based on ID.skipwork chance (e.g. 1%) use other behaviour)\n\nMake 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)", 
    "reporter": "rfree", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1484494013509852", 
    "component": "apps/plugins", 
    "summary": "I2P-Bote: option to fake a timezone when checking emails", 
    "priority": "minor", 
    "keywords": "I2P-Bote privacy", 
    "version": "0.9.17", 
    "parents": "", 
    "time": "2015-02-05T04:40:33", 
    "milestone": "undecided", 
    "owner": "str4d", 
    "type": "enhancement"
}

[str4d]

Trac update at 20150205T04:44:15: str4d changed type from "defect" to "enhancement"

[str4d]

Trac update at 20150216T20:34:27: user commented:

don't take sharp start and end times, but gauß them

[str4d]

Trac update at 20170115T15:26:53:

• zzz changed owner from "" to "str4d"
• zzz changed status from "new" to "assigned"