Live data from Hacker News

uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

discourse.mozilla.org

131–140 of 340 posts

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#131

Earlier quoted context omitted.

It's pretty insane how much your browser knows about you: http://webkay.robinlinus.com/ There's another one I can't find, but it writes out things like "user moved mouse to x,y. User has been idle for 10 seconds, page lost focus, page gained focus" .. kinda creepy how much is available to the Javascript engine.

You must be talking about clickclickclick.click And thanks for the new novelty website bookmark :D

http://imgur.com/6ep0YnW

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#132
post #129

Earlier quoted context omitted.

This actually made me try switching to Firefox again. There's some minor things missing, but for the most part all the features I want are there.

Same for me. I fired up Firefox for the first time in years and it works great. The hardest part to get used to is their super-weird hamburger menu layout.

This menu is changing for Firefox 57. It will have a more "normal" menu soon. You can see it today by installing Nightly Firefox.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#133

Huh. These actually sound like good arguments to switch to Firefox, arguments I've never heard before until now.

One thing I learned several years ago when I decided to jump on the bandwagon and try Chrome was that Chrome was unable to safely block javascript the way NoScript does because the plugin framework doesn't allow a plugin to block Javascript before it's loaded. So all the noscript equivalent for Chrome could offer was to block Javascript after it had loaded. Which seemed unreal and pointless. So I stayed on Firefox. B…

I found uMatrix to be an adequate substitute once figured out (http://adamantine.me/index.php/2015/11/18/umatrix-desperatel...)

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#134
Couldn't the devtools listener shenanigans be solved merely by putting a "pause" button in the browser chrome (possibly through an extension)? Browsers are already throttling CPU usage when the tab isn't visible, so it doesn't seem like it would be too difficult to just throttle to 0 with a toggle.

Even better-- have the pause button in devtools window, "pause" by default when you open devtools, and then unpause once something gets mutated/re-layout'd.

I guess you'd still need to protect the devtools shortcut key so that any DOM shenanigans are guaranteed to get invoked after the devtools listener. But browsers already have all kinds of crazy edge-cases in the name of security (e.g., no manual triggering of menu). Keeping polymorphic worms from corrupting the devtools state seems rather important by comparison.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#135

I am considering going back to FF, but it seems FIDO U2F still isn't done completely and the U2F Extension for FF is not working anymore since the WebExtension switch. Please correct me if missed something, but i think i have to hold off for a little bit longer.

The current plan has U2F shipping as soon as Firefox 57.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#136

Firefox is coming back, finally- I think their market share is at the bottom and we'll see a big uptake over the next couple of years.

Pay attention to this project and volunteer if you wish - https://voice.mozilla.org/ - it may be a big thing for Mozilla

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#137
post #106

Earlier quoted context omitted.

It's not entirely unreasonable. We use software because it's useful. If you make it so secure that it is no longer useful, what have you got left? In the case of Firefox extensions, I'm aware of the risks of the old model, but the fact is that the only observable difference it has made to me so far is that when I accidentally hit back on a page with an unsubmitted form the other day I lost about 20 minutes' worth of…

If you hit Backspace in error, you can disable the “Go Back” action associated with the backspace key using about:config like so: browser.backspace_action = 2 Read [1] for more instructions. If you explicitly used the mouse to click the Back button, I am sorry for the time you lost. 1. http://kb.mozillazine.org/Browser.backspace_action

Allow me to introduce the Thinkpad X61 keyboard:

http://i.imgur.com/JitlIPa.jpg

That's a dedicated "go back" button between up arrow and right ctrl.

My webmail is unusable without Lazarus. I've taken to composing in emacs and pasting the result into forms.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#138

I am considering going back to FF, but it seems FIDO U2F still isn't done completely and the U2F Extension for FF is not working anymore since the WebExtension switch. Please correct me if missed something, but i think i have to hold off for a little bit longer.

Just today someone posted that they're about to get U2F in the main browser:

https://bugzilla.mozilla.org/show_bug.cgi?id=1245527

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#139
post #69

Earlier quoted context omitted.

I always hit DDG first then if the results aren't great just append the Google bang (!g) in the DDG search field to get an unbubbled goog search. The DDG bang system is one of its best features in my mind. https://duckduckgo.com/bang

How often do you end up at Google though; a few years back I tried DDG for a couple of months but ended up basically always doing !g and so went back to Google. Might be time for another go?

I use !s. Redirects it to Startpage instead. Google results, but it acts as a proxy.

On the homepage, https://www.startpage.com/, at the bottom it lists the security part a bit more.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#140

I am considering going back to FF, but it seems FIDO U2F still isn't done completely and the U2F Extension for FF is not working anymore since the WebExtension switch. Please correct me if missed something, but i think i have to hold off for a little bit longer.

Just today someone posted that they're about to get U2F in the main browser: https://bugzilla.mozilla.org/show_bug.cgi?id=1245527

Actually, here's the U2F patch https://bugzilla.mozilla.org/show_bug.cgi?id=1388843
Post reply on HN