Could you add to /Documentation please plus whenever any other links would be useful to that page?
Yes, fixed thank you.
Also:
1. Can he/she also fix the “NO TITLE” problem that doesn’t work on various pages e.g. →
http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Security_in_Real_World
(which reminds me, if they can’t fix it can we redirect that page to a page called “Protection Against Real World Attacks” instead? Or, in desperation I’ll create a new page & copy all text across & fix links because it is annoying to look at that title year after year… 
)
2. Re: the white space after linking to external resources - it is only
a problem when the resource pointed to is a PDF. Maybe hutch knows why? It happens in both normal linking, and in blockquotes (the white space)
Another nit, that template:Tunnel Support has {{VPN documentation}} at the bottom, but no text appears? It just leads to white space - so can we delete or fix that?
Yes, on second thought I realize it is best to generally avoid all the political stuff in wiki (forums maybe ok) because it a rabbit hole that never ends. Wiki-wise, we can just refer to external refs (reputable) in the main and just briefly address the issue if necessary.
Thanks 0brand. Don’t spend too much time on the forums. Your skills are better used for technical fixes and documentation IMO.
Forums are a black hole where users will suck you dry, with many (most?) failing to do basic wiki searches, because if they had the answers would have already been discovered.
1 Like
I’m starting to realize that. Most of my time has been going to support instead of wiki edits. To be honest its is a little frustrating when its only a matter of a (user) using a search engine to find the answer. Is it because of their inexperience - I was there not to long ago - or because they don’t want to spend the time. Free support principle applies for either case but I don’t mind spending a few extra minutes for the former. But I think I’ve been holding their hands a little to much. They have to learn to be self sufficient.
3 Likes
I’m working on Forcing onion wiki. Has anyone else copied over the https Everywhere rulesets from the new file location (old VM to new VM). There are those weird characters and I want to be sure no one has had any problems with copy rulesets to new VM.
The new file location:
~/.tb/tor-browser/Browser/TorBrowser/Data/Browser/profile.default/storage-sync.sqlite
2 Likes
torjunkie:
Yes, fixed thank you.
Also:
1. Can he/she also fix the “NO TITLE” problem that doesn’t work on various pages e.g. →
Will look into it. Part of ⚓ T868 mediawiki fixes #2.
(which reminds me, if they can’t fix it can we redirect that page to a page called “Protection Against Real World Attacks” instead? Or, in desperation I’ll create a new page & copy all text across & fix links because it is annoying to look at that title year after year…
Agreed. That page should be renamed either way.
2. Re: the white space after linking to external resources - it is only
a problem when the resource pointed to is a PDF. Maybe hutch knows why? It happens in both normal linking, and in blockquotes (the white space)
Crucial helpful “it is only a problem when the resource pointed to is a
PDF”. Maybe content security policy related. Could you raise in that
thread please?
Another nit, that template:Tunnel Support has {{VPN documentation}} at the bottom, but no text appears? It just leads to white space - so can we delete or fix that?
Deleted.
1 Like
Already did yesterday. It’s included in a ML message to the Debian bugtracker
1 Like
We don’t necessarily need an external references always. We can also be self-referential sometimes. If you tested it and wrote so in the forums, then that is a reference. Even just <ref>As tested by...</ref> would do as long we can confirm who made the edit.
Added links to bug reports as references now.
In Onionizing Repositories#Debian_Templates users are instructed to add debian.list to Qubes Debian templates. When following these instructions and running apt-get update I get this output.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list.d/debian.list:5
This happens on Debian templates that are up to date but not on Debian templates that have never been updated.
I also have Qubes repos onionized but I don’t think that is the issue.
1 Like
Not sure - haven’t played there for a while. Hopefully you work it out!
All operating system update stuff fixed (very messy), plus millions of lines of spacing fixes etc.
(We really should have a separate Qubes update template of its own & not “borrow” the non-Qubes-Whonix one, but anyway)
1. DispVM half page half done (we need to watch the {{whonix-ws}} and {{whonix-gw}} code isn’t broken on multiple pages - I already discovered it in AppArmor section and DispVMs, so no doubt it is elsewhere.
2. Template: {{Tor_Browser_Remove_Proxy_Settings}} causes massive whitespace because of the last footnote in it for some reason.
E.g. see footnote 32 (or 33) here:
3. In this section, can’t we just delete the bottom two parts which say the same thing as the first section?
http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/About#Debian_Hosts
4. On this page below, you have: {{Template:Qubes}}, but nothing seems to appear? Delete or fix to get rid of whitespace etc?
http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Qubes/Update
Where do we report it? I’d like this fixed before they disappear for good (if possible).
2 Likes
That is the issue. Users can’t use both Qubes onion repos and Debian onions. If repos configured like that I’m not sure if any Qubes-Debian packages would be pulled from the http// URI instead of Debian onions? Likely if onions where down.
1 Like
torjunkie:
2. Template: {{Tor_Browser_Remove_Proxy_Settings}} causes massive whitespace because of the last footnote in it for some reason.
E.g. see footnote 32 (or 33) here:
Can’t see issue.
3. In this section, can’t we just delete the bottom two parts which say the same thing as the first section?
http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/About#Debian_Hosts
I am not sure if we compress to much information into one sentence that
could lead to ever fewer users understanding this. While the sentence
may be technically concise, correct, it may still be less understood
than with more redundancy?
Made some changes:
new Debian release: “may”, “depending on deprecation notice” (in theory,
if I can’t make it work on the new release of Debian for some reason or
can’t switch myself for some reason then actually until that time
oldstable has to be used.)
new Whonix release: “will” (because then it’s clear that there is a new
Whonix release that is functional)
sub headline Debian Hosts, sub sub headline “New Whonix, Debian, Qubes
or Qubes-Whonix Release”, here I actually made a mistake. Debian hosts
have nothing to do with Qubes or Qubes-Whonix. Rewritten.
4. On this page below, you have: {{Template:Qubes}}, but nothing seems to appear? Delete or fix to get rid of whitespace etc?
Yes, legacy. Delete please.
Where do we report it? I’d like this fixed before they disappear for good (if possible).
1 Like
Why not?
If repos configured like that I’m not sure if any Qubes-Debian packages would be pulled from the http// URI instead of Debian onions? Likely if onions where down.
I may be misunderstanding something but any onion should be possible to combine with any other onion. When using onions exclusively and Debian onion is offline then one would miss out on Debian package upgrades for sure.
1. Connection schemes and chain descriptions still right in this section?
(confusing to me as they don’t seem consistent, but I’m no expert)
2. Is this line still correct in processor microcode updates template? (just checking)
It is unnecessary to apply these updates in standard Non-Qubes-Whonix and Qubes-Whonix guest VMs, as they do not have the ability to alter the microcode. However, processor microcode updates should always be applied on the host operating system (for processors by Intel or AMD) [3] and baremetal configurations like Physical Isolation. [4]
Everyone happy with the micro-edits? 
Pretty well ready to smash email section down of the ToC now. And there is stuff that really needs work in those sections, to put it mildly.
1 Like
torjunkie:
1. Connection schemes and chain descriptions still right in this section?
(confusing to me as they don’t seem consistent, but I’m no expert)
Looks ok.
2. Is this line still correct in processor microcode updates template? (just checking)
It is unnecessary to apply these updates in standard Non-Qubes-Whonix and Qubes-Whonix guest VMs, as they do not have the ability to alter the microcode. However, processor microcode updates should always be applied on the host operating system (for processors by Intel or AMD) [3] and baremetal configurations like Physical Isolation. [4]
That is correct.
Everyone happy with the micro-edits?
Happy as always.
1 Like
__NOTITLE__ is broken on a few pages (https://www.whonix.org/w/index.php?search=__NOTITLE__). Planing to repair soonish.
1 Like
__NOTITLE__ should be transformed into a wiki template {{notitle}}. (https://www.whonix.org/wiki/Template:notitle) (If someone gets to it before me.) Mass replace doens’t work.
Empty template (just nothing but a page instead of non-exiting page) for now. Later I’ll add the wiki markup there for HideTitle as soon as I can make that work.
Template {{{title}}} - Whonix seems to work now reliably everywhere. Example:
{{Title|title=
Ways To Contribute
}}
1 Like
Great!
Firejail 0.9.56 still crashes Tor Browser in whonix. “Gah, Tab crashed” etc.
If you can get it working put basic steps here and I’ll add to the wiki.
2 Likes
__NOTITLE__ is not fixable unfortunately. Removed.
Title template however seems to be reliable in all cases. Please use it whenever useful.
{{Title|title=
Ways To Contribute
}}
1 Like
already reported that:-
2 Likes
That protocol-leak-protection page has some good info. @Patrick
I think it should be tidied up, all the long code stuff etc split off into a separate page, and then put somewhere with pride on the main page. Right now it is in a dusty back room & probably not getting many eyeballs.
I’ve been using DisplayTitle to fix a ton of pages. Looks good.
1 Like