Bug #15830

Use a username that makes more sense to our users

Added by sajolida 2018-08-21 14:31:31 . Updated 2020-04-01 21:57:14 .

Status:
Confirmed
Priority:
Normal
Assignee:
sajolida
Category:
Target version:
Start date:
2018-08-21
Due date:
% Done:

0%

Feature Branch:
Type of work:
Discuss
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Right now we use “amnesia” which dates back from … uhhh… and probably doesn’t make much sense for our users. See for example Feature #15571. It’s also made visible in the screen locker.

Maybe “user”, as suggested in Feature #5655 would make sense. Maybe “Tails”. Maybe something else.

I want to be careful when following up on Feature #5655 that the privacy benefit that we get from Feature #5655 is not undermined by a worse usability for our users. Especially seeing that the user bases of the other distributions that could follow on Feature #5655 are orders of magnitude smaller than the Tails user base.

Subtasks

Related issues

Related to Tails - Feature #5655: Share username and hostname amongst all anonymity distributions Confirmed 2016-03-17
Related to Tails - Feature #9554: Explain how to set an administration password instead of asking for one when none is set Confirmed 2015-06-10
Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements In Progress 2018-08-31
Blocks Tails - Feature #17580: Core work 2020Q3 → 2020Q4: User experience Confirmed

History

#1 Updated by sajolida 2018-08-21 14:34:41

  • related to Feature #5655: Share username and hostname amongst all anonymity distributions added

#2 Updated by sajolida 2018-08-21 14:37:19

  • related to Feature #9554: Explain how to set an administration password instead of asking for one when none is set added

#3 Updated by letthemeatpie 2018-09-11 17:29:29

Why not simply, ‘linux’?

#4 Updated by sajolida 2019-01-22 19:56:00

  • related to Feature #14544: Spend software developer time on smallish UX improvements added

#5 Updated by sajolida 2019-01-23 12:49:42

  • Assignee set to sajolida
  • Target version set to Tails_3.13

Next step is to clarify the scope: in which places users are confronted with this name and might be problematic.

#6 Updated by Anonymous 2019-01-23 16:47:04

  • Subject changed from User a username that makes more sense to our users to Use a username that makes more sense to our users

#7 Updated by sajolida 2019-03-18 11:30:55

  • Target version changed from Tails_3.13 to Tails_3.14

#8 Updated by sajolida 2019-05-03 12:08:04

  • blocks Feature #16080: Core work 2018Q4 → 2019Q2: User experience added

#9 Updated by CyrilBrulebois 2019-05-23 21:23:27

  • Target version changed from Tails_3.14 to Tails_3.15

#10 Updated by sajolida 2019-06-06 18:53:00

  • blocked by deleted (Feature #16080: Core work 2018Q4 → 2019Q2: User experience)

#11 Updated by sajolida 2019-06-06 18:54:15

  • blocks Feature #16688: Core work 2019Q3 → 2019Q4: User experience added

#12 Updated by sajolida 2019-06-06 18:56:32

  • Target version changed from Tails_3.15 to Tails_3.16

#13 Updated by sajolida 2019-09-03 09:35:33

  • Target version changed from Tails_3.16 to Tails_3.17

#14 Updated by intrigeri 2019-09-12 14:25:20

  • Target version changed from Tails_3.17 to Tails_4.0

#15 Updated by sajolida 2019-09-30 18:38:18

  • Target version changed from Tails_4.0 to Tails_4.1

#16 Updated by CyrilBrulebois 2019-12-04 11:31:17

  • Target version changed from Tails_4.1 to Tails_4.2

#17 Updated by sajolida 2020-01-06 14:37:52

  • Target version deleted (Tails_4.2)

#18 Updated by sajolida 2020-01-08 14:44:52

  • blocks Feature #17246: Core work 2020Q1 → 2020Q2: User experience added

#19 Updated by sajolida 2020-01-08 14:45:14

  • blocked by deleted (Feature #16688: Core work 2019Q3 → 2019Q4: User experience)

#20 Updated by sajolida 2020-04-01 21:59:41

  • blocked by deleted (Feature #17246: Core work 2020Q1 → 2020Q2: User experience)

#21 Updated by sajolida 2020-04-01 21:59:45

  • blocks Feature #17580: Core work 2020Q3 → 2020Q4: User experience added