John Brooks

> Yes please do. I would really like to use your software in Whonix without making any security tradeoffs. Allowing this is a usability tradeoff. If we follow my theory...

> No, I am not suggesting you tailor your entire program just for our usecase. In onionshare its implemented as a option flag that makes it behave in a different...

> Tor-over-tor is discouraged by upstream because of unclear implications for a user's security. Correction: unclear implications for a user's anonymity. Tor-over-tor is discouraged by that upstream; control port access...

> Its a trac ticket I read quite recently. It is going to happen not really hear-say on my part. Its not going to last as a workaround no matter...

Tor 0.2.7.x should be adding a control port API for publishing hidden services without using the filesystem. With that and the control port filter, it should become possible for Ricochet...

Thanks for the followup! See #512 for some thoughts on those two requests. If you have strong feelings about where those options should be configured, feel free to mention it...

Here's some quick thoughts in case somebody wants to take this on (please do!): Ricochet's UI is a mix of QtQuickControls and custom elements, like the message bubbles. Anywhere in...

The distinguishers I would've been referring to are: 1. Hidden services are relatively rare, and build a very unique pattern of circuits 2. Ricochet clients connect to hidden services in...

Could you help write one? :)

Hmm. My gut feeling is that it's not a high priority, but also not particularly hard to implement. Personally, I'm very rarely interested in finding contacts that aren't online, and...