Re: [Tails-dev] Screenshot clipboard can make my mistakes
Ctrl+C and Ctrl+V are standard shortcuts on pretty much every operating system and I don't think that we should diverge from this. Moakt Temporary Email: COPY: Ctrl + C Paste: Ctrl+V These are very close One 1. I make a screenshot in Keepassxc 2. I do Ctrl+V by mistake in the Tor browser. 3. I send my password to the website Two 1. I make a screenshot in my face image 2. I do Ctrl+V by mistake in the Tor browser. 3. I send my face image to the website ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. -- sajolida ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Pip is not torified by default
Stored for now in https://gitlab.tails.boum.org/tails/tails/-/issues/19320. David A. Wheeler: On Feb 1, 2024, at 5:25 AM, anonym wrote: But, as already shown above, Tails allows you to customize it extensively through the persistence feature. The Additional Software persistence feature [3] allows you to keep any package from Debian installed and up-to-date, so just install python3-pip and the other tools you like that way. [3] https://tails.net/doc/persistent_storage/additional_software/ A persistent storage feature for user installed python packages could also be designed to be a hook that adds the appropriate corresponding .local folders to the persistence.conf upon activation of the feature. It is not a documented feature any more (I think because of bugs like #19267) but you can also make any folder persistent yourself. Start Tails with an administration password, login, start a Root Terminal. This makes ~/.local persistent: echo '/home/amnesia/.local source=dot-local' \ >> /live/persistence/TailsData_unlocked/persistence.conf You can do this multiple times, so this also makes the pip cache persistent: echo '/home/amnesia/.cache/pip source=pip-cache' \ >> /live/persistence/TailsData_unlocked/persistence.conf The `source=pip-cache` part means that the data will be stored on the persistent storage in `/live/persistence/TailsData_unlocked/pip-cache`, so just make sure to never re-use the same source as any other line in that file. You must restart Tails for lines added like this to take effect. I strongly recommend *documenting* this capability (e.g., in "additional software"). There's no way this group can directly support all special needs, but documenting how people can self-help would be really valuable. A few specific examples of common cases (I'd put pip in that category) would be especially helpful. --- David A. Wheeler ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. -- sajolida ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Cron /usr/local/bin/tails-website-last-month-stats '/var/log/nginx/tails.boum.org'
Cron Daemon: Boots in January: grep: access.log.11.gz: binary file matches grep: access.log.10.gz: binary file matches 782686 That's a pretty low number. Did the unusual grep output affect the counting? -- sajolida ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Cron /usr/local/bin/tails-website-last-month-stats '/var/log/nginx/tails.boum.org'
moire: Cron Daemon: Boots in October: 830216 It's a high score, isn't it? Yes! See https://gitlab.tails.boum.org/tails/blueprints/-/wikis/stats/boot/boot.ods. - It's the highest daily average since the crash in users due to the broken upgrades from February 2021. - It makes our average for 2023 greater than our average for 2022. - It makes the curve of the last 2 years look more like the curve before February 2021. Still, October 2023 was our first month with 2 releases since October 2022 and these tend to have more "boots" because people upgrade and restart a bit more. -- sajolida Tails — https://tails.net/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] About using and privacy
abc games: While using the Tails system via flash disk and performing transactions with the Tor browser, can the ISP see that I am using the Tor browser and the Tails system? Is there a setting that needs to be done to prevent it from seeing it? https://tails.net/doc/about/warnings/tor/ -- sajolida Tails — https://tails.net/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] thanks for the hard work
Hi, Thanks a lot for the kind words! It's always good to receive some love from users after long hours behind the computer. Have a nice day! smirnoff2023--- via Tails-dev: dear tails developers, i'm emailing yaw just to let yaw know that yaw did a really great job on devevolping tails, it's nice to have it installed on a USB so i can be able to go online without being harrased by constant ads, i want to thank yaw for the hard work, because tails is the best linux OS that ive used so far. thank you. happy tails user -- sajolida Tails — https://tails.net/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Results from usability tests of the new Persistent Storage in Ecuador
Hi, In March, emmapeel traveled to Ecuador and conducted moderated in-person usability tests of the new Persistent Storage. https://gitlab.tails.boum.org/tails/tails/-/issues/18648 She recruited 4 women from feminist groups who had an interest in privacy technologies but never used Tails before. I prepared the tasks and testing image beforehand and trained her on doing usability tests, as I couldn't travel myself this time. That's why the tests were shorter and the tasks more basic. We asked them to: - Save an image to the USB stick in a way that protects it if their USB stick gets stolen. - Configure Tails to connect to a Wi-Fi network automatically. See the stepped tasks here: https://gitlab.tails.boum.org/tails/ux/-/raw/master/persistent%20storage/tasks-software-2023.odt?inline=false I already tested similar tasks in Brazil in August and in other occasions in the past. The results were very good and emmapeel did a great job on her first facilitation :) The good stuff: - We didn't find any serious usability issue in the new Persistent Storage on these basic tasks. The fact that people don't have to restart to create the enable the Persistent Storage and that their data (eg. Wi-Fi password) is stored on creation made a huge difference. We knew this already but it was great to see it live! - In the past, there was always someone forgetting forgot to unlock their Persistent Storage. This time, #15573 prevented this for P2. - Nobody had troubles connecting to the Tor network. Of course, it helped that the network had no censorship or captive portal, but also the 2 people who chose "hiding" at first quickly rolled back to "automatic". I think that #19166 helped with that. - 3 participants out of 4 hesitated because of the lack of "Save" button in the new Persistent Storage but then correctly assumed that changes were applied automatically. - Turning off features and deleting data was well understood. Congrats for !1010. We didn't test any failure mode of this, though. The bad stuff: - Saving an image from Tor Browser is still a nightmare. Nobody made it. That's #15678 and related issues. I'm worried to see that the situation hasn't improved for our users since 2018 and will push for more action on this front in 2023. - The concept of the Persistent folder, as part of the Persistent Storage, was not always super clear. All the new issues identified had to do with this: * #19642: Implement missing descriptions of PS features * #19645: Add a placeholder file in the Persistent folder * #19646: Persistent folder should not appear as an external device - We didn't test the onboarding of the Persistent Storage in the Welcome Screen (#15586) because emmapeel made people start the tasks from Tails already. I should have clarified this beforehand. For detailed results, see the rainbow table in attachment. Huge thanks to emmapeel for giving a hand on this :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing rainbow_table_persistent_storage_2023_03_Ecuador.fods Description: application/vnd.oasis.opendocument.spreadsheet-flat-xml ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [PATCH] Fix incorrect usage of "discrete"
Oh sweet! I didn't know. Thanks for improving my English. I applied your patch to our stable branch and credited you: https://gitlab.tails.boum.org/tails/tails/-/commit/3e58335ef00c88d9d0d64958fefed8e0a66f7476 Steve Dougherty via Tails-dev: This doesn't retroactively fix news posts. Via Wiktionary: discrete (comparative more discrete, superlative most discrete) 1. Separate; distinct; individual; non-continuous. a government with three discrete divisions 2. That can be perceived individually, not as connected to, or part of, something else. discreet (comparative more discreet or discreeter, superlative most discreet or discreetest) 1. Respectful of privacy or secrecy; exercising caution in order to avoid causing embarrassment; quiet; diplomatic. With a discreet gesture, she reminded him to mind his manners. John just doesn't understand that laughing at Mary all day is not very discreet. 2. Not drawing attention, anger or challenge; inconspicuous. Although cognate and identical in the Middle English period, the term has become distinct from discrete. --- config/chroot_local-includes/usr/share/tails/tca/main.ui.in | 2 +- po/tails.pot| 2 +- wiki/src/doc/anonymous_internet/tor.mdwn| 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/config/chroot_local-includes/usr/share/tails/tca/main.ui.in b/config/chroot_local-includes/usr/share/tails/tca/main.ui.in index f77be556cd..59ca2b8e5b 100644 --- a/config/chroot_local-includes/usr/share/tails/tca/main.ui.in +++ b/config/chroot_local-includes/usr/share/tails/tca/main.ui.in @@ -1498,7 +1498,7 @@ Choose this option if you already know that you need a bridge. Otherwise, Tails 12 Tails will only connect to Tor after you configured a Tor bridge. Bridges are secret Tor relays that hide that you are connecting to Tor. -Our team is doing its best to help you connect to Tor using the most discrete types of Tor bridges. +Our team is doing its best to help you connect to Tor using the most discreet types of Tor bridges. You will have to do extra configuration if you don't know any Tor bridges yet, if you connect from a public Wi-Fi network, or if you are in the Eastern Hemisphere. True diff --git a/po/tails.pot b/po/tails.pot index 82f80aaa9f..29b9a2243a 100644 --- a/po/tails.pot +++ b/po/tails.pot @@ -3000,7 +3000,7 @@ msgid "" "are secret Tor relays that hide that you are connecting to Tor.\n" "\n" "Our team is doing its best to help you connect to Tor using the most " -"discrete types of Tor bridges.\n" +"discreet types of Tor bridges.\n" "\n" "You will have to do extra configuration if you don't know any Tor bridges " "yet, if you connect from a public Wi-Fi network, or if you are in the " diff --git a/wiki/src/doc/anonymous_internet/tor.mdwn b/wiki/src/doc/anonymous_internet/tor.mdwn index a8c2e4f16d..96741a60a6 100644 --- a/wiki/src/doc/anonymous_internet/tor.mdwn +++ b/wiki/src/doc/anonymous_internet/tor.mdwn @@ -156,7 +156,7 @@ of exit nodes of the Tor network is public. -Our team is doing its best to help you connect to Tor using the most discrete +Our team is doing its best to help you connect to Tor using the most discreet types of Tor bridges. That is why, when you decide to hide that you are connecting to Tor: @@ -185,7 +185,7 @@ types of Tor bridges. That is why, when you decide to hide that you are connecti Even someone who knows your bridge cannot know what you are doing online from Tails. -- You can only use the types of bridges that our team considers discrete enough. +- You can only use the types of bridges that our team considers discreet enough. Currently in Tails, only *obfs4* bridges hide that you are using Tor. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] ping...
Keith Bierman: "...it is impossible to use ping in Tails, because ping uses the ICMP protocol while Tor can only transport TCP connections." Seems like including ping is an attractive nuisance. Since it can't work, wouldn't it be better to remove it? Or replacing it with a trivial script which explains why ping can't work? Good point! It seems easy to remove, so why not get rid of it (and a bit of FAQ): https://gitlab.tails.boum.org/tails/tails/-/issues/19579 -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: Add support for curl (does ALL_PROXY fix it?)
boyska: @boyska: Any concern about that since curl is already installed? no specific concern, but of course, this moves the needle towards making it work out of the box. All right, see you on #19448, then! https://gitlab.tails.boum.org/tails/tails/-/issues/19488 -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: Add support for curl (does ALL_PROXY fix it?)
David A. Wheeler: I've created a proposal to briefly describe how to use additional software within Tails. It includes some information on how to use curl: https://gitlab.tails.boum.org/tails/tails/-/merge_requests/1044 Thanks! I'll have a look. I had in mind investigative journalists & similar researchers with a *modest* technical background. More generally, people who gather data (and sometimes send it) from the Internet, especially those who can write simple scripts to do that. Right, I have the same people in mind and already met several of them. I wanted to try adding curl by default to see the impact on the image size but ... it seems to be installed already: https://gitlab.tails.boum.org/tails/tails/-/commit/8aa013f3b549d90609fb2a4dd7e2bd14e3439151 Maybe I missed something! That said, it doesn't work out of the box: amnesia@amnesia:~$ curl https://tails.boum.org/ curl: (7) Failed to connect to 127.0.0.1 port 9050: Connection refused I created #19488 to fix this. I'm even more convinced that we should fix that :) @david: Do you want to give it a try? @boyska: Any concern about that since curl is already installed? -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: Add support for curl (does ALL_PROXY fix it?)
David A. Wheeler: oh yeah, we all like curl. I wonder what kind of user needs curl, though. You mentioned that some packages in Debian will "just work" if curl is working. Can you name any of them? I think that would be very valuable info! Sorry, what I meant was, "I expect that some packages in Debian will "just work" if curl is working". I don't have a specific list. However, we try to add feature to Tails when they are improving something for our personas (see https://tails.boum.org/contribute/personas/ ). In this specific case, I think we don't have an example of how can curl, directly or indirectly, help our personas. It's really easy to add the configuration you propose to Tails. But it will add to our QA process: if we tell our users that they can expect curl to work fine, we'd better test it regularly! All in all, the cost is low but not negligible, while the benefit for our personas seems to be zero. So my personal opinion is that it's not worth it *until* there is a clear use case that is helped by supporting curl. Here again, I'm sorry for the huge delay in answering. I wanted to complete a bit the picture on "who the heck would use curl"? Daniel Moßbrucker used wget for his investigative journalism: https://tails.boum.org/contribute/how/user_experience/interviews/daniel In his own words: « For the research on child abuse, we used wget for most of our crawling and it's super useful to have it already installed. » « I wouldn't call myself a technology expert. I'm able to code a little bit, but for sophisticated projects like these, I still need someone with a real information security background to ask them how do certain things, which tools to use, and to check and improve my 30 lines of script. » When we did the Tails workshop at Netzwerk Recherche in October, it was really sweet to see Daniel advocate for wget as one of the really cool tools included in Tails :) There I also met other journos who have a bit of a technical profile and investigate online data in ways that could totally benefit from wget and curl. In that regard (and many others), the personas on https://tails.boum.org/contribute/personas/ are quite outdated, I think. Thinking about these more techie-journos, curl could totally makes sense in Tails. That said, I haven't really read the other emails in this thread about what it would take from a technical point of view; and it's true that everything that we had to Tails, even as small as curl, can turn into more maintenance work down the line. David: Actually, I'm curious what made you suggest adding curl to Tails. Did you had any particular use case or users in mind? That said, clearly the Tails project already expects that some users will install additional software. So I suggest modifying the documentation to provide *some* tips to users on how to deal with differences when running on Tails (in particular the network and dot files). The current documentation never mentions torsocks or any other related issues. Then you don't have to do more QA, and if later on someone raises a persona, you're a step ahead. We've had https://gitlab.tails.boum.org/tails/tails/-/issues/18013 for a while but I never gave it enough prioritize to tackle it myself. I added your suggestions there for now. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
We should start writing the monthly report for last month. Done! https://tails.boum.org/news/report_2023_01/ -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] xfce, second option graphic interface in tails?
4qu1n4...@riseup.net: Hello developers I would suggest that the group of developers add the possibility of using the xfce graphical interface to allow people who do not have good computers to have access to this technology that tails provides... The gnome and very heavy and very computational processing demand, people with weaker computers can not get access to the tails with gnome, xfce would be a great second option. See https://tails.boum.org/support/faq/#gnome We had users ask for LXDE, XFCE, MATE, KDE, and so on, but we are not going to change desktop. According to us, the main drawback of GNOME is that it requires quite a lot of resources to work properly, but it has many advantages. The GNOME Desktop is: - Well integrated, especially for new Linux users. - Very well translated and documented. - Doing relatively good regarding accessibility features. - Actively developed. - Well maintained in Debian, where it is the default desktop We invested quite some time in acquiring GNOME knowledge, and switching our desktop environment would require going through that process again. We are not proposing several desktop environments to choose from because we want to limit the amount of software included in Tails. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Privacy
jakob.brannstrom via Tails-dev: Hi there, If an adversary controls all three hops in a tor circuit. Will my traffic still be private? In theory, no. In practice, Tor and Tails makes this extremely unlikely. Your question made me realize that we haven't documented this enough in our warnings. I added a new one right now: https://tails.boum.org/doc/about/warnings/tor/#correlation -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] obfs4 not work in Iran
Trojan via Tails-dev: Hi Tails Hi Trojan, Thanks a lot for the kind words! It's always good to receive some inspiring news from users around the world after long hours behind the computer. We want to add Snowflake, and the new Tor Connection assistant will make this easier. Unfortunately, we don't have enough working capacity right now to add Snowflake to Tails right now. You can track our plans on: https://gitlab.tails.boum.org/tails/tails/-/issues/5494 But testimonials from people like you are really useful to help us prioritize our work. So please, keep telling us about how we should improve Tails for the brave people struggling in Iran. We know that we should work faster on these improvements, but it's not always possible :( In solidarity, -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] "Back Up Persistent Storage" dialogue text is misleading; here's a suggested alternative
David A. Wheeler: Hi, I have a minor nit/suggestion for Application -> System Tools -> Back Up Persistent Storage. After using it a bit, I've concluded that the *functionality* works well, but that the text of the dialogue boxes are misleading. Some of its current text suggests that it's updating the OS, not the persistent data. This misleading text might cause confusion for new users, and we don't want them confused when backing up things! Hi, These are all excellent suggestions, thanks! I didn't use or test this utility enough to realize this pretty clear confusion :( Can you check https://gitlab.tails.boum.org/tails/tails/-/merge_requests/995/diffs? -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Add pass for more ways of password managment
hag_rat via Tails-dev: By any change would y'all add pass <https://www.passwordstore.org/> Hi, We love pass and use it internally. We won't add it to Tails because we don't prioritize adding niche command line tools that advanced users than install themselves using the Additional Software feature. That's why we removed keyringer, a similar tool, some years ago: https://gitlab.tails.boum.org/tails/tails/-/issues/15291 -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Installing Tails as a Virtual Machine
nibs123 via Tails-dev: I downloaded the Tails iso in order to run Tails as a virtual machine. What version of Debian Linux does Tails currently use? Debian 11 (Bullseye) but it should work to configure your virtualization software for Debian 10: https://tails.boum.org/doc/advanced_topics/virtualization/virt-manager/ -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
This time it's me. nore...@tails.boum.org: > We should start writing the monthly report for last month. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails is hiring a Fundraising Lead
David A. Wheeler: > However, please note that Tails is probably *already* leaving money on the > table. Yes, we are leaving money on the table in many ways. The main reason right now is lack of workforce to apply to more grants or organize more crowdfunding. > The Secure Open Source Rewards pilot program "financially rewards developers > for > enhancing the security of critical open source projects that we all depend > on." > Although I can't guarantee their approval, I'm sure they would look > positively at reasonable > proposals from Tails. I think the odds are good. Yes, I've nagged this > information before :-). > > If anyone is interested, see: <https://sos.dev/> Thanks! Unfortunately, I won't have time to look more into this before the end of the year, but I created an issue to track this. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [Tails News] Tails is hiring a Fundraising Lead
Hello! Tails is looking for a Fundraising Lead to help us develop and grow our fundraising initiatives. We are looking for a gifted communicator who can tell the story of Tails to a wide variety of current and future donors. They will take the lead on all fundraising efforts from strategy through to execution, and play a key role in ensuring the financial health and sustainability of the project. This role will work closely with our core teams to connect our technical and product strategy to funding opportunities. Full job description and instructions on how to apply: https://tails.boum.org/jobs/fundraising/ Please feel free to share this with anyone you know who might be a fit! Thank you. -- Tails News https://www.autistici.org/mailman/listinfo/amnesia-news To unsubscribe, send an empty email to amnesia-news-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] thunderbird documentation to update for Tails 5
conan: > "Passwords and Keys utility" is still mentioned while it has been > replaced by Kleopatra in Tails 5. > > Documentation update seems needed. Oops! Good catch. I added it to https://gitlab.tails.boum.org/tails/tails/-/issues/18581. We're super late to update our doc, but we'll do it at some point :) > PS: I hope this is the good place to report documentation issues, if not > please let me know. Anywhere I read is a good place: tails-dev, tails-l10n, GitLab, etc. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] FYI: Opportunity for some funded security work for tails & other critical open source software / Free software
David A. Wheeler: > FYI, the "Secure Open Source (SOS) Rewards Program" <https://sos.dev/> > "financially rewards developers for enhancing the security of critical open > source projects." > Examples of such work include "Software supply chain security improvements > including hardening CI/CD pipelines and distribution infrastructure" and > so on. Hi David, Thanks for the pointer and sorry for the delay (coming back from holidays). We'll definitely look into it! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Tails report for April 2022
Tails report for April 2022 <https://tails.boum.org/news/report_2022_04/> * Disoj, our new Project Manager, started working with us. It's the first time Tails has a dedicated Project Manager and we are all very excited about this change. Disoj will help us work better and faster to accomplish our mission <https://tails.boum.org/contribute/mission/>. * We got very busy preparing Tails 5.0 <https://tails.boum.org/news/version_5.0/index.en.html>. * We upgraded all our infrastructure to Debian 11 to ensures that all our public and internal servers will continue receiving security updates timely after August. * We organized 2 online trainings <https://tails.boum.org/news/ciclo_de_autodefensa_digital_mexico/index.en.html> for people in Mexico. You can download our slides <https://tails.boum.org/contribute/how/promote/material/slides/Ciclo_Autodefensa_Digital_202204/Tails-Spanish.odp> and the structure <https://tails.boum.org/contribute/how/promote/material/slides/Ciclo_Autodefensa_Digital_202204/structure/> of the training if you want to organize Tails workshops yourself. * Tails has been started more than 783 850 times this month. This makes 25 031 boots a day on average. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
nore...@tails.boum.org: > We should start writing the monthly report for last month. > > A blueprint with the current report, who is responsible to curate it, and > a template with instructions on how to write it can be found on: > > https://gitlab.tails.boum.org/tails/blueprints/-/wikis/monthly_report/ I'll substitute anonym. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] We'll try to release Tails 5.0 (Bullseye) on May 3
intrigeri: > intrigeri (2022-04-21): >> We believe there's a good chance we manage to fix next week the >> blockers we've identified, and thus release 5.0 on May 3 (instead of >> 4.30 + 5.0~rc1). > > We've fixed all the blockers so unless something really bad happens at > the last minute, we're going to release 5.0 on May 3. Congrats! > I've updated https://tails.boum.org/contribute/calendar/ accordingly. > I've also created GitLab milestones for the 5.x releases that are > already scheduled, so you can now use them to plan your work :) Wow! The future suddenly feels wider :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [PATCH] update vm-install instructions
kwadronaut via Tails-dev: > Hi, > > see attached patch for a minor update to the documentation. Hi kwadronaut, Thanks a lot for the patch. Precisely these days, we're updating our doc to Tails 5.0 (Bullseye), so you're arriving right on time :) I applied it and fixed it a bit more with fd6773d41e. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Cron /usr/local/bin/tails-website-last-month-stats '/var/log/nginx/tails.boum.org'
Zen Fu: > sajolida writes: > >> Cron Daemon: >>> Boots in February: 717702 >> >> +2.7%! > > Hum, how so? The number i see for January is: 773496 > > Did i get it wrong? I'm looking at the number of boots per day. January has 31 days and February 28: 773 496 / 31 = 24 951 717 702 / 28 = 25 632 -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Cron /usr/local/bin/tails-website-last-month-stats '/var/log/nginx/tails.boum.org'
Cron Daemon: > Boots in February: 717702 +2.7%! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Spring cleaning our GitLab labels
intrigeri: > 2. Merge these labels: > >- "C: Installation", "C: Installation Assistant", "C: Installer" > → "C: Installation" I also thought about that this other day. So, yes! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Tails report for December 2021
Releases Tails 4.25 was released on December 2021 <https://tails.boum.org/news/version_4.25/index.en.html>. * We added a utility to make a backup of the Persistent Storage to another Tails USB stick. * We added a new entry called *Tails (External Hard Disk)* to the GRUB boot loader. Hiring a Project Manager We published a job offer for a Project Manager <https://tails.boum.org/jobs/project_manager/> and reviewed the first 50 applicants. We were very impressed by the quality of the applicants and this gives us a lot of hope for the future of the project. We selected 6 applicants that we will interview in January. We are still reviewing new applications! Please pass the word :) Automatic time synchronization We wrote a prototype to automate the synchronization of the computer's clock before connecting to the Tor network. (#18717 <https://gitlab.tails.boum.org/tails/tails/-/issues/18717>) This will help people living in Eastern Europe and Asia connect to Tor bridges from Tails. When users decide to connect to the Tor network automatically <https://tails.boum.org/doc/anonymous_internet/tor/index.en.html#automatic>, Tails will connect to Fedora's captive portal detection /without going through Tor/ to automatically correct the clock before connecting to Tor. You can read more about our security design <https://tails.boum.org/contribute/design/Tor_enforcement/#non-tor-traffic> and current implementation plans <https://gitlab.tails.boum.org/tails/blueprints/-/wikis/robust_time_syncing#current-plan> or test the nightly build <https://nightly.tails.boum.org/build_Tails_ISO_18717-time-sync-before-tor/lastStable/archive/latest.img> of our prototype. Usability tests of first-time use We did some usability tests of our installation instructions. We recruited 5 activists with interest in privacy technologies and observed them while they downloaded, installed, and started Tails for the first time. We hadn't tested this entire flow since 2015 and so many things happened since then. * 3 of them had a pretty good installation experience of 10-20 minutes, download excluded. This process became much easier since 2015 thanks to the distribution of USB images instead of ISO images. * 2 of them went a very bad route and took more than 1 hour to install Tails despite us rescuing them along the way. The good news is that we could help these people with only changes to the website. You can see the detailed findings and the 19 GitLab issues that we created from these usability tests in this rainbow table <https://gitlab.tails.boum.org/tails/ux/-/raw/master/first-time/rainbow_table.fods?inline=false> or read a more detailed report <https://lists.autistici.org/message/20211217.014522.68cdc460.en.html>. (#18074 <https://gitlab.tails.boum.org/tails/tails/-/issues/18074>) We also published our policy for the retention of the user research data <https://tails.boum.org/contribute/how/user_experience/research/> gathered during such activities. Metrics * The Russian translation of our documentation about connecting to the Tor network <https://tails.boum.org/doc/anonymous_internet/tor/index.en.html> was the top growing page on our website, according to Google Search. This happened while Russia started blocking Tor <https://ooni.org/post/2021-russia-blocks-tor/> in December. We are very proud to have released the Russian translation of our entire user documentation in October and released the /Tor Connection/ assistant in July <https://tails.boum.org/news/version_4.20/index.en.html> to make it easier for people to circumvent this kind of censorship. We estimate that 4 times more people are using bridges from Tails since the release of /Tor Connection/, from the /WhisperBack/ reports that we receive from users. * Tails has been started more than 752 953 times this month. This makes 24 289 boots a day on average. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] results for usability tests of first-time use (#18074)
Zen Fu: > sajolida writes: >> We hadn't tested this entire flow since 2015 and so many things happened >> since then. > > That sounds to me as a too long interval for such important work, right? > I wonder if you or someone has an evaluation re. the amount of UX work > needed vs the amount of resources/focus allocated to it, past and > future. It's good that you're making me reflect on this :) The biggest issue that I discovered during the tests is that people missed following the rest of the installation instructions after downloading. I think that this comes from 2 main changes done since 2015: - (Mostly), the split of the download (and verification) page as a separate page from the rest of the installation steps, done in 2017. I did this split when we migrated the verification extension to WebExtension. I tracked this to the download of the image itself not being integrated in the verification process anymore: https://lists.autistici.org/message/20170609.175300.2fbfc35e.en.html We thought that having 2 different pages would help people verify between downloading and moving on with the rest of the installation. I did some usability tests on paper prototype of the new download page, but I skipped doing usability tests of the entire process again on software after the release by lack of budget and time. It was also the first time that I was testing things on paper prototypes. Testing only a paper prototype mislead me because they sometimes influence too much what people pay attention to, compared to being on an actual web page. - (Also), the addition of the warnings at the bottom of the download page, done in 2020. They made the page harder to navigate by hiding the link to the rest of the installations steps in the middle of the download page instead of at the bottom. We clearly didn't pay enough attention to how this change could impact the UX of the entire page. The good news is that this regression was only introduced 6 months ago :) Regarding what I could have done differently since 2015 and lessons learned, we should: - Always test on software on top of testing on paper prototypes. If we can't test on software right away, we should schedule tests without waiting for years. - Consider testing again our critical paths if *anything* changed. Seemingly unrelated doc updates can break a user journey. - Work on outsourcing usability tests. Testing in-house have a lot of value but, in this case, it would have been better to test our installation instructions again in 2018-2019 than to wait until 2021. In this case, testing the installation instructions is also probably one of the simplest tests to outsource. In 2017, we didn't have budget for that but now we could. In December, I started discussing with external contractors to outsource usability tests of our donation process. It will good to try. Regarding the short term plans, we'll solve the biggest issues with #16808, hopefully in January. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Windows Camouflage Feature Help
Zen Fu: > intrigeri writes: >> sajolida (2021-11-24): >>> My opinion is "no", in favor of #7148 but I'd like to hear more from the >>> rest of the team. >> >> I agree. > > +1, I think that: > > - sajolida's analysis makes sense, and > > - trying to reach a cheaper, maybe less convincing, but on the other > hand more general way of "camouflaging" seems to be a sane way to > move forward. Updated #10830 accordingly. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] results for usability tests of first-time use (#18074)
sajolida: > - I'm not even mentioning the nightmare of saving to a folder permitted > by Tor Browser. The low-hanging fruit for that is #15768, already in > the shortlist of our UX debt. Meh! It's rather #15028: Rename "Tor Browser" shortcuts and folders :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] results for usability tests of first-time use (#18074)
Hi, Last week I did usability tests of downloading, installing, and starting Tails with 5 people. I recruited them through friends of friends in activist circles. None of them had heard about Tails before. I handed them a Tails leaflet (in Spanish) and asked them to go ahead and use it. They all installed and started on a MacBook Pro that I provided. Unfortunately, VLC didn't record any audio for some mysterious reason so I can't share any video clips with you. We hadn't tested this entire flow since 2015 and so many things happened since then. You can see the detailed findings and the 19 issues that I created from in this rainbow table: https://gitlab.tails.boum.org/tails/ux/-/raw/master/first-time/rainbow_table.fods?inline=false Installation - Download and install 3 of them had a pretty good installation experience of 10-20 minutes (download excluded). Tons of kudos to the USB images that made this process so much easier! 2 of them went a very bad route and took more than 1 hour to install despite me rescuing them. The good news is that I think we could help these people with only changes to the website. - Verifying Only 1 of them verified her download! She was the one who followed the instructions most diligently. All the other participants didn't verify for various reasons. Most surprisingly, some people didn't verify because they didn't understood that they had to select their download from the "Verify..." button in the download instructions. One of them even ended up in the design doc linked from the toggle section in search for verification instructions :) To solve this, I'll explain better the verification (#18776) and add it as a step in the overview (#18774). - Install The 2 people who took more than 1 hour to install were the kind of people who only follow instructions when in trouble -- and sometimes not even that :) For example: * They tried to open the USB image from the browser or macOS. I'll document this error message. (#18777) We could also distribute our images in ZIP files with help. (#18057) * They tried to copy the USB image on the USB stick because they didn't think that there were other installation steps. I'll clarify this in the steps in the overview. (#18774) Merging the overview, download, and steps will also help. (#16808) * Once they had the image on the USB stick, Etcher didn't let them install Tails on the same USB stick. Etcher should clarify their error message. (#18783) Persistent Storage == Then I asked them to download a picture from the Internet and save it to their Tails in a way that protects it if their USB stick is stolen. Only 3 participants had some time left. They all failed miserably. - The reference to the Persistent Storage on the leaflet didn't stick in their mind, and wasn't even clear when I told them that there was a clue in the leaflet. Until #15586, people won't find out about the Persistent Storage without external help. The Spanish translation said "volume", which didn't help. (#18767) - 2 of these 3 participants had a very hard time even download an image from the Tor Browser. They tried drag-and-drop, didn't find "Save Page As..." in the hamburger menu, didn't use the contextual menu (being on Mac probably didn't help), etc. - I'm not even mentioning the nightmare of saving to a folder permitted by Tor Browser. The low-hanging fruit for that is #15768, already in the shortlist of our UX debt. - Other than that, the new Persistent Storage interface worked fine! It was far from being stress-tested but I don't think it's worth it to test it more until we have more improvements of the blueprint implemented: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/Persistent-Storage-redesign We only found a serious bug in the shortcut to the Persistent folder. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Windows Camouflage Feature Help
CyberPunk.Neural.Interface via Tails-dev: > Looking to help with windows camouflage feature. what GTK version the > latest TAILS build is using or plan on using? For the record, the Windows camouflage was dropped from Tails 2.0 (January 2016) because it was not ported to GNOME 3.14: https://tails.boum.org/news/windows_camouflage_jessie/ https://tails.boum.org/news/version_2.0/ 6 years later, I don't think that we should introduce a Windows camouflage again. I still understand the potential benefits but I don't think that they outweigh the costs and that our team should spend resources on this: - The camouflage can help hiding that you are using Tails to people who can see your screen. It felt and looked super cool (that's important!) but it was not a reliable security solution either (that's important too!). For example, for it to avoid suspicion in a cybercafé or public library, or computer room in a school, it would have to mimic the particular version of Windows or macOS used in the neighboring computers. That's quite more complex than allowing users to switch to 1 alternative GNOME theme. - Even if an external contributor, like you (thanks!), wants to help with a new camouflage, it will always require our core team to do some work for it to happen (answering questions, reviewing code, etc.). Plus, it becomes something that our team will have to maintain in the future. Lack of maintenance work is precisely what caused the original camouflage to be dropped. - Before you start the session, it would be extra hard to make the Boot Loader or Welcome Screen look like Windows or macOS. Once you started using Tails and have several windows open, your screen looks more like a "browser with a website on it" than Tails. At most it looks like a Linux distribution to people close enough to see the menus and window frames. I think that we should instead work on allowing a custom desktop background (that people could configure to look like Windows or macOS) and maybe a custom GNOME theme. That's https://gitlab.tails.boum.org/tails/tails/-/issues/7148. I think that it would be less initial work, less maintenance, and would cover more use cases. Customization is an important emotional aspect of technology. For example, custom background was in the top 5 feature requests in the 2020 survey, along with Monero, VPN, and persistent Tor Browser settings: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/user_survey/openpgp_and_pidgin#general-purpose-questions #10830 was rejected 4 years ago by lack of progress. I think that we should use this thread on tails-dev to clarify whether we might accept contributions to a new camouflage or not, and document this on #10830 for the future. My opinion is "no", in favor of #7148 but I'd like to hear more from the rest of the team. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Release schedule for Tails 4.24
intrigeri: > This release should include a major upgrade: Tor Browser based on > Firefox 91. We won't have the capacity to do a release candidate > but we should be able to at least call for testing of a nightly build. > > Dear technical writers, please account for the corresponding potential > doc updates. Thanks for the heads-up! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Tails report for September 2021
Tails report for August, 2021 <https://tails.boum.org/news/report_2021_08/> Releases In august, we released 4.22~rc1 and 4.22 <https://tails.boum.org/news/version_4.22/index.en.html>. Having a release candidate helped us gather feedback from users to build a more solid 4.22. Enjoy it! Tails 4.23 is scheduled for October 5 <https://tails.boum.org/contribute/calendar/>. Highlights of the month * We migrated our XMPP chat rooms <https://tails.boum.org/support/talk/index.en.html> to |disroot.org|. You do /not/ need to have a disroot.org account to join us on the talk chat, any XMPP account is fine. XMPP chat room is only used for users' mutual help, and is not always monitored by our help desk. Write an email if you want to talk with Tails' help desk. * The Foundations Team <https://tails.boum.org/contribute/working_together/roles/foundations_team/> met for a sprint, which resulted in many bugs being fixed and features being added. You can taste some of them in 4.22 <https://tails.boum.org/news/version_4.22/index.en.html>, but some of them haven't make it for the current release: o Improving the time zone selection user interface (#18514 <https://gitlab.tails.boum.org/tails/tails/-/issues/18514>). o Redesigning Persistent Storage setting (#17803 <https://gitlab.tails.boum.org/tails/tails/-/issues/17803>). * Our joint proposal with Tor to DRL has been accepted. This will help us do more user research and implement UX improvements. * We added Word Solver as a sponsor <https://tails.boum.org/sponsors/index.en.html>. * We are improving the speed of our Continous Integration infrastructure. This is not immediately visible to users, but helps making Tails' development more enjoyable and sustainable. Metrics * Tails has been started more than 675,177 times this month. This makes 22,505 boots a day on average. How do we know this? <https://tails.boum.org/support/faq/index.en.html#boot-statistics> -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Using TAILS
safe-the-planet via Tails-dev: > Dear Ladies and Gentlemen, Hi, > 1) There are very good videos on YT how to install TAILS. We have > already written out the procedure and wanted to install TAILS soon. But > unfortunately you need two USB sticks for it. Now we have seen on the > homepage of TAILS that you can also do this directly in Linux - in the > terminal. This is faster and only one USB stick is needed. Not that we > only have one USB stick, we find the installation via terminal easier. > Do we see it right, that you can only copy the commands and paste them > into the terminal? You have to be a little careful to use the right name > ... But otherwise we find it easier. Our official instructions have not required 2 USB sticks since October 2018. That's why we don't recommend YouTube videos: they tend to be very outdated and confuse more than help. Please refer only to https://tails.boum.org/install/. > 2) We always read that you should NOT use TAILS or the TOR browser with > VPN. What do you recommend? Why is it more insecure to use with VPN, > should it be the case? Of course, we assume VPN's that have an > appropriate reputation and can be classified safe. Otherwise, of course, > the situation is clear. See our FAQ on VPNs: https://tails.boum.org/support/faq/#vpn. > 3) Why is the homepage called "tails.boum.org"? Why "boum"? Our website used to be hosted by boum.org, but not anymore. We've been looking for a better domain name but haven't got one just yet. > 4) In the persistent folder the data is secure but the folder is > visible. Will TAILS eventually come with programs similar to Veracrypt? Not super likely: https://gitlab.tails.boum.org/tails/tails/-/issues/5929. > Or can these invisible folders be displayed with appropriate software? See https://tails.boum.org/doc/encryption_and_privacy/veracrypt/. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] An outside of the box proposal re persistence backups
intrigeri: > Thanks for clarifying. I've added a note to the blueprint so we don't > forget this option whenever it'll be time to work on the S4 > user scenario. We won't invest resources into this before we actually > have backups (S1) but it's great that you're experimenting with btrfs > in the context of Tails! I didn't know anything about btrfs before this thread. Thanks for educating me! What I particularly like about this idea is that it could provide backup history (scenario S4 on the blueprint) while being compatible with the plans we had so far. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Add simple GUI to back up persistent volume (attached)
intrigeri: > @sajolida, what do you think? Sounds great! Also, the code is simple enough to allow me to work on the UI and strings on my own :) Thanks a lot David for helping us do meaningful increments on this very important missing feature. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] bridges
pathes.mathes--- via Tails-dev: > Hello. There is no place to store the obfs4 bridges in my Tor browser; > the instructions about Settings, Tor, Store a bridge don't apply to my > Tor browser. Since I do not have persistent storage setup, not sure how > I could store the obfs4 bridges anyhow. Could possibly write-in the > obfs4 at start-up but they are kind of long. Hi Aristophrenes, Thanks for sharing your findings! It helps us improve Tails. Sorry for the delay in getting back to you. We're working on a feature to store bridges in the Persistent Storage for Tails 4.22 (September 7): https://gitlab.tails.boum.org/tails/tails/-/issues/5461 We're also working on making it easier to enter bridges each time: https://gitlab.tails.boum.org/tails/tails/-/issues/18219 If you don't have a Persistent Storage, maybe you can store your bridges in another USB stick for now? -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Can't connect through bridges
Felipe via Tails-dev: > Hello. I am having trouble to connect through tor using bridges, > plugable transports or anything really. It only works if I choose to use > tor without bridges. > > I use the bridges or plugable transports provided by torproject... > > The OS was running smoothly, though with an old version of December 2020. Hi Felipe, Thanks for sharing your findings! It helps us improve Tails. Sorry for the delay in getting back to you. Bridges only work fine if the clock of your computer has a correct time. If you are East of London and have Windows installed on your computer, bridges will most likely not work: https://gitlab.tails.boum.org/tails/tails/-/issues/15548 https://tails.boum.org/doc/anonymous_internet/tor/#index4h1 We are working on a fix for this issue in Tails 4.22 (September 7). -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Bridge Connection Assistant Feedback/Question
Xxxx Xx: > Hello devs! Hi! > Thanks so much for all your work, you are heroes. Thanks for sharing your findings. It helps us improve Tails. Sorry for the delay in getting back to you. > I am writing to ask for assistance with the Connection Assistant when > entering bridges. I acquired 2 obfs4 bridges via the automatic emailer, > but when I entered them in the CA, the Connect button was still greyed > out. As a relative newb, I assume this is somehow operator error, but > since it's such a new application, there isn't much in the way of > troubleshooting guides. I would appreciate any guidance you can offer. We know that some people are having problems entering their bridge lines correctly: https://gitlab.tails.boum.org/tails/tails/-/issues/18478 I referenced your problems from this GitLab issue. More likely you didn't enter the bridge lines correct that that's why the "Connect to Tor" button stayed unavailable. Could you check your bridge lines and confirm whether this was your issue? Thanks! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Problems with 4.2
Now putting Neil in copy since they are not subscribed to tails-dev. N Pitceathly: > I have upgraded 4.19 to4.2 and have unfortunately struck problems signing > into Tor. I like to keep my anonymity so have usually signed in using Tor > bridges added and have presumed that's what happened. With 4.2, I am > unable > to connect in anyway other than a straight connection. ooops, sorry to hear that, and thanks for reporting us! I understand you were already using bridges with 4.19, right? > I have emailed Tor for bridges, and copied then into the space allocated > for them, but there is always an error message. Also, once I get an error > message there is no way to go back so that I can change my method of > connecting to straight through. Let's see if we can understand why this happens: - have you copied the whole (very long) bridge line? an example is obfs4 76.74.178.195:9443 406A8B5869B72221036291407EC3688C69995F80 cert=FY2R16JOoE2VNCU2gVLWBj6Gg+YBP7mTLU5zl12Fz9iC5TQG6SqE71CFhD3zIuJcEFrcMQ iat-mode=0 - is Tails clock accurate? Is it more than an hour greater than UTC? https://time.is/UTC unfortunately we have this bug which might affect you if this is the case: https://gitlab.tails.boum.org/tails/tails/-/issues/15548 bye! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Unable to connect on tor
Now putting Odran in copy as they might not be subscribed to the mailing list. boyska: > Odran Ligneul: >> Hello there, > > hello, and thanks for sharing your feedback with us! > >> I just updated my tails with the most recent version and I need now to >> configure my Tor. >> >> I am using my personal WiFi without any issues in the past and now, I am >> not able to connect on tor anymore. >> >> I used different bridges downloaded from your website and your email >> addresse but none of them work when I enter them, I always get the "error >> connecting to tor" > > were you already using bridges before, with other versions of Tails? Also, which options did you choose in the Tor Connection assistant? Could you tell us in more details what you did and what happened? > I think you hit this bug: > https://gitlab.tails.boum.org/tails/tails/-/issues/15548 > the good news is that we are working on it :) > the bad news is that there's not much you can do about that, right now. Since Odran is telling us that they had no problem before 4.20, I'm tempted to think that this is rather another occurrence of: https://gitlab.tails.boum.org/tails/tails/-/issues/18481 >> Since I am not using a public or a corporate network, I should not >> struggle >> to connect on tor right ? > > If you use the "easier" option on Tor Connection first choice, that > should work for you, then, and fix the problems you are seeing. > > But keep in mind that *will* reveal that you are using Tails. see > https://tails.boum.org/doc/anonymous_internet/tor/index.en.html for more > info on this choice. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] links for donor's newsletter
Hi, Next week, I'll send a newsletter to donors. It'll be the first time we write to donor outside of the end-of-year fundraiser. Yay! I thought about having a section of news and links that could be of interest to our readers. I'm not a big Internet browser myself so I thought about ask all of you for help :) What recent links do you think could be of interest to past donors and align with our mission and values? https://tails.boum.org/contribute/mission/ I probably won't have space to include all of them and will curate the list to only keep the best ones. Thanks in advance :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Tails report for June 2021
Tails report for June, 2021 [1] HIGHLIGHTS * We entirely rewrote and redesigned our very old warnings page [2]. The new warnings page [3] is shorter, easier to understand by less technical people, less scary, more helpful, and visually attractive. We also integrated it in our download page [4] so that people can learn more about tails while waiting for their download. Read our articles on: * Protecting your identity [5] * Limiations of Tor [6] * Using untrusted computers [7] * We finished making Tails ready for the deprecation of onion services v2 by upgrading to OnionShare 2.2. * We explained that users can reduce the size of the download [8] of future automatic upgrades by doing a manual upgrade to the latest version. * We published our finances for 2020 [9]. * We documented better MAT and metadata [10]. * We documented how to use Dino in Tails [11]. Dino is being considered as an option to replace Pidgin in Tails. Please report your findings! METRICS * Tails has been started more than 629 659 times this month. This makes 20 989 boots a day on average. How do we know this? [12] Links: -- [1] https://tails.boum.org/news/report_2021_06/ [2] https://web.archive.org/web/20210531191605/https://tails.boum.org/doc/about/warning/ [3] https://tails.boum.org/doc/about/warnings/index.en.html [4] https://tails.boum.org/install/download/index.en.html [5] https://tails.boum.org/doc/about/warnings/identity/index.en.html [6] https://tails.boum.org/doc/about/warnings/tor/index.en.html [7] https://tails.boum.org/doc/about/warnings/computer/index.en.html [8] https://tails.boum.org/doc/upgrade/index.en.html#reduce [9] https://tails.boum.org/doc/about/finances/index.en.html#2020 [10] https://tails.boum.org/doc/sensitive_documents/metadata/index.en.html [11] https://tails.boum.org/doc/advanced_topics/dino/index.en.html [12] https://tails.boum.org/support/faq/index.en.html#boot-statistics___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: use a Label instead of a Milestone to track our roadmap
intrigeri: > https://gitlab.tails.boum.org/groups/tails/-/issues?label_name%5B%5D=2021 > https://gitlab.tails.boum.org/groups/tails/-/issues?label_name%5B%5D=2022 Thanks :) Using the same green as for Sponsors looks like a perfect choice! I hope that the mess I did 2 weeks ago didn't make your work more complicated. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: migrate our public chat rooms to another friendly XMPP server (#17956)
intrigeri: > I'd like to hear your thoughts about this topic by July 11. > > [...]> > Why keep a public chat room at all? > === > > A few months ago, in a survey run on this mailing list, a number of > reasons were raised in favor of keeping a tails-dev public chat room. > sajolida played the devil's advocate about some of these reasons, > then the discussion stopped. My understanding is that we have a rough > consensus in favor of keeping such a chat room, at least for now. The devil's advocate likes the current proposal and thanks you very much for keeping our infra running :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: use a Label instead of a Milestone to track our roadmap
boyska: > seems good to me. Thanks everybody for sharing your thoughts. I tried to implement this and realized half-way through that it requires group labels that I don't have the rights to create. So see you on https://gitlab.tails.boum.org/tails/sysadmin/-/issues/17837 for the implementation. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] UEFI is not BIOS
Hi conan, Good to see you on tails-dev@ :) Cody Brownstein: >> It appears that BIOS is used for both BIOS and UEFI. > > I think for this documentation it's fine to use BIOS in place of UEFI. > Regardless of whether the user's computer has a traditional BIOS or a > modern UEFI, the goal is to get Tails to boot off the USB stick. Right, that's why I wrote only "BIOS" here. I think that most people continue to use the word "BIOS" to mean either BIOS or UEFI. In this particular case, it doesn't really make the documentation more cumbersome to follow so I went ahead and changed "BIOS" to "BIOS or UEFI" in 19fcdac8ce. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Proposal: use a Label instead of a Milestone to track our roadmap
Last year, we encoded the items on our roadmap using the Milestones %2021 and %2022: https://gitlab.tails.boum.org/groups/tails/-/milestones/10 https://gitlab.tails.boum.org/groups/tails/-/milestones/109 The problem is that we lose this information as we assign issues to the version numbers that we use as milestones to organize our work on a shorter time frame. For example, I want to get #8845 done by 4.20, so I moved it from %2021 to %4.20, lose the roadmap semantics. As a consequence, it's hard to have a bird's view of the progress made on our roadmap (or a kanban). I propose that we change this to using labels, for example ~2021 instead of %2021. This way, changing milestones wouldn't lose the roadmap info. It would make it easier to track and evaluate progress without having to go back to the canonical version of the roadmap from Mural. Do you see any disadvantage to using a label instead of milestone for our roadmap items? -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
I created summit#27 to track the implementation of the new proposal. https://gitlab.tails.boum.org/tails/summit/-/issues/27 -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing nore...@tails.boum.org: > We should start writing the monthly report for last month. > > A blueprint with the current report, who volunteered to curate it, and > tips on how to fill it can be found on: > > https://gitlab.tails.boum.org/tails/blueprints/-/wikis/monthly_report/ > > But *you* should make sure that the cool stuff that *you* did will be > mentioned in there. The person who volunteered to curate the report will > help coordinate, patch, and rephrase things but will not be able to go > through every possible source of information (including what's in your > head). > > Keeping in mind that these reports are targeted at the other Tails > contributors, people contributing to related projects, expert users, and > Tails advocates, so they can be useful, for example, to: > > - Give others a quick overview of what you are doing and where your work > can be found. > - Get help or feedback from others. > - Give a sense of the very diverse contributions that are valuable to > the project and encourage more people to join in. > - Show off how cool we are! OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Fwd: [Job] Senior Security Engineer, SecureDrop team
Forwarding here an exciting job offer slightly related to Tails -- at least contributions to Tails are listed in the "Great to have" :) Forwarded Message Subject: [Job] Senior Security Engineer, SecureDrop team Date: Wed, 26 May 2021 22:07:14 -0700 From: Erik Moeller Hey folks - We're hiring a Senior Security Engineer for SecureDrop, an open source platform used by about 70 news organizations around the world to receive tips from anonymous sources. More about the job here: https://freedom.press/jobs/job-opening-senior-security-engineer/ We're a distributed team, so applications from around the world are very welcome. If you're thinking about applying or recommending someone, but have questions first, feel free to shoot me a note! Help spreading the word in your networks is very much appreciated <3 Warmly, Erik -- Principal Project Manager Freedom of the Press Foundation OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
ignifugo: > AH I read about this... > > " > Ask Me Anything session with Tails > " > > I will add in the upcoming event in the report of April. Please don't advertise the Ask Me Anything in our monthly reports. See #18194 for our outreach strategy. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] IP change of tails.boum.org
tails-sysadm...@boum.org: > We're planning an IP address change for our main server, to be done in > the 2nd week of June (7th-11th) 2021. > > Please avoid relying on the server and expect some outage during those > days. I understand that our users will be affected in a similar way as they were this week-end: broken upgrades and broken /home. I think that your team should at least communicate about this in real time on Twitter. I won't be doing this communication in real time with you but I can help you to make sure that you can use our Twitter account on that day. If you expect the outage to last from more than a few hours, maybe we should also consider other ways of warning people in advance, maybe with another short blog post posted the week before and sent to amnesia-news. What do you think? -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails 4.19~beta1 postponed (and what about 4.19~rc1?)
anonym: > * I was supposed to prepare it, but I've been sick this week and haven't > been able to put in the needed hours > * We found some last-minute issues we'd ideally like to be fixed Thanks for the update! > Also, as you might have seen elsewhere, Mozilla just pushed all releases > one week into the future, which in particular means that 4.19 also will > be released a week later than planned, so we actually have a bonus week > and can afford to postpone. In other words, if we release 4.19~beta1 on > Thursday, 29 April, we'd give users the same amount of time as before. I > think we can do it earlier than that next week, on Tuesday, April 27. > > But then there would only be a bit more than a week until 4.19~rc1, > which feels like a waste. So I propose we postpone it a week, until > April 13. In summary, users will then have two weeks to test the beta > (and we to fix the problems) until the RC, and then they have a bit more > than two weeks to test it before the final release. > > tl;dr: > > Proposal: > * Tails 4.19~beta1 is postponed from 2021-04-22 to 2021-04-27 > * Tails 4.19~rc1 is postponed from 2021-05-06 to 2021-05-13 Works for me. We rescheduled our meeting to debrief the feedback with boyska to Wed May 5, 16:00 UTC. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: use the "Reviewer" field in GitLab MRs
intrigeri: Any issue with that? No issues for me. It seems like that coders depend on GitLab features for productivity much more than my own teams. So I trust the Foundations team to make the right choice here and I appreciate the energy that you put into these things. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Donation campaign analysis
Hi, Below is my usual analysis of the donation campaign. Summary: Amount 112 129€+42% Number of donations 2799+40% Recurring donors297 +29% Boots per month in 2020 30250 +20% Work time 35 h-27% This does include a huge donation in bitcoins worth 34.7k€. This does not include a huge donation of 50k€ from a company that contacted us on tails-fundrais...@boum.org. They didn't want to be named on our sponsors page but we usually don't include sponsors in the analysis of the campaign. The campaign was 10% shorter (88 days instead of 96 usually) and started right after Tor launched their campaign, which I always avoided in the past. We would have had even better results with a slightly longer and slightly earlier campaign. Cryptos --- Cryptocurrencies have seen a huge increase this year going from: - 39% of the money to 69% - 29% of donations to 35% Bitcoin grew more in amount (+368%) and not only because of the huge donation. Monero grew more in donations (+254%). Other cryptos are still peanuts with less than 1% of the money. Incentives -- This year, we did 3 significant changes to how we advertised the donation campaign: ### Design work on /donate and the banner For record, we: - Improved the structure and text on /donate. - Worked with Andrés to create images for /donate and the banner. - Improved the slogan on the banner based on a survey from previous donors and tested the banner with potential donors. ### Twitter I did an extensive Twitter campaign, with help from Estrella Soria and scheduled 34 tweets in 4 languages across 68 days. 9% of the referrers on /donate came from Twitter. That's a lot! In comparison, only 1.2% of finalized PayPal donations came directly from a link on Twitter, that is, without additional clicks in-between. This number is computer on very few such donations so pretty unreliable. What I'm not sure here is whether Twitter users drop out much more (likely if they didn't know Tails before) or whether Twitter donors browsed other parts of the website before donating (likely as well). Last year I didn't have the logs of the website so I can't really compare how much more this was. ### Blog posts I only wrote 2 blog posts: - /news/achievements_in_2020, on December 23 - /news/plans_for_2021, on January 8 In the past, we always launched the campaign with an extra post. This post was usually the most painful to write because we have to find yet another way of asking for money. To evaluate the impact of this opening post, I compared the 1st week of the campaign with the first 4 weeks of the campaign, in 2019 and 2020. In 2019, 46% of the donations in the first 4 weeks were done in the 1st week, versus 50% in 2020. In 2019, the first 4 weeks also included our usual blog post on achievements. So our campaign launched more successfully in 2020 without opening post. There is also no clear sign of extra activity after the 2 later blog posts from 2020. This confirms data from previous years: carefully crafting blog posts has very little impact on the results of the campaign. Communication with donors - This year, I did 2 improvements to how we keep in touch with donors: - I added a checkbox on /donate for people to opt in to a newsletter, 2-3 times a year. 26% of PayPal donors opted in to receive our newsletter. - I started using the invitation feature of LimeSurvey to send the call to the donation campaign and the thank you email. It's totally hackish but allows sending prettier emails and provides an opt out link to recipients. Before people had to send us an email to opt out. Many more people unsubscribed with this new opt out mechanism. I don't think that's because of the format or content of the email and rather because of the change in the subscription mechanism. I have good hopes that both these improvements will help us build a stronger relationships with donors in the long run. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Risks of Additional Software feature (was Re: decentralized ethereum wallet)
duc01k--- via Tails-dev: Opened a bug: https://gitlab.tails.boum.org/tails/tails/-/issues/18232 Thanks for the clear feedback duc01k! I wrote this doc and reading your detailed comments about how you understand each line really helps me understand better your concern. To be honest, I'm not sure that we can do a lot to make this doc less scary but there are definitely some bits of it that can be improved to be clearer. I don't think that working on this should be a big priority for our technical writing team but at least it's good to have all this feedback well tracked for when we'll work on it. See you on #18232 :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Registration for RightsCon (June 7-11, 2021) is now open!
Tickets for RightsCon are on sale at early bird price until March 31. I might be presenting our fundraising work at a session, so I'll buy myself a ticket next week unless someone disagrees. Shout out if you also want to be representing Tails at RightsCon21. For the record: https://tails.boum.org/contribute/sponsorship_to_attend_events/ -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] QR code maker/scanner built in Tails OS
Eirik Slettebø: That would be useful to copy text to and from Tails OS out of the box without a network connection. You can install the zbar-tools package using the Additional Software feature of Tails. It include a zbarcam utility that can scan QR codes from your webcam. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
emma peel: emma peel: OK, I am curating the report. Please add your information until Feb. 8, as I want to publish it on Feb.10 Here the link: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/monthly_report/report_2021_01 OK, the report is ready for review'n'merge at https://gitlab.tails.boum.org/tails/tails/-/merge_requests/346 It would be nice to have it published today. It builds ok in local. I hope I didnt forgot to add anything important! Merged! https://tails.boum.org/news/report_2021_01/ -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] The future of monthly reports, 2021 edition [Was: Preparing the next monthly report]
intrigeri: sajolida (2021-02-03): I've curated ⅔ of reports since 2017 (I've asked sajolida for clarification privately as this is very different from the data I see. But anyway, this should not impact the analysis I did below.) Sorry I messed up my calculation yesterday. It's more like ⅓ actually :) I was pissed off and hurried when I wrote this email yesterday and I didn't realize that this figure was totally unrealistic; though it matched my state of mind at that time :) Mea culpa. My conclusion is that overall, this new setup did not reach its goals: the work is less tedious for sure, but most of the work is still done by the same few people. +1 - technical writers act as writers and editors, i.e.: - use our internal team monthly reports to write good quality contents, with a communication style that's consistent with the rest of our communication (for example, shorter than this email :]]] ) - define a strategy, e.g. in terms of frequency (it could be that monthly is not the best, I dunno, I'm not trained at this kind of communication) - welcome contributions from volunteers and decide what to do with them - other teams share info, needs, expectations, and feedback with technical writers about the intended audience they have in mind for these reports (e.g. FT about Debian & Tor people, fundraising about potential donors, etc.) At this point this is meant to be half a proposal, half a conversation trigger. Perhaps you disagree with my assumptions and goals? Perhaps you have other ideas? Also, this proposal is clearly not perfect. For example, in an organization with more resources, folks trained/experienced at communication would handle the communication strategy and act as editors. In our current situation, my impression is that technical writing is the closest skill we have in-house to communication, hence this proposal. I agree with your analysis. I'm not sure whether the technical writing (TW) team is in a good shape right now to take this over. I really don't want to add this to my TW plate which is already full. Maybe Cody can take this over without my help. Sam is still in a trial period and probably has too little general knowledge about the project yet. More on the long-term, these reports could totally fit in the responsibilities of a management-ish non-technical hire. Finally, I'm fine with either putting the reports on hold, or publishing them only when someone volunteered to curate them, until our technical writing capacity has increased sufficiently to cope with this additional task. I understand it is a matter of mere months now :) And thanks a lot to emmapeel for taking over January's report. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
Tails: The person who volunteered to curate the report will help coordinate, patch, and rephrase things but will not be able to go through every possible source of information (including what's in your head). I volunteered to curate the January report some weeks ago but I withdraw myself today. I'm seriously overworked with the UX sprint until February 15 and in Tails in general. I've curated ⅔ of reports since 2017 but I won't curate them anymore. This monthly report dynamics has been recurrently frustrating for me. What I envisioned as a way of communicating within the project, connecting with the rest of the world, and celebrating our achievements, has felt broken for me for years. I've put a lot of energy in the past to try to change this but I don't have this energy anymore. I'll find elsewhere the information that I need from them. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Rewrite live-persist as part of Persistent Storage settings rewrite
segfault: What do you think about that plan? I already talked to segfault about this but I think it's amazing and super important! Right now, an essential concept in the redesign that I worked on last week is to help people enable the Persistent Storage features that they need right when they need it: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/Persistent-Storage-redesign#just-in-time-help It would prevent people from: - Restarting yet again - Loosing data because they didn't realize that it could be saved to the Persistent Storage before creating one or activating the corresponding feature (eg. Wi-Fi password time and time again in my usability tests). > I plan to do that in bash, copying the parts from live-persist and live-boot which we need for > that. Bash for the win! I trust you to have good reasons to choose bash over Python here :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] selling merch as Tails while outsourcing the effort - some concrete ideas
s the procurement service also handle designing and producing the merch or do we have to do this ourselves? What kind of items can they produce themselves, eg. USB sticks or condoms (Tails is the condom of the cyberspace!). Anything else? I created an issue on GitLab to track this research: https://gitlab.tails.boum.org/tails/tails/-/issues/18141 Our Fundraising team is seriously understaffed so I won't put energy into doing this research myself but it would be great if syster and others start gathering info on the GitLab issue. I also don't see us doing this any time soon, so bare in mind that this research might not be put to use before years. But we also want reliable procurement services on the long-term so our slow pace shouldn't matter so much :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [announcement] Blueprints migration on 2021-01-14 (#18079) [Was: Proposal: migrate our blueprints to a GitLab wiki]
intrigeri: intrigeri (2021-01-12): So, today I'll start planning & implementing the migration to a GitLab wiki. At some point I'll have to make our blueprints read-only. I'll share timing info once the migration steps are clearer to me. I've done all the preparation work I could think of. Wow, already! Impressive. Good luck with the migration! I'm so glad this will finally happen. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [brainstorm] What are our public XMPP chat rooms useful for? (#17956)
intrigeri: - some of our soul and identity, i.e. "we work in the open" - a place where friendly bystanders can lurk and follow our work: FOSS developers, users, etc. Devil's advocate: How good is #tails to follow our work compared to: - #tails-summit to which friendly bystanders don't have access to? Though I'm not sure what's done where these days. - Our public monthly reports? It's not the same kind of information, which is would be more useful to follow our work and for which public? - https://gitlab.tails.boum.org/tails/tails/-/issues?sort=updated_desc - a little bit of the efforts we've put into dismantling the long-standing myth that Tails is produced by some sort of secret, unapproachable group of anonymous people Devil's advocate: Big tech and proprietary software companies have neither public development channels nor suffer from the myth of being pseudo-clandestine organizations. Having a public XMPP room wouldn't add much if this was solved on our website: - #17700: Have an "About Us" section - #17046: Have a "People" page -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing OpenPGP_signature Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Tails report for December 2020
Tails report for December, 2020 [1] IN MEMORIAM OF KARSTEN LOESING We join the Tor project in mourning Karsten Loesing [2]. Our sincere condolences to Karsten's family and colleagues. Those of us who were lucky enough to cross Karsten's path remember him as a very kind, thoughtful, and smart person. Rest in peace, Karsten. RELEASES * Tails 4.14 was released on December 15 [3]. * Tails 4.15 is scheduled for January 26 [4]. The following changes were introduced in Tails 4.15: * Add support for the Ledger hardware wallets in _Electrum_. (#15353 [5]) * Remove the _Unifont_ font. (!263 [6]) * Fix Additional Software by updating the APT key for deb.torproject.org. (#18042 [7]) * Fix changing the administration password stored in the Persistent Storage. (#18018 [8]) * Fix opening the Persistent Storage of another Tails USB stick in the _Files_ browser. (#18050 [9]) * Restore automatically a _GnuPG_ public keyring from its backup when it gets corrupt. (#17807 [10]) NEW CORE DEVELOPER Today, we celebrate the arrival in our Foundations Team [11] of a new member: boyska. His skills and experience in operating systems, software development, and collective projects will: * Accelerate development of new features, user experience improvements, and bug fixes. * Make our day-to-day maintenance work more sustainable. This work has no visible impact most of the time, except that Tails is still alive after more than a decade, and here to stay! * Decrease our reliance on a tiny number of key persons. This is one important step we're taking, among others, towards making Tails a healthier project. > I'm boyska, a fellow who always loved computers. When I realized the profound > social implications of technology, I tried to make my part: that's how I got > involved with free software, security and hacking in general. A post-it note > in my brain remembers me that computing should be fun, not scary. Additionally, we would like to thank: * the thousands of people whose donation allowed us to fund this new position Please consider donating today [12] to fight surveillance and censorship. * the dozens of people who applied to this job offer [13] It's been truly heart-warming to see so many great applicants interested in working with us. Welcome, boyska! :) CODE * We implemented a mechanism for adding a "Don't Show Again" button to some notifications. We'll try it out in Tails 4.15 for the warning displayed when starting Tails in a virtual machine; then we'll iterate from there. * We finished porting our Python code to Python 3. Yeah! * We made plans for rewriting _Persistent Storage_ in Python, making it compatible with Wayland, and redesigning its UX from scratch. DOCUMENTATION AND WEBSITE * Started rewriting /doc/about/warning: * Samuel DiBella rewrote the section about contextual identities [14] (#17882 [15]) * We rewrote the sections about confirmation attacks and global adversaries [16] (#17869 [17]) * Added an FAQ about "Is it safe to use an older version of Tails? [18]" (#18001 [19]) * Improved our security [20] page and replaced "hole" by "vulnerability" everywhere on our website, as per our style guide. (#18032 [21]) USER EXPERIENCE * Started analyzing the search queries on our website, following a methodology by Susan Farrell [22]. (#11649 [23]) * Started preparing the redesign of the Persistent Storage that we'll work on in January. (#15572 [24]) * Investigated what it would take to stop distributing ISO images: * #18047 [25]: Users unintentionally install ISO to USB instead of the .img * #18054 [26]: Distribute USB images by default for all virtual machines * #18055 [27]: Stop distributing ISO images * Added some depth to the buttons on our website. (#15111 [28]) FUNDING GRANTS * Our proposal to the UXFund to work on a replacement for Tor Launcher was approved buy scaled down by 20%. DONATIONS * Received 57.8kEUR from 88 donations at CCT since the beginning of the campaign. It's 70% more donations, that's the important part, and 599% more money thanks to a 50kEUR donation from some crypto trading company, that's the big cherry on top of the cake! * Blogged about our achievements in 2020 [29]. SPONSORS * Renamed "partners" as "sponsors [30]" after DeepOnion listed Tails as their partner on their website. The word "partners" implies reciprocity and a deeper relationship, while the word "sponsor" doesn't and is more accurate, honest, and common. * Got invited to the Lifetime Raffle [31] of ProtonMail. OUTREACH PAST EVENTS * Tails and Tor were presented (among other tools) to journalism students at Sciences Po
Re: [Tails-dev] Git submodules stuff polluting my repos
intrigeri: Also, please pay special attention to the "Update your Git configuration" part, and make sure you follow all steps to ensure your repositories and submodules all point to the new and correct places. Fixed :) I missed `git submodule sync` that was added to the doc in August. Thanks for the hint! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Git submodules stuff polluting my repos
Since a while, I have changes to tails.git:submodules uncommitted in all my local copies of the repo: diff --git a/submodules/mirror-pool-dispatcher b/submodules/mirror-pool-dispatcher index baf816c2d7..99bb6898d0 16 --- a/submodules/mirror-pool-dispatcher +++ b/submodules/mirror-pool-dispatcher @@ -1 +1 @@ -Subproject commit baf816c2d7fc447e49c1fdb977144766d8786e92 +Subproject commit 99bb6898d04f57995835044520f6192c50b62399-dirty I tried to: - Update my submodules: git submodule update - Remove all submodule configuration and folder - Reset them entirely: rm -rf submodules git submodule update --init I get errors and can't get rid of them: $ git submodule update --init Submodule path 'submodules/chutney': checked out '71b25eeec8ae9e5a6968139917b72c588f583a57' Submodule path 'submodules/jenkins-tools': checked out '3bb3123456cf507698aafc22f882238fcc27bfc1' fatal: remote error: FATAL: R any mirror-pool-dispatcher daemon DENIED by fallthru (or you mis-spelled the reponame) Unable to fetch in submodule path 'submodules/mirror-pool-dispatcher' fatal: remote error: FATAL: R any mirror-pool-dispatcher daemon DENIED by fallthru (or you mis-spelled the reponame) Fetched in submodule path 'submodules/mirror-pool-dispatcher', but it did not contain baf816c2d7fc447e49c1fdb977144766d8786e92. Direct fetching of that commit failed. What's up here? I never use submodules myself and would really like to be able to silent all this noise. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Preparing the next monthly report
We should start writing the monthly report for last month. A blueprint with the current report, who volunteered to curate it, and tips on how to fill it can be found on: https://tails.boum.org/blueprint/monthly_report/ But *you* should make sure that the cool stuff that *you* did will be mentioned in there. The person who volunteered to curate the report will help coordinate, patch, and rephrase things but will not be able to go through every possible source of information (including what's in your head). Keeping in mind that these reports are targeted at the other Tails contributors, people contributing to related projects, expert users, and Tails advocates, so they can be useful, for example, to: - Give others a quick overview of what you are doing and where your work can be found. - Get help or feedback from others. - Give a sense of the very diverse contributions that are valuable to the project and encourage more people to join in. - Show off how cool we are! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Fwd: Re: [Tails-project] Have you guys considered selling Tails USB sticks or merch instead of donations like the old days?
BRBfGWMz: For now, do you want me to create a write up of the process? I don't know how far you've been. What kind of information would you like to see in it? Ideally, we would gather information that helps us understand: - What kind of services we can get from such companies. - How different companies differ and how to choose one. I understand that you started investigating only one company, so we can't "compare" them yet but we could start gathering info about what service they provide that would be useful to Tails and under what conditions. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] GitLab MR terminology update: WIP → Draft
intrigeri: > I like the fact "Draft" is short enough that I won't be tempted to > use an acronym for it ;) Yep. With my technical writing hat on, it's an excellent renaming! :D -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the upcoming release: 4.9
Cyril Brulebois: > Hi, > > After a somewhat extended break, I'm trying to plan my coming back to > Tails duties to get ready for the upcoming release (4.9, July 27-28). Welcome back! It sounds like a perfect timing :) I hope that your time off was good! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Monero GUI/�CLI Debian Package On Tails
Mr. Lee Chiffre: >> If we can push the Monero GUI and the Monero CLI onto the official Tails >> OS, it would go a very long way in terms of financial privacy on the Tails >> OS. > > I think it is a great idea to include Monero onto Tails. Monero is a very > mainstream coin as an alternative to Bitcoin. I agree that, if Tails was to include software for another cryptocurrency, it should be Monero. We have a FAQ about adding more software to Tails: https://tails.boum.org/support/faq#new_software If a software is not included in Tails, but is included in Debian, you can use the Additional Software feature of the Persistent Storage to install it automatically every time you start Tails. I see that the monero CLI and server is already in Debian but that the shape of the package is not super great: https://tracker.debian.org/pkg/monero I can't find any GUI for it in Debian. If the Monero project upstream is serious about Linux adoption, they should be the ones working on having it in Debian. I don't think that Tails should do this work. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] how to replace "Core Work" views? [was: GitLab is now in production]
sajolida: > intrigeri: >> Where to ask questions and report problems >> == >> >> There are most certainly some rough edges, confusion, and bugs caused >> by this migration, so: >> >> - If you have questions or trouble with the new *workflow*, please >>either email or [...] > > Another question. > > What's the plan to replace "Core Work" views and tickets? > > https://gitlab.tails.boum.org/tails/tails/-/issues?scope=all=%E2%9C%93=closed=%22Core+work+201%22 > > I see that other teams than UX and Technical Writing stopped using them > years ago, though I thought that it was still the somehow standard way > of giving transparency and accountability on the priorities of teams. > > I don't mind stopping using them myself if there's no plan for > replacement but I'm curious how other teams track their priorities. It > might be useful to avoid each team reinventing its own wheel and still > give some transparency and accountability. > > I guess that we can use Milestones but then, what do you do with tasks > that your team considers important but for which the team is lagging > behind in terms of capacity? > > - Using Milestones and postponing them for too long is not great. > - Relying on the Label "Core Work: $TEAM" might make it easier to loose > them from sight. Sorry for the noise, a few hours later I realized that the labels "Core Work: $TEAM" are enough to give transparency and accountability and Milestones to explicit short-term priorities. And that it was already documented on: https://tails.boum.org/contribute/working_together/GitLab/#core-work -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] how to replace "Core Work" views? [was: GitLab is now in production]
intrigeri: > Where to ask questions and report problems > == > > There are most certainly some rough edges, confusion, and bugs caused > by this migration, so: > > - If you have questions or trouble with the new *workflow*, please >either email or [...] Another question. What's the plan to replace "Core Work" views and tickets? https://gitlab.tails.boum.org/tails/tails/-/issues?scope=all=%E2%9C%93=closed=%22Core+work+201%22 I see that other teams than UX and Technical Writing stopped using them years ago, though I thought that it was still the somehow standard way of giving transparency and accountability on the priorities of teams. I don't mind stopping using them myself if there's no plan for replacement but I'm curious how other teams track their priorities. It might be useful to avoid each team reinventing its own wheel and still give some transparency and accountability. I guess that we can use Milestones but then, what do you do with tasks that your team considers important but for which the team is lagging behind in terms of capacity? - Using Milestones and postponing them for too long is not great. - Relying on the Label "Core Work: $TEAM" might make it easier to loose them from sight. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [Tails-project] Request for change in communication culture
intrigeri: > Sandro Knauß (2020-05-24): >> anonym wrote: >>> Let me first express the change we're seeking: when leaving a comment on a >>> ticket, consider it your responsibility that the right person(s) will read >>> it! If you don't @mention someone, you probably are failing this >>> responsibility! >> >> On the one side, yes doing @mention somone helps, so the person knows, that >> they should answer.That's why I propose, that we also add groups/function >> mentions like @ft, @sysadmin, @help desk... Than people outside the team can >> make sure, the other teams know about it and the teams itself can make sure, >> that there are shifts and forward issues to the correct person in their >> teams. >> This should reduce the informal hierarchies and give the teams to define >> their >> own shifts etc. > > I understand that at any given time, mentioning one such @role account > would notify the team member(s) who is currently on duty — as opposed > to every single member of the team. Is this what you're proposing? I don't think that hefee's proposal was specific about automating a single notification to the person on duty. Otherwise they might not have written "the teams itself can [...] forward issues to the correct person in their teams". > Assuming I got it right, I it a lot. I think this idea complements > nicely other tools that we either have already or that we would like > to have: > > - @group mentions: great for raising attention of *every* *single* >member of a team, which most of the time is not great IMO. > >I just documented this tool: > > https://gitlab.tails.boum.org/tails/tails/-/commit/49476de8863c91c5bf8feb2ab6056776149e8fa5 I understand that hefee was proposing this. > - "Core Work: $team" labels: it's rare that folks outside of a team >dare adding this label, which is a bold statement that essentially >means "I think X is your job"; I believe the tool you're proposing >would allow expressing a range of somewhat weaker >statements/questions, thus making it more likely that >non-team-members will dare using it, which sounds great. > > - Document who is on shift on a given team: on the one hand, I think >this would nicely complement your idea for matters that are not >worth tracking on GitLab (e.g. sometimes a 2 minutes chat on XMPP >saves lots of paperwork) > >https://gitlab.tails.boum.org/tails/tails/-/issues/17763 > > What do others think? I'm not in team that does shifts. But if I were, I think that receiving a few notifications even when I'm not on shift would give me some useful context about what's happening to the other person's shift. For example, I could give them relevant information about a previous shift or acquire knowledge that would be useful for a future shift. I feel like it would help share knowledge and avoid creating silos inside a team. As someone that asks questions to Help Desk, I think that I would always prefer asking my question to the whole group, assuming that the team is self-organized and that the person on shift has the responsibility to answer while leaving more opportunity for others to jump in, than to only ask it to the person on shifts. So, for my communication with Help Desk, I'm afraid that having @help_desk point to a single person on shift instead of everybody in the team might slow down my work and I'll probably fallback to explicitly mentioning everybody in the team. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Re-Introduction of I2P to Tails
Konrad Bächler: > we would like to help and work on the re-introduction of I2P into Tails. > We understood that there is a need for the re-introduction in the "Tails > way" (easy to maintain, as close as possible to Debian). Is this true - > or is I2P unwanted? :) Hi Konrad, thanks for proposing to contribute to Tails. Unfortunately, we lack good decision making processes in Tails to be able to give you a clear-cut answer. My personal opinion is that we shouldn't re-introduce I2P in Tails before they drastically increase their user base outside of Tails: https://gitlab.tails.boum.org/tails/tails/-/issues/12264 This thread is also where we should continue this discussion as GitLab is a better archive for these kind of things. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Lanzamiento de Wahay [was: Wahay Re: Tor Control Port in Tails]
Forwarded from global-so...@lists.torproject.org about the official launching of Wahay, discussed previously in this thread. Sounds like a perfect Friday afternoon activity in you're in the Americas :) Forwarded Message Subject: [global-south] Lanzamiento de Wahay viernes 5 de junio (was: Fwd: Wahay: Mumble + Onion Service) Date: Mon, 1 Jun 2020 10:43:06 -0500 From: Rafael Bonifaz To: global-so...@lists.torproject.org Hi, I would go in Spanish as this event is going to be in Spanish. At the end of the email I forward the email I send to tor-talk. Hola, este viernes a las 18h GMT -5 será el lanzamiento de Wahay. Este es un sistema seguro y autónomo de conferencias de audio que une el poder de Mumble con Tor. Es parecido a Zoom en el sentido en el que se puede crear una reunión y otras personas se suman a la misma. Por detrás Wahay es muy diferente, cuando alguien crea la reunión, se inicia un servidor de Mumble que se publica como servicio Onion a la red Tor. El link de la reunión es la url .onion a la que otras personas pueden sumarse. Evidentemente la experiencia de usuario también es diferente. Para empezar es solo conferencia de audio y la misma es más parecida a utilizar walkie talkie en el sentido de que una persona habla a la vez y configuramos Mumble para que funcione con push to talk y así evitar los problemas de eco. En resumen es un sistema seguro, autónomo y descentralizado para reuniones de audio virtual. Espero nos puedan acompañar este viernes: Fecha: Viernes 5 de junio Hora: 18h GMT -5 Lugar: https://www.youtube.com/watch?v=eUH0Wr5U1Ro Saludos, Rafael ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] GitLab is now in production
intrigeri: > To follow the transition instructions, see: > > https://tails.boum.org/contribute/working_together/GitLab/transition/ Very useful! The full list and the `git remote set-url` command is much easier that editing each .git/config file by hand as I've been doing during the week :) > Known issues > > > - Updates to repositories used to build our website (tails.git and >any of its underlay repositories, such as mirror-pool.git) are not >automatically propagated to our production website. Only sysadmins >can manually propagate such updates. > >So far I've been synchronizing tails.git's master branch to our >production website at least once a day. If you need anything beyond >that, ask me or tails-sysadm...@boum.org. Aaahhh! I've been wondering twice already whether the website was broken when my changes were not reflected :) > - Our translation platform is not integrated with GitLab yet. What are the practical implications of this? Strings are not automatically updated in Weblate and translations in Weblate are not automatically applied to the website? -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] BisQ on Tails
weather-bea...@autistici.org: > Hi folks > > Thanks for the awesome job you do! I have donated couple of times in > past as a sign of my appreciations for your efforts Thanks for that! :) > In case nobody has suggested yet, I would like to suggest that Bisq DEX > would be added to the list of programs when tails load. I am not tech > savvy, so I am not sure how to install it separatelly I don't think that Bisq DEX has been suggested yet. We have a FAQ about adding new applications to Tails and I think that Bisq DEX fits into it: https://tails.boum.org/support/faq/#software I see that they distribute a Debian package on their website and that someone already started working on making it available in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772886 Once it's in Debian you will be able to install it in Tails using the Additional Software feature: https://tails.boum.org/doc/first_steps/persistence/configure/#additional_software Cheers, -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Request for change in communication culture
I'm moving this discussion to tails-project@ and quoting your fully because not all core contributors (starting with paid workers) are subscribed to tails-dev@ while we have a check list item to make sure that they are all subscribed at least to tails-project@. For example most of the Help Desk is not subscribed to tails-dev@ and it's been particularly complicated for me to get their attention on Redmine and mentions helped. anonym: > Hi! > > Let me first express the change we're seeking: when leaving a comment on a > ticket, consider it your responsibility that the right person(s) will read > it! If you don't @mention someone, you probably are failing this > responsibility! I've also realized pretty late that mentioning people on Redmine A LOT was useful and needed. I started doing it pretty consistently and it works! So I fully support your proposal. > [Note that @mentioning works in both Redmine and GitLab, and this proposal is > meant for both.] > > So far we have been relying on one person subscribing to all Redmine changes > and constantly following up on new comments and notifying the right people so > they are not "lost into the void". This is not sustainable (and IIRC GitLab > does not support subscribing to everything?) so we need to distribute this > work. > > To me it makes most sense to put this responsibility on the poster, at least > among us regular-ish contributors that are expected to have read the > contributor's docs -- new (or "drive-by") contributors cannot be expected to > have done this, and will be dealt with differently, some how. > > In practice this means you should do the following when leaving a comment: > > 1. Figure out who you want to read the comment! A good resource for this is: > >https://tails.boum.org/contribute/#mentors Note that this list is unmaintained and outdated and we have plans to get rid of it: https://redmine.tails.boum.org/code/issues/17076 >If you have trouble finding who to @mention, please mention @anonym and > I'll try to help! > > 2. Is this person already the assignee of the ticket you are posting to? If > so they will be notified any way, so we don't necessarily have to spam them > further by @mentioning them. But please err on the side of over-using > @mentions rather than under-using them! :) Did you check that assignees actually receive ALL comments on their tickets? I didn't check but I'm not sure. > 3. Otherwise, just add a @mention (or several, if you think several people > could be interested in this comment) somewhere in your comment. intrigeri told me that he was not sure whether it worked to add several mentions on the same line. I didn't check, but since then I stopped writing: @some1 @some2 And always write: @some1 @some2 > 4. Post! > > What are your thoughts on this? I know this proposal isn't 100% bullet proof, > it's more of a necessary reaction to the fact that we won't have a person > doing all this work for us any longer. > > Personally I think there might be a few cases when the above rule doesn't > apply, e.g. if you just want to add some piece of info to a ticket no one is > working on, just to make sure it is available to whoever might work on it in > the distant future. Not sure how to formalize a rule around this, but > remember: "please err on the side of over-using @mentions rather than > under-using them". > > Related to all this, if you need a technical rubber-duck, try talking to me > (e.g. by private email or pinging me on XMPP)! If I cannot outright help you > directly, I most likely can find someone who is better suited to help. > > Cheers! -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [Tails-news] Job offer: Technical writer
Summary === Tails, a portable operating system that protects privacy and helps avoid censorship, is looking for a technical writing consultant to strengthen our Technical Writing team. The Technical Writing team is responsible for writing our user documentation, support pages, and release notes. Complete job offer: https://tails.boum.org/jobs/technical_writer/ About Tails === Tails is a non-profit organization whose mission is to empower people worldwide by giving out an operating system that protects from surveillance and censorship. We make digital security tools accessible to everyone, whenever they need it: activists, journalists, freedom fighters, and ultimately, you, whenever you need extra privacy in this digital world. The Tails project was started in 2009 and has now more than 30 000 daily users. Read more about our mission and values: https://tails.boum.org/contribute/mission/ Details === Role description As a technical writer working for Tails, you will: - Update our user documentation to changes in Tails: new features, smaller updates, and changes in the included software. - Improve our support pages to answer frequent questions and document known issues and workarounds. - Redact release notes to describe the changes in new versions of Tails and how they affect users. - Communicate with our engineers, UX designer, and help desk to get a detailed understanding of the topic and discuss priorities. - Help our UX designer write text for user interfaces. - Apply, maintain, and improve our writing style guide. - Improve the structure and information architecture of our user documentation and support pages. You will be part of the Technical Writing team and work with 2 other technical writers to decide priorities, assign tasks, and review each other's work. You and your team will be responsible to self-organize your work and time with the project's priorities in mind. You will work remotely and use mostly asynchronous communication channels (email and bug tracker) to work with your team and other people in the project, who live in different time zones and have various degrees of involvement. We also use Jabber/XMPP and voice calls for synchronous communication. You will be part of the Tails community, which includes paid workers and volunteer contributors. Together, we are in charge of maintaining not only an operating system but also the good health of the community. Together, we continuously discuss and improve various social and organizational aspects of the Tails project. We will meet in person at least once a year during the annual gathering of all regular Tails contributors (usually in Europe). You will have the opportunity to represent Tails in other international events, if you want to. Qualifications -- - If you are part of a group that is under-represented in Free and Open Source Software communities, we particularly encourage you to apply. We acknowledge that our community is not as diverse as we would like it to be. We understand that we are part of the problem. We want to be part of the solution. - You can dedicate between 10 and 20 hours to Tails every month. - Experience working in technical writing of software documentation. - Good written skills in English. Most of our documentation was not written by native speakers, therefore being an English native speaker is a plus but not a requirement. - Some experience adapting your writing style to the context and the audience. For example, using plain language, writing for the web techniques, or technical communication style guides. - Some experience using Linux. - Interest in how people in a team organize their work and communicate about it, share their needs and feelings, make decisions, and share responsibilities. Optional skills --- Additionally, we would love it if you have: - Experience with some of the tools of docs as code workflows: * Issue trackers, for example GitHub, GitLab, or Redmine * Version-control software, for example Git, Subversion, or Mercurial * Plain text markup, for example Markdown or Textile * Static site generators, for example Hugo, Jekyll, or Sphinx - Experience participating in Open Source, Free Software, Internet freedom communities, or digital privacy tools. - Basic knowledge of web technologies: HTML, CSS, JavaScript, etc. How to apply Send an email to sajol...@pimienta.org. Include as much of the following information as you want. All items are optional: - CV - Feel free to not include your legal name, gender, or photo in your CV. - Links to your personal website, portfolio, or sample work - References Mention the name of the job offer clearly in the body of your email. ___ amnesia-news mailing list amnesia-n...@boum.org https://www.autistici.org/mailman/listinfo/amnesia-news To unsubscribe from this list, send
Re: [Tails-dev] DKIM signature on ta...@boum.org is broken
Hi Sebastian, Thanks for let us know about your problem. I'm forwarding this to our sysadmins. Sebastian Nielsen via Tails-dev: > For the news message that was just sent, contains the following error: > > > > X-DKIM-Signature: invalid (invalid); pubkey_unavailable > > > > So I checked, the DKIM signature on that mail is: > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boum.org; > > s=stigmate; t=1588739219; > > > bh=43TDf5u3GKyDCUmyWWeuZNuNlwELkA2LRuma+NqPLH4=; > > > h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: > > > List-Post:List-Help:List-Subscribe:Reply-To:From; > > > b=PiqFQ3DtTN2FUWgEkjXqPn17T65auUAugD+CpLojiO2QgMSLITauXEWxtpGGQ/T0S > > > QdJtjKCQc14EoCpdgGI8TZ0H4wDo5hmhYQosZlnN0r2a7WR730bG+sEGAVhIK0neVG > > KVlObvReR6KCTcD0c8dcPyX+SbbhbrVk8EbYq6WE= > > > > Means that stigmate._domainkey.boum.org should return a pubkey: > > > > root@sebastian-desktop:~# dig TXT stigmate._domainkey.boum.org > > > > ; <<>> DiG 9.16.1-Ubuntu <<>> TXT stigmate._domainkey.boum.org > > ;; global options: +cmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58784 > > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 > > > > ;; OPT PSEUDOSECTION: > > ; EDNS: version: 0, flags:; udp: 4096 > > ;; QUESTION SECTION: > > ;stigmate._domainkey.boum.org. IN TXT > > > > ;; AUTHORITY SECTION: > > boum.org. 3179 IN SOA ns1-v6.investici.org. > hostmaster > > .boum.org. > 1579558432 43200 3600 2419200 3600 > > > > ;; Query time: 0 msec > > ;; SERVER: 192.168.1.1#53(192.168.1.1) > > ;; WHEN: ons maj 06 06:34:08 CEST 2020 > > ;; MSG SIZE rcvd: 121 > > > > root@sebastian-desktop:~# > > > > > > Yep, I got your SOA record back, meaning there is no TXT record for > stigmate._domainkey.boum.org > > > > > > Maybe you should fix that? > > > > Best regards, Sebastian Nielsen > > > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. > -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Wahay Re: Tor Control Port in Tails
Rafael Bonifaz: > El 12/3/20 a las 23:34, sajolida escribió: >> sajolida: >>> Rafael Bonifaz: >>>> Last time I wrote to this list was related to the Mumble + Tails >>>> scripts. Here in CAD we have been working on GUI client that >>>> integrates Mumble and Tor Onion Service. The GUI is very simple you can >>>> host meetings and join meetings. >> >> [...] >> >> Tonight I tested Wahay and it's pretty cool! I also discovered that the >> Mumble UI has been seriously revamped in Buster and doesn't show the >> dreaded audio settings anymore. Yay! >> >> In attachments some screenshots of Wahay in action. > > Well there is work to be done and bugs to be fix. So please if you can > help us test it it would be great. > >> I think that we should seriously consider including it in Tails :) > > That sounds awesome!!! I think that the next steps should be: - For you to have it included in Debian. I see that you already build Debian packages, so that's a great first step. I know practically nothing about the process to get it included in Debian but we have many Debian developers at Tails, so hopefully someone can help you if needed. - For us to test Wahay more thoroughly. I'd like to test it for some of our internal meetings :) >> Good job Rafael! > > Actually, the job was done by my colleagues at CAD. Sure. Good job CAD! :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Do you read the changelog?
intrigeri: > From the information consumer's perspective, different folks > apparently want/need access to 2 different kinds of information: > > - the "why": what the fixed problem was Let's keep in mind that release notes are also here to solve precisely this concern. When I write them, my work is to filter out things that I deem unimportant to our users. The changelog includes more changes than the release notes but they shouldn't matter to our users. They could matter to auditors or developers. Also, most of the time, the changelog only describes what changed and less and less *why* it was changed. For example, when writing the release notes, it's my work to understand the *why* of a change and how it impacts users. Most of the time this information is not in the changelog. For example, first line: "Upgrade Tor Browser to 9.0.7-build1" is the *what* but has no info regarding the *why* and the impact on users. > - the "how": how exactly the problem was fixed > > From the information production perspective, we have 2 sources of > information, that may both include one, or the other, kind of > information folks want/need access to: > > - The changelog is generated from commit messages, that sometimes >document the problem the commit fixes, and sometimes only document >how said commit fixes the problem (with a link to the issue that >itself presumably documents the problem). > > - For user-facing problems, our issue titles are generally focused on >documenting what the problem is; while for lower-level aspects, our >issue titles are often about the solution. I expect we'll see the >same for MR titles unless we formalize something else. Yep. > This diversity of inputs + diversity of desired outputs makes it hard > to design a simple, automated, one-size-fits-all solution. > So I'll now zoom into practical use cases: > >> A. 1 technical users reads the changelog "to determine […] what impact >>the change might have to me in regards how I use Tails" > > I understand this is about the "how". > > I believe that the sort of Tails usage that requires such a deep > understanding of the system, beyond what's in the release notes, > qualifies as "expert usage", which is not our primary focus. > So I propose we don't include (A) in our list of requirements here. Agreed. Even power users should have enough with the release notes. Auditors should be able to navigate a raw list of tickets and commits. > This being said, I believe that my proposal for (C) below mostly > addresses this. > >> B. 3 technical users / occasional contributors read the changelog, to >>learn and/or out of curiosity > > This could be a mix of "why" and "how". > > Similarly to (A), I propose we don't focus on this here, but I believe > that my proposal for (C) below mostly addresses this. > >> C. 2 contributors check it out occasionally, as a single place that >>exposes the history of changes we've released > > This is about the "how", the "why", and the "when". > > Zooming further into what we heard about (C), the changelog address > these needs: > > C.1 Need more details than what the release notes include, > i.e. the "how" information > > C.2 Need easy access to the aggregated information across multiple > releases > > Here's something I believe would address these 2 needs: > > - Write a program that fetches from GitLab the list of issues and MRs >closed by a specified set of releases, and presents them together, >grouped by milestone, via 1 single user operation (C.2). > > - And for C.1, sometimes issue/MR titles don't include this >information, but commit messages do. So this program could have >a mode in which, for each MR, it displays the corresponding >commit messages. > > I suspect this program exists already. If not, it should be pretty > cheap to write (modulo perhaps some issue <-> MR matching and > de-duplication, if we feel fancy). > > Once we have this program, it becomes very cheap for the RM to paste > its output as-is in the changelog file, and/or for us to publish this > information over HTTPS somewhere (so one can click on links to go > explore issues/MRs/commits further). > > This would solve 90% of my use case and I know how to deal via Git > with the remaining 10%. > > Muri, would this be good enough for you? > >> D. sajolida uses it when writing release notes but it's insufficient >>and he could probably do as good with Redmine only, with some >>caveats (might be a bit slower, might need more clarification fr
Re: [Tails-dev] [Tails-ux] Tails Greeter settings
intrigeri: > sajolida (2020-02-25): >> Surprisingly, it's not even clear to me what the implications of the >> Language and Region settings can be on privacy. So I'm moving the >> discussion to tails-dev@boum.org in order to ask our fellow developers. > > First, most, if not all, exploited applications have access to > locale configuration. > > Wrt. network fingerprinting: > > - We have to assume that some applications may expose the system's >locale configuration as part of their network activity. > > - For Tor Browser and Thunderbird, our configuration tries to avoid >this (best effort) but it's impossible to prove we did not >miss anything. > > Wrt. local storage: > > - If an adversary can read the content of the persistent storage, I'm >pretty sure that the locale configuration can be easily inferred >from that. > > - If/once we allow persisting the locale in cleartext on the system >partition, this information will be available to an adversary >who seizes the Tails device. Thanks for the technical details! So it will really not be easy to explain practical the implications in a simple way. I stored this info on #17532 but I won't make it part of our priorities right now because the cost/benefit is really not clear to me. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Control Port in Tails
Rafael Bonifaz: > I would also like to register to the mailing list, but can't find how to > do it. https://www.autistici.org/mailman/listinfo/tails-dev -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tails 4.5 release and testing schedule
Cyril Brulebois: > This is a major release, so it will be preceded by a release candidate > somewhen late March. The details regarding the exact timing of the RC > still need to be discussed (in an upcoming RM meeting). Let us know once you decided so we can merge stuff in time. I hope we'll get at least #17136, which will be pretty exciting! > To be frank, > it's a bit scary for me as it'll be the very first one (hopefully with > some hand-holding if required). > > Manual testers, please report whether you are available for testing on > 2020-04-07 (and possibly the day before) to me privately. Isn't there a round of manual tests on the RC as well? > - 4.4 was a bit hard on the coordination side as Tor Browser was >published rather late compared to the usual timing (that can be the >weekend prior, or at least the day before the scheduled date for the >Tails release), that's why we had to shift as well… > - We plan to talk with Tor people to see how we can improve our working >together and avoid a similar problem in the future (by getting at >least a little more communication going). > - Many thanks to the 4.4 testers for their flexibility! I hope it wasn't too hard on you either. At least for me, extra flexibility aside, it's good to see that we sometimes postpone releases for a few days when needed. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Tor Control Port in Tails
Rafael Bonifaz: > Hello, Hola! @tails-dev: Rafael is not subscribed to tails-dev@ so we should keep him in Cc: when answering. @Rafael: See anonym's answer from March 7 regarding the control port: https://lists.autistici.org/message/20200307.121724.5b28fe26.en.html > Last time I wrote to this list was related to the Mumble + Tails > scripts. Here in CAD we have been working on GUI client that > integrates Mumble and Tor Onion Service. The GUI is very simple you can > host meetings and join meetings. > > At the moment we have a client that works in most modern Linux > distributions and you can see the source[2]. > > We also have a website, where you can download the binaries (of course > that website needs a lot of work)[3]. This sounds super cool! I really want to give it a try. I'm swamped with billion things (as always) so it might take a while but I'll get to it. One of my main concern with Mumble is the UX of the client itself, especially the audio settings; on which the quality of the call depends a lot. It's unclear from your website if you replaced the UI of the Mumble client or if you use the upstream one. Since you mention usability as one of your goal on the GitHub page, I wonder if you concur with my analysis and what's your approach to that. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Broken link in 4.2.2 release notes
xin: > Hello, the link [[security > level|doc/anonymous_internet/Tor_Browser.html#security_level]] is > broken, maybe it works without the ".html". xin always on the lookout! Good catch! Fixed in e703bfb93b. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Do you read the changelog?
Michael Gerstacker via Tails-dev: >> Hi, Tails contributors, >> >> - Do you read the changelog at all? > > If thats the always-broken-in-two-halfs link in the email after an release > then yes sometimes when i am not too lazy to manually put the link together. Indeed, it's broken. See attachment. I never noticed it before. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Reminder about our Code of Conduct
Cyril Brulebois: >> Like the technical community as a whole, the Tails team and community is >> made up of a mixture of people from all over the world, working on every >> aspect of the mission including mentorship, teaching, and >> ^^^ >> connecting people. The commitments that we stand by as a community are >> described in the >> [[Tails Social Contract|contribute/working_together/social_contract]]. >> >> Diversity is one of our huge strengths, but it can also lead to >> communication issues and unhappiness. To that end, we have a few ground >> rules that we ask people to adhere to when they're participating within >> this community and project. These rules apply equally to founders, >> mentors and those seeking help and guidance. >> >> This isn't an exhaustive list of things that you can't do. Rather, take >> it in the spirit in which it's intended a guide to make it >> ^^^ >> easier to enrich all of us and the technical communities in which we >> participate. > > Only skimmed over the mail but HTML entities were obvious… maybe fix for next > time? :) Oops! To prevent this in the future, I changed these HTML entities with the real thing in the Markdown source. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Fwd: Converting ikiwiki to hugo
intrigeri: > Hi, > > Birger Schacht: >> Ah, I didn't even know moving away from ikiwiki was considered. > > I can't say it's being very actively considered but it's been in the > back of the mind of a few of us for a while. I believe the only place > where it's vaguely tracked and where information in being shared on > this topic currently is: > > https://tails.boum.org/blueprint/replace_ikiwiki/ Yup. I would love to move to a more flexible and more actively developed Static Site Generator (SSG). Last time I did some research, I focused on the translation mechanism. We have a decent PO plugin in ikiwiki but I couldn't find anything as good in other popular SSGs. Maybe things have changed since then. Alternatively, the idea that Ulrike mentioned in her first email would be to push all the translation logic to the translation platform (Weblate): feed Weblate with Markdown files in English and get back Markdown files in other languages. Then we might not need any translation plugin in the SSG itself. Last time I checked, both ideas required pretty heavy development either on the SSG or on Weblate. I think that this is what blocking us from considering moving out of ikiwiki for real. But it's super interesting to see your experiment. It means that, once we have a solution for the translations, the rest might not be that far away :) -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Mumble and Tails in Scripts
intrigeri: > sajolida: >> Ok. As it would be the first time that we're doing something like this, >> I'd like to have the opinion of more people on that. >> >> The proposal is to create a page about Mumble from Tails in the >> "Advanced topics" section, including a copy of the scripts. I would do >> some minimal reformatting on the original blog posts. >> >> Having this on the website only is less work (and commitment) than >> adding the scripts to Tails itself and could serve as a way of knowing >> how popular such a solution would be. >> >> Regarding maintenance, I would leave it to Rafael and CAD. If the >> scripts ever happen to be badly broken and unmaintained, by then we'll >> have a better idea of how popular they are so we can evaluate the >> cost/benefit of fixing them and possibly drop them. >> >> We should also have someone from Tails review the code of the scripts >> for security (and maybe nothing else for now). > > Sounds good to me! I created #17245 to track this but I don't have the skills to do it myself. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
