>>> intrigeri intrigeri[at]boum.org:
>>> In case there was a misunderstanding, note that '(amnesia)' is _not_
>>> part of the file name:
>>>
>>> * `~/Tor Browser files` (amnesiac)
>>> * `~/Persistent/Tor Browser files`
>>>
>> SpencerOne spencerone[at]openmailbox.org:
>> 'Amnesia', although not explicitly labeled as a directory destination,
>> and
>> 'Persistent', are not very clear labels, and I am unsure of how
>> effectively they
>> translate into other languages.
>>
> intrigeri intrigeri[at]boum.org:
> Just to clarify, nobody will see "amnesia" written anywhere.
> What users will see is "Tor Browser files", which is amnesiac since
> it's Tails and it's not on the persistent volume.
>
I know, and to your point below: "very confusing to users if we start
explicitly labeling anything as "Forgotten", since it's the default in
Tails.", It is the default that cars drive forward, yet there is a
dedicated 'D' on the shifter, in addition to the other non-default
states. Though people are only beginners once, it can still be more
clear than not, in a game theory kind of way, to see opposites
appropriately labeled as such.
However, I respect the decision to not be that explicit and, instead,
let the context and function of the OS itself communicate that the
default "storage" location contents will be wiped, i.e., forgotten.
>
> Regarding "~/Persistent": we've had it called as such, as one of our
> default persistence options forever. I guess we could rename it, but
> it's another discussion IMO (as long as the current consensus of
> reusing that directory for persistent Tor Browser downloads holds).
> I see you're proposing "Remembered" and "Permanent" later.
> Please start a new, dedicated thread about this topic :)
>
No need. Just suggestions to this thread. Besides, I am not usually in
favor of using bug trackers to design, only to address bugs or to
address issues with the implementation of particular designations, as it
can easily fragment the process and, in turn, the outcome.
So, with that said, my interest is in providing feedback/suggestions on
current bugs/tickets, allowing you all to create bugs/tickets as you see
fit, and being around to assist in closing them. However, since I spent
all of my time with mechanical engineering/material
science/sustainability/anthropology/philosophy/form development, I wont
be of much help in the coding/development capacity : ( But, since only
the last three apply in this context, I am here for all HuX needs : )
>>
>> And this is overlooking that amnesia, i.e., to
>> forget, is not what is really happening, e.g., the files are being
>> removed, i.e.,
>> deleted, as I am sure there are traces of them in some form on the
>> storage device.
>>
> What do you mean exactly? What's stored outside of the persistent
> volume is *not* written to disk. Ever. If it is, then you've found
> a pretty serious breakage of our design goals, and I'm very curious.
>
Well, given this:
* ~/Tor Browser/
* ~/Persistent/Tor Browser/
Isn't there a location for the amnesiac files? If so, they physically
exist at some point and, to fulfill the amnesiac function of the
experience, are then removed, right? In my experience, these files can
be located like deleted pictures on any portable media storage device,
though my severe lack of expert knowledge in this area might be the
cause of my misconception.
>>
>> However, with that said, we could say:
>>
>> ~/Tor Browser files/Remembered
>> ~/Tor Browser files/Forgotten
>>
> ... this would require reintroducing a dedicated persistence option
> for "~/Tor Browser files/Remembered", which sajolida and tchou
> convinced me to drop.
>
If you mean:
* ~/Tor Browser/Persistent
in addition to:
* ~/Persistent/Tor Browser/
then yes, they have argued correctly. My bad for overlooking that when
making the proposal.
>
> I've already argued earlier in this thread why I believe it would be
> very confusing to users if we start explicitly labeling anything as
> "Forgotten", since it's the default in Tails.
>
> This also applies to your other suggestions.
>
>> Though 'files' might be redundant if the context of the experience
>> establishes that
>> these directory destinations are for storing files.
>
> Interesting point. Building on top of the current state of things,
> that would give:
>
> * ~/Tor Browser/
> * ~/Persistent/Tor Browser/
>
Wordlife,
SpencerOne