Hey,
>>>> Spencer:
>>>> After reviewing Tails 1.4, the current blueprint, and the most
>>>> recent UI
>>>> screens, the unlock persistence process seems to be:
>>>>
>>>> 1) Enter passphrase
>>>> 2) Start Tails
>>>>
>>>> If this is the case, and we have no intention of changing it for
>>>> 2.0,
>>>> have we decided on any feedback other than, for example, what
>>>> happens if
>>>> people enter the wrong passphrase?
>>>>
>>>
>>> Sajolida:
>>> Not yet.
>>>
>>
>> Spencer:
>> Word. A "Success!" indicator might be appropriate to assist with user
>> confidence.
>>
>
> Sajolida:
> I'm definitely not against this is we find a proper way to display it
> (in terms of interaction). Just to have some mockup to discuss upon, in
> the one on the blueprint we might display a "Success" for one second
> after "Start Tails" is clicked and before we start opening the desktop
> environment.
>
Perfect thought!
>>>
>>> it felt superfluous to have a
>>> dedicated button to unlock persistence.
>>>
>>
>> I feel you. However, a click to power/unlock Persistence is equal to
>> a
>> click to enter a passphrase. The last thing I am trying to work out
>> is
>> if we can create a more harmonious relationship between the
>> Persistence
>> passphrase field and the 'Start Tails' button, possibly removing the
>> need for either of these clicks.
>>
>
> Right, another possibility that might be worth investigating would be a
> timeout to automatically check the passphrase after some time of
> inactivity in the passphrase field. In case of failure we could
> silently
> ignore it (not to annoy slow typers) and only display "wrong
> passphrase"
> after clicking on "Start Tails".
>
