Absolutely love this release. Glad to see the red screen of death is gone. Interface on Android looks wonderful too (love the Material You icon).
A request for future releases: it would be nice to have uBO installed, just like in the Mullvad Browser. There are some cases where TOR is significantly better than MB + VPN, so having a content blocker is helpful when we need to use some sites with Javascript selectively enabled.
How am I supposed to make each website remember its zoom level or launch tor windows maximized?
Yes, I know, anonymity and stuff, but I have to use Tor as my main browser since the government has cracked down on VPNs (not to mention you canât trust random ones that happen to (barely) work), and I have slight disability with my hand and problem with eyesight.
Having to constantly maximize and set the zoom level is not easy for me.
I know its perhaps more of a niche system but please do include TBA in the discussion so the whole Tor ecosystem can collectively advance as one. Thanks
Love the new release, especially the 1400 x 900 windows. Why not 1600 x 900 though? Oh well.
Also, upgrading from 12.5.6 I got a double tab about connecting to the Tor network (I have Connect automatically ticked on in the Preferences). Could not actually connect but clicking the New Identity button solved it, dunno if itâs a bug or something related to my setup.
0xc0000005 is a very generic error (access violation).
In earlier messages you mentioned youâre on ARM. In case it could be a problem with translation from x86 to ARM.
At the moment we provide native ARM binaries only for macOS.
We donât have the hardware for testing with other operating systems and the amount of changes weâd need to do to our reproducible build system is unknown (and Mozilla doesnât even mention AArch64+mingw).
The problems you wrote in the screenshot below is that tor.exe doesnât start.
Iâd expect you could have the same error if you try to start it outside the browser.
Actually, Iâd say even desktop hasnât been discussed yet.
We briefly talked about considering it, but as far as I know, it isnât officially a 13.5 thing for Tor Browser, yet. If we decide weâll do it, weâll update the related issue.
In general, we still havenât a list for 13.5. We only have some musts/priorities, e.g., connection assist for Android, and stuff we wanted in 13.0 but that didnât make into it.
I canât reproduce this. Does it Could you please try with a fresh installation and in case open an issue with steps to reproduce?
One of the tabs was probably the update notes, itâs normal when you update .
That option is ignored after a connection failure is detected, to avoid making users end up in a loop where they constantly get error messages.
New identity shouldnât be related (the only tor-related things it does is sending SIGNAL NEWNYM over the control port).
Please let us know if you manage to find a way to consistently reproduce this problem.
If Iâm not wrong, there isnât exactly a portable version of TOR per se. If you download the installer on to a USB and install it on the USB itself, then it becomes a portable download. If you download it on your PC and install it, it installs in the PC. Remember, the TOR Browser is not like conventional apps (at least in Windows as far as I know). All the required files and modules are installed in a single folder which can be deleted if you want to remove the app (as opposed to a classic uninstall process).
Isnât this like using only circuits made of two nodes? Iâm not sure itâs a great idea.
So, the first request is very easy: hamburger menu â new Tor circuit for this site. Itâs always available, even for internal about:pages (maybe thatâs a little bug).
If keyboard is also fine, itâs Ctrl+Shift+L (on Linux, en-US; in general, we localize shortcuts, so you might have a different one).
For the request of displaying circuit display, I think we could also open an issue.
Let me find a vanilla bridge I could try.
To avoid any confusion: it was especially about the browser UI.
This is a great point and something Iâll be advocating for going forward â unless thereâs a platform-specific reason why we should deviate from providing parity-by-default.
However as @PieroV says we havenât reached a decision about this as of now, and it isnât officially on the roadmap yet.
Hey @eddlang, Iâm really sorry to hear about the accessibility issues youâre facing because of this change. Making it more difficult to use Tor Browser in a way that meets your needs was certainly not our intention, and I really appreciate you bringing this use-case to our attention.
Thank you everyone for the constructive feedback and bug reports in this thread, please keep them coming! Itâs also great to hear what youâre liking about the release too.
Thinking ahead to future releases, you may be interested in downloading Tor Browser Alpha and becoming an alpha tester to help us catch things earlier in the development process â however please make yourself aware of the risks first: