It looks really good now. I like how Fedora stands out from the rest of the Qubes templates.
This part is what my eyes focus on:
Note: Updating Fedora templates exclusively over Onion Services is not possible.
Good idea (whonix repo template)
I like this idea (merge). That way there are two sections i.e. Qubes and Non-Qubes.
Each platform (Fedora, Debian ) can have an template instructing users to inspect/review repository config file. And what to look for when doing so. I think that would be a good idea.
I’m up to the task
Edit: Someone took care of the nits for me. I suspect torjunkie
Made a few changes to onionizing repositories. Merging the Onionizing Tor project updates didn’t work out. It just didn’t look right regardless of how it was formatted. I’m going to move to Installing Newer Tor Versions (tomorrow). Also working on the templates for inspecting the repository files. We currently have instructions to “test” repositories after onionizing, but beginners likely don’t know what that means.
@HulaHoop i cant install or do any step with your installation instructions. Please whenever you are free update your instructions to be fitting with Debian Buster as a host.
The leaks mentioned in Filesharing and Torrenting only apply when used outside of Whonix. At the moment it sounds like Whonix users would be affected too. Can we point that out without making it an invitation?
--baseuri is unfortunately not implemented. I didn’t have ideas how to do it back then. Perhaps standardize instructions and have user do it manually similar to all other instructions?
The issue of burdensome and repetitive instructions on a single page regarding the different ways to edit a text file was discussed before. I was recently surprised to find this taking place even on the KVM installation instructions page.
I would like to suggest the following be added to the top of every guide-style page that requires editing text files:
Editing text files
In this guide [/page] we use nano [optional: link to a very quick guide, added below] as a text editor. If you prefer a graphical editor use mousepad (on XFCE) or kwrite (on KDE).
For example, instead of:
nano filename [or always sudo nano?]
use
kdesudo mousepad filename
Then, all the instructions throughout the page will only use nano instead of the repeated clause "if you are using… then… ".
To make things more friendly I wrote the following “very quick guide” mentioned above (should appear on a dedicated page, containing only that):
Nano is a popular and simple text editor in Linux. Basic usage:
Open the file for editing by typing in terminal:
nano filename
If the file was created by root, we need to use sudo to get proper privileges:
sudo nano filename
If you try to edit a file that does not exist, nano will create the file.
Essential keyboard shortcuts:
To save: CTRL-O
To Exit: CTRL-X
Moving the cursor is done using the arrow keys or Page Up and Page Down. Mouse click does not move the cursor.
More keyboard shortcuts:
To delete a full line: move to that line, then press CTRL-K
To search: press CTRL-W, then type the text you wish to find, then ENTER.
Formatting can be improved of course.
More can be added, but I think it’s unnecessary. Better keep it short. Even the search function is probably not required for the tasks users are expected to follow throughout the guides. We may add:
