Converting the HTTPS-Everywhere user rules sqlite3 binary file to plain text file for editing, then back to a binary file looked promising in the beginning but turned out to be a dead end. If anyone would like a go at it or could give some advice. The issue is in the last step. Somehow the file is changed when converting from plaintext file back to a sqlite3 binary file
1. Install sqlite
sudo apt-get install sqlite3
2. Dump the https-everywhere rules data base to a plain text file.
For most pages {{Footer}} sorts out licensing perfectly.
{{License_Amnesia {{FULLPAGENAME}}}} is only required for a few pages imported from Tails a few years ago. Only pages that already have that which then get moved elsewhere may require it.
Pages that have it such as /Documentation also contains something like:
<!--
The Whonix Documentation wiki page is forked from the Tails Documentation page, from this exact source <http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc.mdwn;hb=920ef988d1e8ed552f4e97d1423e0038e1bfbbf4>.
-->
Since years passed since then the link broke. Keep it anyhow as is. Not worth the effort. Copyright is being complied with. Still has enough information if someone wanted to dig. No one interested in this.
If we move content from such a page elsewhere we’d hack to check how the Tails page looked back then or looks now to see if we have to re-add that notice.
While we are at it… Does bitmessage belong to Email Overview? I mean shout it be on the Email Overview page? It’s not listed on Whonix ™ Documentation which might make it hard to find. I am writing might since I don’t really know how someone who’s interested in Whonix and bitmessage would search and then find or fail to find.
More generally asking… Would you think the wiki gets more usable by moving more things into dedicated wiki pages?
Like on the Instant Messenger Chat page. HexChat has its own page while Gajim and others do not.
Good work 0brand Those who have technical skills and can write sensibly are rare.
I put all the BitMessage stuff on its own page (which it deserves & because of length) and put you as maintainer. Hope that is okay. Did some small edits too (I think your last two recorded edits were missed by me e.g. pic update etc).
On second thought, its not a big enough deal to worry about.
A little more cleaning up to do on the Email page and it will be done.
Considering I quite literally knew nothing and couldn’t write worth shit when I starting visiting Whonix.org. My tech skill and writing ability can be attributed to having great teachers. Some of the best IMO
I see the Dev/Mixmaster page has most of the proper installation / config etc settings, so why don’t I use all the good info from that page, merge with the main Mixmaster page, then you can later delete that Dev page?
I presume those instructions are still functional? Never played with it before.
Also, I gather all Re-mailers are not traditional email, so I put them under “alternatives” (since that is how they are described on the Email Overview page). Better split on ToC that way.
Basically all the wiki up to Anonymous Email section is tight now, so would like to keep editing from there down. Exception:
“Testers” page - maybe 0brand and I can work through all the missing steps / instructions?
Also, we should finish off the DispVM page as a priority, as it is a bit of a mess.
I can do that Maybe make instructions a little easier for less experienced users to follow. The more testers we have all the better for development.
Um…yes it was me I put a lot of hard work into that page
I’ll start on the Qubes/DispVM first since it only has a few TODOs to complete.
I’ve also been working on sys-whonix DispVMs with persistent entry guards. Created using the instructions you and I authored for Service VMs (Qubes Docs). I’m hesitant to post until I have testing/research completed. In the past I posted DispVM hacks that were not safe to use but some forum members still insisted on using and even recommending to other users after Patrick asked then not to.
I see the Dev/Mixmaster page has most of the proper installation / config etc settings, so why don’t I use all the good info from that page, merge with the main Mixmaster page, then you can later delete that Dev page?
Dev/Mixmaster is just dev notes. /Mixmaster should be ok as is content wise.
I presume those instructions are still functional? Never played with it before.
Also, I gather all Re-mailers are not traditional email, so I put them under “alternatives” (since that is how they are described on the Email Overview page). Better split on ToC that way.
Basically all the wiki up to Anonymous Email section is tight now, so would like to keep editing from there down. Exception:
Noted - footer is enough.
I’m pressed for time atm so I’ll re-edit a little later on.
Those who have technical skills and can write sensibly are rare.
I put a lot of hard work into that page