Long Wiki Edits Thread

Great! All very true. Yeah, let’s migrate the forum post to the wiki and replace my forum post with a wiki page.

Done.

Should “limitations on free speech” retain personal pronouns, “I” and “me” or should it be more generic?

1 Like

Warnings added.

1 Like

Removed from Connecting to Tor before a VPN. Reason: duplication. At the moment we are clearly saying on top of the page:

Before combining Tor with other tunnels, be sure to read and understand the risks!

So we don’t duplicate any warnings.

Also if we add it on one version (x over Tor vs Tor over x) it should be on both and not only on one of the two.

This is hopefully only temporary. Above is not a good style. I think users don’t like documentation for the thing they want to work on split among multiple pages. They want the exact thing they want to do all on one coherent page. This however would require a ton of new wiki templates which then get reused for the many combinations before/after Tor vs VPN vs proxy vs ssh. Perhaps not realistic? Too much work? That’s why above’s quote is stressed.

Could you please move to Combining Tunnels with Tor and rewrite from VPN to tunnel-link? Since it really applies to any kind of tunnel link.

Can be more generic if this can become a fully agreed Whonix team speech. Good idea.


Made more generic. Limitations on Free Speech on Whonix Website since applies to all, wiki, forums, comments, …

Limitations on Free Speech on Whonix Website is too specific for Wiki Comments Policy? Applies more generally. Own page?

I want to add Tariq’s advice on activity compartmentalizing per guard. What is the best page for this?

1 Like

That was still there so I removed it.

https://whonix.org/w/index.php?title=Tunnels/Connecting_to_Tor_before_a_VPN&oldid=40433&diff=cur

If you would like me to spend the time on this, i can do that. Might be worth it.

  • Easier to follow instruction = Less support requests.
  • Pages would be shorter. Maybe users would actually read the documentation?
    • Users might not even use a VPN? But not likely, it took me a while before I realized they were not required / not always necessary.

Needs to be done eventually why not start now?

Rewrote and removed duplicat. I think its a little clearer now?

https://whonix.org/w/index.php?title=Tunnels/Introduction&oldid=40435&diff=cur

Re: Limitations on free speech on whonix website. Yes, should have its own page. I can do that and migrate. Should also include these links?:

1 Like

Either:

2 Likes

The slash / would create a sub page.

Yay! :slight_smile:

(Well, daunting task. That’s why I never did it. Other things made me think:

  • Perhaps an automation script? As far as that is possible in a generic way?
  • Perhaps a user → Tor → VPN documentation without fail closed mechanism for circumvention only for easy of use?)

Oopsy

I could do that but I have a feeling I would be booted off the Whonix team and erased from the Whonix history books when you saw it. :slight_smile:

In all seriousness, it could get it done but its not something that you would be able to use. My bash skills are not that advanced.

That would be a good idea. Was reading an article (don’t remember where) but employees in big Chines telecom companies use VPNs to access twitter and other social media platforms that are censored. All they really need is something to circumvent the firewall. Maybe Failed close not always necessary?

1 Like

0brand:

Oopsy

I could do that but I have a feeling I would be booted off the Whonix team and erased from the Whonix history books when you saw it. :slight_smile:

In all seriousness, it could get it done but its not something that you would be able to use. My bash skills are not that advanced.

:slight_smile:

That would be a good idea. Was reading an article (don’t remember where) but employees in big Chines telecom companies use VPNs to access twitter and other social media platforms that are censored. All they really need is something to circumvent the firewall. Maybe Failed close not always necessary?

Yes. For some websites it’s easy. VPN = access. Tor = no access. No
other repercussions. Specifically to just get read access where Tor exit
relays are blocked to something one doesn’t have to go crazy about fail
closed mechanism.

1 Like

Removed limitations on free speech on Whonix website.

https://whonix.orghttps://www.whonix.org/w/index.php?title=Wiki_Comments_Policy&diff=40479&oldid=40439

Migrated to its own page.

https://www.whonix.org/w/index.php?title=Limitations_on_Free_Speech_on_Whonix_Website&oldid=40478&diff=cur

1 Like

Done. I tried to make it as simple as I can, but I don’t know how difficult it will be for beginners.

1 Like

Lost at hello:

  • multi-Workstation scenarios
  • snapshots
  • from a clean base
  • pristine Gateway snapshot

Yes it’s terrible I know, but I don’t know how to improve it. Should I just admit that it’s never going to be practical for beginners and forget it?

Do you understand it though or am the only one?

At maximum more technical users are reading and capable to use this. However these concepts (mentioned above) are not used elsewhere in wiki and even if they are the links are missing. Also I am nitpicky about terminology, for example multi-Workstation will be less understood then [[Mutliple Whonix-Workstation|Mutliple Whonix-Workstation]] which we use more or less consistent thorough the wiki. So all this needs is a nitpicky revision.

The difference between instructions that work for users, and instructions that don’t work for users.

old: How-to: Use Wickr Me in Whonix ™
new: How-to: Use Wickr Me in Whonix ™
diff: Wickr: Difference between revisions - Whonix

I tried rephrasing it into a somewhat less complicated way. Opinon?

1 Like

Got a bug report.

Thunderbird 60.4.0 is incompatible with Debian -- Error

Debian -- Details of package xul-ext-torbirdy in stretch-backports works.

Also the install torbirdy from torproject site vs Debian (backports) difference is not clear for users. The former looks much more involved and advantages of it are not immediately obvious if it is needed.

@tempest

  • Most Security Recommendations aren’t actionable. Split and move to Tor Onion Services - ADVANCED?
  • Under Tor Onion Services - EASY in sub chapter Introduction we mention lots of unique, interesting items but new reader would be lost at hello. Not really EASY. :wink: And someone who never heard of onion services wouldn’t get from the introduction that servers/websites/etc. can be run with it.

The provider used in encrypted email with thunderbird chapter vfemail.net might need to be replaced?

Happy New Year!

I hope all of you have thoroughly enjoyed your memembership!

As you may be aware, recently we were hit by another DDOS attack. Thanks to our friends at
New Continuum Data Centers, we were able to weather the attacks with minimal inteference. This latest
attack was against our incoming mail servers, which did cause some delays processing incoming email.
We’re actually in a really good position, technologically speaking, to diversify our incoming mail systems
across the globe - but we really need a healthy cash injection to get that going.

What that can do is provide upstream links that can be saturated in the event of an attack, without actually
affecting incoming deliveries OR access to your email.

If you haven’t already, please upgrade now to help us achieve this new redundancy goal. VFEmail Control Panel Login

Due to low “free to subscriber” conversions, we may be ending free registrations.

The cost to create a new Copper account
would be $1. Part of this POSSIBLE requirement is the amount of effort and costs involved in cleaning up spam, RBLs, and upstream
rejections at other providers. Another reason is our Ad revenue has dropped dramatically, while our site usage has increased.
I will be ‘massaging’ the ads to try and improve our revenue there, but we really need your support!

Thanks - wishing you all the best in 2019!

Rick Romero
VFEmail.net

@tempest

1 Like