As we all know, cybersecurity is a completely f-d up mess, which endangers everyone. And as we all agree, it is frustrating that no quick solution is in sight. But presumably we would also all agree that TP cannot fail to issue emergency patches when emergencies arise which a patch can ameliorate.

in Russia banned VPN, Tor, anonymizers.Under the law potentially all proxy and VPN-services, as well as anonymous networks Tor, I2P and Freenet, fall. Their owners are invited to restrict access to sites that are on the roster of prohibited websites of Roskomnadzor.To track anonymizers, Tor and VPN-services that provide access to blocked sites in Russia, there will be FSB officers and police.

Net neutrality ends today in the U.S. I've known about Tor Browser for a few years, and I'm aware it's effective with bypassing firewalls. It seems more likely however, that ISPs would throttle traffic.
My question is: Will Tor Browser make throttled websites load any faster?

Good question. I don't think anyone yet knows how this will play out, not even the FCC b-ds who killed NN, not the ISPs, not the EFF, nobody. We'll just have to see.

Several US states are seeking to rush onto the books their own net neutrality laws. WA state got there first, just ahead of FCC's action, so arguably NN is still the law of the land in one US state. That might not seem to matter much, except that Amazon hosts many sites and I think those servers might be subject to WA law, at least in principle. FCC will doubtless challenge state laws and the whole mess will surely eventually wind up in the lap of the seriously flawed SCOTUS gods.

I don't think the individual's speed will be throttled...it'll be the websites that are throttled if they don't pay for faster service. That means sites who are already running on a shoe string won't be able to compete with those that have more resources. If you visit sites that can't pay for the faster speed, it's likely that your connection/user experience will be slow or maybe non-existent. At any rate, it's not a good thing. I'm not certain if the Tor Project will be one of those sites.

>>> unexpected error-try later
It is important : my openic dns seem block this website (for commenting only).
The team of Tor should contact openic for a better compatibility && it is not because they pass the test that they are working properly configured or allowing a comment using 'cookie' only.

Recent Updates

There's a new alpha release available for download. If you build Tor from source, you can download the source code for 0.4.0.1-alpha from the usual place on the website. Packages should be available over the coming weeks, with a new alpha Tor Browser release likely by the end of the month.

Remember, this is an alpha release: you should only run this if you'd like to find and report more bugs than usual.

Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It introduces improved features for power and bandwidth conservation, more accurate reporting of bootstrap progress for user interfaces, and an experimental backend for an exciting new adaptive padding feature. There is also the usual assortment of bugfixes and minor features, all described below.

Changes in version 0.4.0.1-alpha - 2019-01-18

Major features (battery management, client, dormant mode):

When Tor is running as a client, and it is unused for a long time, it can now enter a "dormant" state. When Tor is dormant, it avoids network and CPU activity until it is reawoken either by a user request or by a controller command. For more information, see the configuration options starting with "Dormant". Implements tickets 2149 and 28335.

The client's memory of whether it is "dormant", and how long it has spent idle, persists across invocations. Implements ticket 28624.

There is a DormantOnFirstStartup option that integrators can use if they expect that in many cases, Tor will be installed but not used.

Major features (bootstrap reporting):

When reporting bootstrap progress, report the first connection uniformly, regardless of whether it's a connection for building application circuits. This allows finer-grained reporting of early progress than previously possible, with the improvements of ticket 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.

When reporting bootstrap progress, treat connecting to a proxy or pluggable transport as separate from having successfully used that proxy or pluggable transport to connect to a relay. Closes tickets 27100 and 28884.

Tor 0.3.5.7 is the first stable release in its series; it includes compilation and portability fixes, and a fix for a severe problem affecting directory caches. Tor 0.3.4.10 and 0.3.3.11 are also released today; please see the official announcements for those releases if you are tracking older stable versions.

The Tor 0.3.5 series includes several new features and performance improvements, including client authorization for v3 onion services, cleanups to bootstrap reporting, support for improved bandwidth- measurement tools, experimental support for NSS in place of OpenSSL, and much more. It also begins a full reorganization of Tor's code layout, for improved modularity and maintainability in the future. Finally, there is the usual set of performance improvements and bugfixes that we try to do in every release series.

There are a couple of changes in the 0.3.5 that may affect compatibility. First, the default version for newly created onion services is now v3. Use the HiddenServiceVersion option if you want to override this. Second, some log messages related to bootstrapping have changed; if you use stem, you may need to update to the latest version so it will recognize them.

We have designated 0.3.5 as a "long-term support" (LTS) series: we will continue to patch major bugs in typical configurations of 0.3.5 until at least 1 Feb 2022. (We do not plan to provide long-term support for embedding, Rust support, NSS support, running a directory authority, or unsupported platforms. For these, you will need to stick with the latest stable release.)

Below are the changes since 0.3.5.6-rc. For a complete list of changes since 0.3.4.9, see the ReleaseNotes file.

Changes in version 0.3.5.7 - 2019-01-07

Major bugfixes (relay, directory):

Always reactivate linked connections in the main loop so long as any linked connection has been active. Previously, connections serving directory information wouldn't get reactivated after the first chunk of data was sent (usually 32KB), which would prevent clients from bootstrapping. Fixes bug 28912; bugfix on 0.3.4.1-alpha. Patch by "cypherpunks3".