Tails

#5 Updated by sajolida 2018-06-28 17:21:40

• File password-prompt.png added
• Assignee changed from sajolida to emmapeel
• QA Check set to Dev Needed

Improving SEO from external search engine will probably help with the internal search engine as well.

And also, it’s actually a mess because the password prompt as for the “amnesia password”, yet another name for the same password :(

So let’s use these queries as reference:

• “Root”
  • https://duckduckgo.com/?q=how+to+be+root+on+tails&kad=en_US&ia=videos: the one pointing to the video
  • https://duckduckgo.com/?q=tails+root+password&kad=en_US&ia=web: this one is good, saved by “Root Terminal” having “root” in its name
  • https://tails.boum.org/ikiwiki.cgi?P=root+password: this one somehow works, probably for the same reason
• “Amnesia”
  • https://duckduckgo.com/?q=tails+amnesia+password&kad=en_US&ia=web: this one is good, maybe saved by having “amnesic” in our tagline because otherwise “amnesia” is not mentioned anywhere…
  • https://tails.boum.org/ikiwiki.cgi?P=amnesia+password: this one is clearly broken

I’m thinking about the following, though it’s ugly. What about starting the page with “In Tails, an administration password (also called root password or amnesia password) […]”?

That should probably be enough to fix the queries that don’t work yet.

We should do this changes on master and test them a few weeks after merging.

I also prepared a screenshot that might help understanding the terminology mess. See attachment. We could add stuff to its alt tag as well (and add a note that the alt tab is useful for SEO because otherwise xin will rightfully propose to remove it).

#7 Updated by emmapeel 2018-06-29 10:37:01

• Assignee changed from emmapeel to sajolida

#8 Updated by sajolida 2018-06-30 17:43:10

• Assignee changed from sajolida to emmapeel

Yes, but please do it in doc/14589-additional-software directly.

#10 Updated by sajolida 2018-08-14 18:40:05

• Status changed from Confirmed to Resolved
• Assignee deleted (emmapeel)
• QA Check changed from Dev Needed to Pass
• Feature Branch set to 3e8d48209d + ecde9b5df4

Despite me literally spelling out a solution, emmapeel didn’t submit patches in time for the freeze, so I did that myself in master (so we can test the result before the release). That’s 3e8d48209d + ecde9b5df4.

#11 Updated by sajolida 2018-08-14 18:42:31

• Status changed from Resolved to In Progress

Oops, actually, I want to keep this ticket open to check the improvements in search engines in a few weeks.

Ulrike: Reassign it to me once you had a quick look. The same as Feature #15574#note-1 applies: do whatever you want with this info as a manager but don’t review this work in depth.

#12 Updated by Anonymous 2018-08-19 10:57:51

• Status changed from In Progress to Fix committed
• Assignee set to sajolida
• % Done changed from 0 to 100

Thanks! Reassigning back to you for review in a few weeks.

#13 Updated by intrigeri 2018-08-19 12:17:39

• Status changed from Fix committed to In Progress

(Otherwise this will be closed when we release 3.9, which apparently would be incorrect.)

#14 Updated by sajolida 2018-08-19 19:49:59

• Target version changed from Tails_3.9 to Tails_3.10.1

I think it’s ok to do this after 3.9 because until then I’ll be super busy…

#18 Updated by sajolida 2018-10-21 20:29:02

• Status changed from In Progress to Resolved
• QA Check deleted (Pass)

Yeah… I’m not 100% happy with the results but it definitely got improved and I’m not sure whatelse we could do → closing this ticket.