[orbot roadmap] I would add:
auditing of and control over network usage and power usage I try to run very little on my devices, and notice when there are violations of the "don't keep awake a lot" rule. I am not saying orbot is at fault here, but in general this seems to be a tricky and pervasive class of bugs, so I expect trouble. I haven't dug into this enough to actually have a complaint, but I'd like to see some improved self-auditing of how much network is used, and docs about how orbot decides to create circuits and when it tears them down (based on usage). I would hope that after some time with no client use, it goes into a sort of background sleep mode where it uses zero resources, or at least that should be default. (I realize there is a case to burn more resources to have circuits ready.) Maybe this all works. But a big complaint of mine about the android world (or perhaps the mobile world) is that documentation and specs aren't necessary. Particularly for privacy apps, I think it's necesary to have a specification of what the app will do, so that it can be audited against that specification. I can't find any docs or specs from: https://guardianproject.info/apps/orbot
signature.asc
Description: PGP signature
_______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
