More complex instructions for Debian users for adding the Whonix repository. I.e. they need to install apt-transport-tor and also keep in mind Hide Tor use from the Internet Service Provider too? Maybe not a good reason?
How much is it worth connecting to Whonix repositories over Tor when all other of users repositories are probably still using plain http over clearnet? Maybe not a good reason?
tor+http://deb.whonix.org could be mentioned but I was wondering if that is not what the user is looking for in that moment, thus bouncing.
The fact that safer defaults are not widely used is not a good argument IMO. It protects against version leak and user targetting also from additional attention that user John Doe knows about Whonix and is a user.
If we want to declutter the main Documentation page further, what would work nicely would be shifting everything currently with “Advanced:…” to a sub-page.
When you look at most of those sections, they are either advanced or (more often IMO) just obscure activities e.g. nested virtualization, building from source, unsupported virtualizers and other random things. Probably 1/100 users do most of that, so I agree what one of the commentators on that page, it should be simplified.
So if we have an /wiki/Advanced/Documentation page I think all the following stuff should go there:
Advanced: Esoteric Issues
Advanced: File Transfers and SSH / SSHFS
Advanced: Miscellaneous
Advanced: Platform Support
Advanced: Tor
Advanced: Whonix-specific
(And we can also lose the ‘Advanced’ part in each title. If any stuff in those sections is either a) not advanced, or b) common, then simply link to it in the main ToC page instead. Definite rationalization required, otherwise the ToC looks overwhelming).
Appendix should probably stay on the main Documentation page as is.
Would be much cleaner, and less intimidating for ‘normal’ users i.e. 98% of people.
Since you agree then I’ll shift all those “Advanced” bits and pieces to an “Advanced Documentation” page. Stop me now if you don’t want that…
Looks good. I see adw made some edits too - thanks adw
Agree that simple Qs in forums like this indicate documentation needs to fill that gap - backing up what people were saying about quick start guides etc. ‘Normal’ users have very simple expectations in the main.
The reason I didn’t do that originally was because of the small size of the text/content attached to Multiple Whonix-Gateways i.e. would have been a tiny page? You still want to do that?
I guess we have to in this case? Multiple-Whonix-Workstation’s didn’t fit multiple Whonix-Gateway’s or TemplateVMs. So if we split it, we should split for good for consistency.
i have delete video & audio editing tools because they were KDE based. anyone has better alternatives? (better to be DE free dependencies or Xfce based)
For pre-installation it’s nice if we can reasonably stick with XFCE only (reasons of disk space and maybe some other reasons). However, generally it’s not a problem if users mix packages of GTK, QT, LXDE, Gnome, Mate, KDE and whatever. If some user wants for example kwave, there is no reason to discourage that. So if there are no replacements for those, we can just keep the kde ones there. Or should the kde ones (just speaking theoretical) be better than anything else, another reason to leave them there.
Yes. I was considering it. When there is autologin it would also apply to:
physical isolation (autologin there would be surely criticized as security issue)
Non-Qubes-Whonix XFCE version: autologin for desktop is obvious and can be disabled but tty1 autologin would be a bad surprise to those who disable autologin for the desktop.
Is it worth it? Are those who get confused by host login the same users who accidentally downloaded the CLI rather than XFCE version and those users would be stranded after autologin anyhow?
Not easy to enable autologin for some versions only. Might require a new package which gets installed on CLI only.
