Proposal - Better Defaults and UX

[elibroftw]

First of all, great job to everyone who decided to build Lokinet and Session. But for adoption, Lokinet should work out of the box. Please do not take the following as commands, they are mere suggestions that would benefit currents users and most importantly non technical users. Also I might be ignorant so if I say something wrong about the software, that just means that the feature was not communicated clearly, not that there is no problem!

• When I first used it, I had the exit node blank, and the flip off. I pressed the power button and my IP was still exposed.
• Privacy software should not require any tinkering to offer an acceptable level of privacy!
• UX; The cursor should be a pointer when hovering over the power button
• UX: The tooltip should inform the user what happens when the UI element is clicked. Not what the element's current state means. That should be obvious or at least a status label/text. I don't think it would hurt if there was a status message to tell the user if they are connected to Lokinet. This would also accommodate color-blind users.
• Default 1: the default exit node address should be exit.loki. Users that just heard about Loki and downloaded it to access a website should not end up compromised because they were not educated in how to use the software!
• Default 2: the flip should be enabled by default. It's super unclear what it's purpose is actually. In what cases do users not require the exit to be enabled?
• UI not responsive. The UI is unresposive to clicks at times even after being clicked. When I enable the exit flip without being connected, the slider slides but the text is still "ENABLE EXIT"
  
• Keyboard shortcuts: For some reason, I can't use PrtSc when I have the window active.

Again thanks for this wonderful software. If I decide to launch a website, I will also launch it on TOR and Loki. If Loki is the jackpot it really looks like, it is heavily underutilized and unheard of!

[majestrate]

we are in the process of rewriting the gui entirely. This issue looks like it belongs to the old gui that we are deprecating as the screenshots seem to be of the old qt one.