Opened 4 years ago

Last modified 22 months ago

#1462 assigned enhancement

I2P-Bote: option to fake a timezone when checking emails

Reported by: rfree Owned by: str4d
Priority: minor Milestone: undecided
Component: apps/plugins Version: 0.9.17
Keywords: I2P-Bote privacy Cc:
Parent Tickets:

Description

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)

Subtickets (add)

Change History (4)

comment:1 Changed 4 years ago by str4d

  • Type changed from defect to enhancement

comment:2 Changed 4 years ago by user

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

comment:3 Changed 2 years ago by zzz

  • Owner set to str4d
  • Status changed from new to assigned

comment:4 Changed 22 months ago by str4d

Migrated to https://github.com/i2p/i2p.i2p-bote/issues - I will close these tickets as things are resolved rather than right now, but please make future comments on GitHub?.

Note: See TracTickets for help on using tickets.