News for hackers. Stuff that matters.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by StavrosK on Thursday May 30, 2019 @08:31AM (#20050471)
Please switch to Firefox, it's better:

https://www.mozilla.org/en-US/firefox/new/?redirect_source=f...

If your favorite feature works slightly worse in Firefox, consider that its interests align with yours, unlike Google's.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by ptero on Thursday May 30, 2019 @09:04AM (#20050724)
I personally switched from Chrome to Firefox, but I think we need more well running browsers, not less. Even most well-meaning organizations get many have strange ideas and can use "my way or the highway" liberally when competition does not produce other palatable options. Thus while I did switch I hope Google steps back from this heavy handed approach (and more valid options get developed by other groups and companies). My 2c.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by StavrosK on Thursday May 30, 2019 @09:13AM (#20050803)
We do need more well-running browsers, which means browsers with roughly equal market share. I'm not comfortable with an 80/20 situation, but even then I'd prefer Firefox to be the 80 instead of Chrome.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by ptero on Thursday May 30, 2019 @09:35AM (#20050945)
I would also prefer an 80/20 split to be in the Firefox favor.

However, I do not see that "many well-running" means "roughly equal market share". Browsers are software and thus easy to replicate. And due to the huge market (> 1B users), even 1% market penetration is meaningful -- that is provides enough users to stay alive and develop.

Linux, text editors, many email clients, etc. were originally hackers toys, not grandma's tools and as such had a small (but vocal and dedicated) user base that cared about functionality and not market penetration. But once certain functionality threshold has been reached a lot of people were willing to wrap the core in a grandma-style interface. It could work for new browsers, too -- the main threat is not low user base, but being eaten by a large corp once it is capable enough to be a potential threat. My 2c.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by pmlnr on Thursday May 30, 2019 @08:44AM (#20050547)
Maybe it's time for a new firefox ad in the Times.

https://blog.mozilla.org/press/2004/12/mozilla-foundation-pl...

Re:Chrome extension manifest v3 proposal: comment from uBloc... by diegof79 on Thursday May 30, 2019 @09:21AM (#20050847)
Firefox is great, and since the Quantum release is getting better on each release.

My 2 reasons to keep coming back to Chrome for Mac are the battery life and DevTools. Firefox is very power hungry in macOS, there are a few bugs reported about that (see [1] and related tickets). The best in terms of energy consumption is Safari, but the dev tools are terrible.

So each time that I switch my default browser to Firefox or Safari, I end switching back to Chrome a week after for one of those two reasons :(

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042

Re:Chrome extension manifest v3 proposal: comment from uBloc... by dylan604 on Thursday May 30, 2019 @09:42AM (#20051015)
What differences are you seeing in the two dev tools? I use both browsers, and as far as what I’m using the dev tools for, they both give me the info I’m looking to find.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by diegof79 on Thursday May 30, 2019 @10:53AM (#20051800)
Feature-wise most of the dev tools are similar across browsers (in particular Firefox and Chome are similar), but the things that keep me coming back to Chrome DevTools are:

- Console. Both Safari and Firefox put the input at the bottom so it's like a command line. Chrome puts it at the top, so it feels more like a code editor. It's a small difference, but that combined with auto-complete and the preview of results makes Chrome console better for me.

- Editing of CSS properties. Chrome and Firefox are similar in this area, but Safari is terrible (it improved in Safari 12, but it has some interaction annoyances when you edit rules). Since I work doing UX, I do dev mostly for prototyping. Tweaking CSS in the dev tools is something that I do often.

- Display of computed CSS properties, Chrome displays the "trail" of a property in the computed view. (Note: I just discovered that Safari added that as an experimental feature in the latest versions).

- Source Maps: My experience with source maps was much better in Chrome DevTools. For example, Chrome shows the files mapped by a bundle in the source tree, while Safari shows the bundle and only displays the source map when you hit a breakpoint (if there is a setting for that I couldn't find it).

- Accessibility tree is also a great feature of Chrome DevTools.

- For small (simple) projects, the ability to link a file system workspace is also great (although useless for projects that use a lot of JS tooling).

Re:Chrome extension manifest v3 proposal: comment from uBloc... by dylan604 on Thursday May 30, 2019 @12:14PM (#20052697)
Okay, this makes a little more sense, as you seem to be mainly mentioning differences with Safari. I haven't broken into the Safari dev tools just yet, although I have a feeling that is around the corner since I just read that to see what iOS Safari is doing you use the Safari dev tools when connected via cable. And the rabbit hole just goes deeper. It's turtles all the way down I guess.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by joombaga on Thursday May 30, 2019 @11:59AM (#20052504)
Input is at the top of the console for me in Firefox on macOS.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by ubermonkey on Thursday May 30, 2019 @09:04AM (#20050721)
This.

I'm on OSX. My primary browser is Safari, but I typically had Chrome running, too.

Something pushed me over the edge last year, and I switched to Firefox for exactly this reason. There was a time when FF was lagging badly, but that all seems to be over now.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by theandrewbailey on Thursday May 30, 2019 @09:24AM (#20050864)
I might be the only person in the world who never stopped using Firefox as a primary browser (since ~2005).
Re:Chrome extension manifest v3 proposal: comment from uBloc... by oftenwrong on Thursday May 30, 2019 @10:05AM (#20051209)
I have used it as my main browser since it was called "Firebird". For me, its pros have always outweighed its cons, even during the long period in which its stability/performance/memory-usage was inferior to its competitors.

Some nostalgia:

https://upload.wikimedia.org/wikipedia/commons/a/a1/Mozilla_...

Re:Chrome extension manifest v3 proposal: comment from uBloc... by cesarb on Thursday May 30, 2019 @11:19AM (#20052101)
I can top that: not only I used it as my main browser while it was still called "Firebird", but I also used as my main browser its predecessor Mozilla back when its version numbers were single-digit "milestones". For those who didn't experience these early versions: they crashed a lot, and opening more than one window (there were no tabs back then) increased the chances of a crash so much that after 2-3 windows having it crash was almost certain. (Before that, I had used Netscape, starting with Netscape 2.)
Re:Chrome extension manifest v3 proposal: comment from uBloc... by jackewiehose on Thursday May 30, 2019 @10:15AM (#20051319)
You are not. For some reason chrome always felt much more sluggish than firefox (on linux as well as on windows).

Maybe it's the kind of websites I visit? I don't know...

Re:Chrome extension manifest v3 proposal: comment from uBloc... by SquareWheel on Thursday May 30, 2019 @08:57AM (#20050643)
It's not better, but it's still very good. And it's getting better every day. Both Chrome and Firefox are extremely impressive browsers.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by aoeuidiue on Thursday May 30, 2019 @08:59AM (#20050673)
While I want to, performance is always an issue and has been for a period of years, 5+ or more.

I'm talking my entire system gets taken out for minutes by one pages' shitty javascript. Even then, I'm not even sure if it's the pages fault or a plugin, or firefox itself.

Surely I'm not the exception to an application that everyone else seems to have no issue with?

Re:Chrome extension manifest v3 proposal: comment from uBloc... by CJefferson on Thursday May 30, 2019 @09:12AM (#20050791)
Honestly, something is up with your system if that is a regular occurrence in Firefox.

Try doing a full reset, delete all your configs and extensions. Then run plain Firefox with no extensions for a while, and see if that behaves well. If not, something serious is up and you should try reporting it to the Firefox bugzilla if you can repeat it.

If that works fine, something was up in your config, or extensions. Once I found someone had gone into the internal Firefox config settings and changes something years ago, forgotten it, and it was now causing serious performance problems.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by timw4mail on Thursday May 30, 2019 @09:26AM (#20050876)
Extensions/Addons are also running Javascript, so they can definitely be a factor in how responsive the browser is.

Chrome is slightly better at utilizing every computing resource available, but that also means that it is more resource-intensive.

Now, every once in a while, I do experience Firefox being unresponsive. Restarting the browser always fixes that, even with the same browsing session. I haven't experienced Firefox locking up the entire system, except with really low resource computers (like Netbooks, or < 4GB of Ram).

Re:Chrome extension manifest v3 proposal: comment from uBloc... by behnamoh on Thursday May 30, 2019 @09:06AM (#20050747)
Please define "better". I've used both Chrome and FF, and traditionally FF was more aimed at developers and heavy users. However, they lost that advantage over Chrome when their add-ons started to have forward compatibility issues.

Speaking of add-ons, I do miss FireBug. It was easy to find/define XPATHs by it (which is critical for web scraping). The new inspect element in FF just lacks that feature.

Just how GNU/Linux and macOS are traditionally more appealing to professionals and developers, FF should come to grips with targeting their own niche market. It's interesting how so many great ideas from these "niche" markets (e.g. Unix and Linux in the case of OSs) have surfaced in the more dominant, closed, commercial ones (i.e. Windows). If Mozilla want to really make the web a better place, they should know that by keeping their users happy (who are mostly developers), the ideas they put forth will sooner or later get spread in other browsers as well.

As another analogy, you might think about LISP and how the main ideas were later implemented in even the most imperative languages: although Lisp as we knew it is not dominant anymore, the ideas that made it different are still alive in Ruby, JS, etc.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by radcon on Thursday May 30, 2019 @08:52AM (#20050607)
I had already switched on PC because of Chrome's voracious appetite for RAM.

On mobile I made the switch to avoid AMP pages.

The list of reasons keeps growing...

[dead]
Re:Chrome extension manifest v3 proposal: comment from uBloc... by StavrosK on Thursday May 30, 2019 @08:56AM (#20050638)
> The rarely disclosed amounts in ballpark of tens of millions are being paid by Google on (somewhat) yearly basis. They call it donations but a few people see something else here.

They don't call it "donations", they call it "payment for having Google as the default search engine". This isn't even news.

> Need to push DRM under the table? No problem. HTTPS? No problem either

Yeah, God forbid websites deploy TLS.

What the hell is this comment?

Re:Chrome extension manifest v3 proposal: comment from uBloc... by dang on Thursday May 30, 2019 @03:51PM (#20055249)
Please don't break the site guidelines regardless of how wrong some other comment is.

https://news.ycombinator.com/newsguidelines.html

Re:Chrome extension manifest v3 proposal: comment from uBloc... by snazz on Thursday May 30, 2019 @08:59AM (#20050674)
I’d personally rather have optional DRM and more Firefox users than no DRM and more Chrome users. Encryption decreases the spying power that ISPs have, which can’t be a bad thing.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by garganzol on Thursday May 30, 2019 @09:02AM (#20050693)
Please consider to take a wider look. Once TLS is everywhere, it's much harder to cut the ads from pages in a centralized fashion. Another point is that data trends and statistics remain exclusively at the hands of a Big Co. Win-win for Google.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by StavrosK on Thursday May 30, 2019 @09:06AM (#20050740)
I'm not sure what you mean. TLS is everywhere now, and uBlock origin works fine. I don't know what you mean about "the hands of a big Co" either. I think you gravely misunderstand how TLS works.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by garganzol on Thursday May 30, 2019 @09:14AM (#20050808)
Don't get me wrong, I'm all in for TLS. But consider this asymmetry: with encryption, all data remains at hands of a Big Co as nobody else can access it. An exclusive access to data at large is a powerful weapon fueling inequality, wars and monopolies.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by StavrosK on Thursday May 30, 2019 @09:20AM (#20050846)
Yeah, this doesn't make any sense, I'm sorry. You seem to not know how encryption works, or please go into some detail on why you think this is.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by garganzol on Thursday May 30, 2019 @09:42AM (#20051019)
Simple. TLS ensures data integrity and protects it from eavesdropping. Here is a conversation between Alice and Bob:

Alice <-TLS-> Bob

In this scheme, only Alice and Bob can know the details of a conversation.

Another conversation with Kevin reveals another scheme:

Kevin <-TLS-> Bob

See the pattern? Both Alice and Kevin shared their information with Bob.

Now imagine that Bob is a Big Co. And it has hundreds of millions conversations every day.

In this way, Bob is able to gather big data about all the persons he ever talked to. And because TLS only protects data in transit, Bob now has the privilege of an exclusive access to the gathered data en masse. No other person in the world would be able to access it as Bob claims a total ownership on it.

What Bob would do with data? It's an open question.

One scenario is to build a graph of relations between the persons and then target them with ads. Another scenario is to target all the persons who ever dared to show signs of non-conformity and disagreement and put them to jail. The possibilities are endless and nobody would be able to prove anything because TLS helped Bob to deter all the eavesdroppers. And now he has the ultimate power to rule the world.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by StavrosK on Thursday May 30, 2019 @09:46AM (#20051052)
Oh I see, so you believe random third parties like your ISP and whoever runs the routers reading your passwords and data in transit is a good thing?
Re:Chrome extension manifest v3 proposal: comment from uBloc... by garganzol on Thursday May 30, 2019 @10:05AM (#20051214)
Passwords/control panels should be secure from eavesdropping. TLS perfectly covers this as for now.

In order to keep the society from diverging into rampant monopolization and totalitarization, I would propose a modification to TLS that would allow to optionally turn off encryption while preserving data integrity guarantees.

News outlets/public resources/Youtube and the whole society would all benefit from using such form of TLS.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by cytzol on Thursday May 30, 2019 @10:37AM (#20051582)
> In order to keep the society from diverging into rampant monopolization and totalitarization, I would propose a modification to TLS that would allow to optionally turn off encryption while preserving data integrity guarantees.

You can already use TLS with the null cypher to get the data integrity guarantees you want.

Apparently Microsoft (back in 2016) did this to for Windows Update: https://twitter.com/SwiftOnSecurity/status/74533301869746995...

Re:Chrome extension manifest v3 proposal: comment from uBloc... by ignaloidas on Thursday May 30, 2019 @10:11AM (#20051282)
So you think that it is better to everyone to know everyone's conversations rather than everyone to know just their conversations, because someone could have more conversations and that is not fair. Now that is actually dangerous, because if someone wants to misuse your data, you'd rather them have only your conversation to them, not your conversations to everyone.
Re:Chrome extension manifest v3 proposal: comment from uBloc... by Dylan16807 on Thursday May 30, 2019 @02:14PM (#20054253)
In general it's only the large and powerful organizations that have the ability to eavesdrop in the first place! Removing the encryption doesn't help anyone directly.

I'm pretty sure you can publish your TLS transcripts, too. This ensures that when you want to share this data with someone they'll actually get it, and allows you to keep it private when you want.

Re:Chrome extension manifest v3 proposal: comment from uBloc... by ceejayoz on Thursday May 30, 2019 @09:14AM (#20050806)
> Once TLS is everywhere, it's much harder to cut the ads from pages in a centralized fashion.

Sure, but the reverse is true, too. ISPs have already been abusing NXDOMAIN DNS queries to serve ads for years.