Matthew Finkel: > On Fri, Aug 23, 2019 at 7:59 PM <g80vmgm...@riseup.net> wrote: >> panina: >>> On 7/31/19 5:35 PM, 'awokd' via qubes-users wrote: >>>> panina: >>>>> Hello. >>>>> >>>>> >>>>> I've been looking for how to fix some bad default settings in the whonix >>>>> tor browser. Namely, they removed NoScript from the toolbar, so that the >>>>> NoScript cannot be used as intended. >>>>> >>>>> Since it's not adviced (and not easily possible) to start the browser in >>>>> the template, I have to do this manually each time I start a whonix dvm. >>>>> Since this is cumbersome, I'm not using the NoScript plugin as intended. >>>>> >>>>> Does anyone know how to get this plugin into the toolbar for each dvm? I >>>>> realize that this is a Whonix issue, but all of the affected users are >>>>> on this list... >>>> >>>> You might be able to hack it like in 14- >>>> https://forums.whonix.org/t/how-do-i-customise-tor-browser-in-a-whonix-templatebased-dvm-in-whonix-14/5580/27. >>>> Note it may compromise anonymity by making your browser unique or at >>>> least less generic. >>>> >>> >>> Can't seem to get this working. I get confused by how the dvm's work, >>> and am not succeeding in starting any applications in the dvm template. >>> >>> >>> >>> On 8/9/19 9:05 AM, Patrick Schleizer wrote: >>>>> panina: >>>>> Namely, they removed NoScript from the toolbar, so that the >>>>> NoScript cannot be used as intended. >>>> >>>> >>>> We did not. Decision by upstream, The Tor Project. >>>> >>>> >>> https://forums.whonix.org/t/workstation-15-dropped-both-noscript-and-https/7733 >>> >>> Thanks, duly noted. Is there any chance to get them to add a setting for >>> this? Or re-think their decision? >>> >>> <3 >>> /panina >>> >> >>> Thanks, duly noted. Is there any chance to get them to add a setting for >>> this? Or re-think their decision? >> >> Please see: >> https://trac.torproject.org/projects/tor/ticket/30600 >> https://trac.torproject.org/projects/tor/ticket/30570 >> >> TL;DR The TBB developers pushed out some half-baked changes that >> compromise UX, are hostile to the idea of reverting those changes, and, >> three months later, apparently have zero interest in fully baking those >> changes. >> >> ¯\_(ツ)_/¯ > > That's a little harsh, isn't it? Saying there is no interest is > ignoring the fact that Tor Browser is maintained by a team of 10 > people for four different operating systems. Tor Browser is useless > (and actively harmful) if users are confused about which settings they > should change (due to careful design choices) and which settings they > shouldn't change. The Noscript and https-everywhere buttons on the > toolbar allowed people to tweak the settings easily, and this was not > something a normal user should do. If someone really needs to change > these settings, then they can go through a more complicated procedure > for accomplishing that. > > The team will finish implementing this, but (in particular) the > highest priority task right now is migrating the Tor Browser patches > and build system from Firefox 60esr to 68esr within the next few > weeks. >
We're getting off-topic here, and I also don't wish to bring Tor Project politics into this list. That said: > That's a little harsh, isn't it? Saying there is no interest is > ignoring the fact that Tor Browser is maintained by a team of 10 > people for four different operating systems. No, it is frankly not harsh enough. Available developer time to finish implementing the half-baked changes is irrelevant. The correct way to do this would have been to wait until the changes were fully baked (i.e. until Proposal 101 was fully implemented, including per-site security settings), rather than half-assing them, pushing them out the door, then three months later thinking about maybe getting around to finishing up sometime in the future after higher priority tasks are done. > [...] this was not something a normal user should do. Well, I don't know how things *should* be, but an awful lot of TBB users have found these controls essential. I personally have had to explain to multiple non-technical TBB users in meatspace how to re-access the NoScript widget, which they all have found essential to using TBB. Regardless of available developer time and priorities, breaking a feature many users find essential without any warning, not giving any explanation of how to access that essential feature, and then forgetting about un-breaking that feature for months is simply piss-poor project management. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/27bec4ce-662a-fa69-3902-7dc1f5016cc4%40riseup.net.
