HNHacker News
TopNewBestAskShowJobs

rhelmer

658 karma · joined May 14, 2010

submissionscomments
rhelmer··on Browsers, not apps, are the future of mobile
There is a design doc describing non-Web embedding for WASM:

https://github.com/WebAssembly/design/blob/master/NonWeb.md

That doesn't mention HTML but focuses on avoiding JS entirely, so presumably there'd be some more direct way to invoke the program (but don't take my word for it ;) )

rhelmer··on Firefox: Announcing Project Mortar
I managed to get this working as a WebExtension in Firefox (mostly just hacking around a few APIs that aren't ready in Firefox yet). Could be a path forward for folks that want to keep using pdf.js perhaps.
rhelmer··on “Our primary goal is to un-fork the Tor Browser”
That really should not be happening.

Are you clicking "Change Search Settings" in the search drop-down, and changing the "Default Search Engine" in the preferences (about:preferences#search) ?

rhelmer··on “Our primary goal is to un-fork the Tor Browser”
There are lots of great web browsers now, which is a huge improvement on the state of the world when Firefox 1.0 was released.

All major browsers today do share a huge problem - the web browser needs to be fast (performance and responsiveness are a Really Big Deal to people), and it also needs to be secure (people getting ransomware via the browser is Not OK with them). Privacy is a more nebulous topic, I agree.

One place where Mozilla has invested that can make a real difference there is with Rust and Servo.

A lot of the investments in Firefox that Mozilla makes are intended to help the web as a whole. Trying to standardize and expand on cross-browser extensions with WebExtensions is an example of this.

Coming back to the topic, while I agree that most people don't care about privacy online but there are some who do and Tor users almost certainly do. Bringing Tor's security and privacy improvements to Firefox is good for everyone, and some improvements help both performance/responsiveness and security (the recently-released and ongoing work from Mozilla on multiprocess and sandboxing is an example of this.)

rhelmer··on Mozilla Awards $585k to Nine Open Source Projects
> "If they spent allocated 5% of that revenue on Servo, they could hire 70 developers year round at $235,000 each to work on Servo full time, year-round."

Firefox is a shipping product and Servo is a research project.

Components from Servo are making their way to Firefox as both sides are ready, and parts of Firefox are being written/re-written in Rust as well:

https://wiki.mozilla.org/Oxidation

So over time it's certainly possible that more engineers will be allocated to Rust/Servo related projects, as they make their way into shipping products.

rhelmer··on Mozilla Awards $585k to Nine Open Source Projects
Mozilla Labs is no longer active. There is a Research group however: https://www.mozilla.org/en-US/research/

They work on Rust and Servo (among other things.)

rhelmer··on What’s Next for Multi-Process Firefox
Tab Groups was moved to an extension, and has had a lot of nice improvements: https://addons.mozilla.org/en-US/firefox/addon/tab-groups-pa...

A lot of folks use https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...

Personally I use separate windows for separate tasks, so I can close a whole window when I am done with something (research, work, tabs from HN, etc.)

rhelmer··on Malware in the browser: how you might get hacked by a Chrome extension
I don't think it's sleazy, while Mozilla does review all add-ons, it's hard to restrict what an extension right now since they can access internal APIs and there isn't really a permission system to speak of.

Additionally, JS is a dynamic language so it's difficult to provide adequate automated scanning for malicious intent. Even so, extension authors can be quite clever in how they hide malicious behavior, especially if there's financial reward involved.

WebExtensions (https://wiki.mozilla.org/WebExtensions) add a permission system, have a much smaller attack surface, and should help to alleviate this problem. This combined with automated scanning + human review and

For Chrome, I think Google prefers a combination of automated scanning and quick response, without upfront human review (based on https://static.googleusercontent.com/media/research.google.c...)

rhelmer··on Mozilla Fathom: Find meaning in the web
Standardization would be a useful outcome, having multiple implementations shipping is a prerequisite as I understand it - it's something Mozilla could participate in, along with other interested browser vendors.

There's a community group: https://www.w3.org/community/browserext/ but no WG yet as far as I can tell.

rhelmer··on Mozilla Fathom: Find meaning in the web
> Maybe I can convince someone to write something about it.

You should come chat in #webextensions, if we can identify where messaging is falling down and fix it this would be great!

I think one thing missing right now is having good "release criteria" for WebExtensions (like we did for e10s) - I don't think implementing every single API that's available to old-style extensions right now is a tractable problem (since it's "every internal API", all the way up to executing arbitrary commands).

rhelmer··on Mozilla Fathom: Find meaning in the web
WebExtensions are a superset of what Chrome does. Things like tree-style tabs will be possible in Firefox with the new extension system, for instance.

There are already several WebExtension APIs implemented that Firefox supports that Chrome does not, the difference now is that APIs are being built specifically for extension authors to use, rather than Firefox internals being directly accessible (which certainly allows you to modify anything, but is intractable to maintain backwards compat and secure).

Many authors of popular extensions are working on specifying and prototyping the APIs they need.

rhelmer··on Mozilla Fathom: Find meaning in the web
> Dropping XUL breaks backwards compatability and it seems Mozilla is willing to break it before they provide adequate replacement APIs

The problem is not XUL. Modifying HTML or XUL DOM via JS is roughly equivalent (setting aside XUL-only features like XBL, does this matter for many extensions?)

The problem is all the internal JS APIs that add-ons can call right now, there are too many to secure and ensure backwards compat. This is why extensions break between releases so much. It's also pretty hard to program against, so there are a lot of common bugs and it's very difficult to ensure any level of security, since Firefox extensions can do anything.

WebExtensions are intended to be a superset of the APIs Chrome exposes, new APIs are being added all the time. It must be possible to implement them securely and maintain them over time, unlike the current situation with internal-only APIs.

> The design of the new addon signature requirements turns AMO into a walled garden and I very much do not appreciate that

I disagree. Signing is required to make it more difficult for malicious extensions to persist in the wild. There's no requirement to host on AMO, just a requirement to sign if you want your extension to run in Firefox release builds.

If the extension is later found to be malicious, it can be revoked without having to depend on the ID (which is set by the add-on and trivial to circumvent).

> The primary concerns I have, which I left Firefox over

Which browser did you switch to? There's still time to participate and influence outcomes, old-style extensions are still supported today...

rhelmer··on Firefox tops Microsoft browser market share for first time
Mozilla has very clear, detailed privacy policies for all data it collects:

https://www.mozilla.org/en-US/privacy/firefox/

You can find more developer-focused information on Safe Browsing and Telemetry:

https://wiki.mozilla.org/Safe_Browsing https://wiki.mozilla.org/Telemetry

My understanding of the Safe Browsing feature based on browsing the above is that a list of blacklisted URLs is downloaded to the client, this list is known phishing sites.

> Use something like Palemoon and configure about:config a bit more and you should be fine. But be very skeptical of Mozilla claiming FF is some privacy enhancing tool.

Keeping Firefox secure and making the right tradeoffs for collecting data to make the product better (like telemetry and crash reports) while avoiding using the data for nefarious purposes is a hard job, and I think Mozilla does it very well (disclaimer: I work there, and I see the way people treat and talk about users and their data).

> Their plugins ecosystem is also a security nightmare...

Assuming you mean extensions (aka Add-ons) - it is true that there isn't really a security model around classic Firefox extensions, which is one reason they are so powerful. The current form of Firefox extension is essentially the same as in the 1.0 days, and was intended to keep the browser slim and allow for new non-core features.

Web Extensions are intended as the replacement, they are similar to (and largely compatible with) the current Chrome extension system: https://wiki.mozilla.org/WebExtensions

Firefox already does and will continue to support more APIs than Chrome does, to enable more powerful extensions such as Tree Style Tabs.

rhelmer··on Firefox Test Pilot
Oops, thanks!
rhelmer··on Firefox Test Pilot
Correct, supporting existing extensions constrains the architecture of Firefox.

Extensions themselves can also introduce performance problems of course.

rhelmer··on Firefox Test Pilot
Oh, I forgot to mention in my sibling comment - extensions are frequently pinpointed as the cause of (or a contributing factor to) performance problems. Additionally, many of them rely on older features in the Mozilla architecture, which makes it very hard to fix without breaking extensions that people rely on.

While there has been and continues to be significant work in this area, the Web Extensions project has been making great progress and provides a much better means to contain and control extensions, while making the development experience better:

https://wiki.mozilla.org/WebExtensions/

This is already shipping today and many classic Firefox extensions have already switched over.

rhelmer··on Firefox Test Pilot
Hello (and Pocket for what it's worth) are relatively small add-ons that ship with Firefox nowadays, the bulk of the actual magic for both happens in web content. Hello has a new tab-sharing feature, but that also works by sending media streams through WebRTC.

I am starting to suspect that their prominent placement and sudden appearance in the default Firefox UI caused people to think that they are taking a larger amount of Mozilla's development resources than is actually the case.

To bring it back on topic to Test Pilot - hopefully this will help the overall Firefox community vet these types of ideas before they make it to the default UI.

Even if the outcome is ultimately the same (new feature is added/default UI is changed, which makes some subset of people legitimately unhappy), it gives a wider audience a chance to test and provide feedback and generally socialize new ideas.

rhelmer··on Firefox Test Pilot
While it's true that not all bugs are created equal, we do know that some bugs are exacerbated by architectural problems (single process versus multi-process is a good example of this), and new approaches like what Servo is doing in Rust make it possible to write parallel code in a way that is less likely to crash, and less likely to lead to security vulnerabilities.

In general, existing bugs (that I am aware of) are either not actionable because of existing architectural issues, or just because the nature of the bug is difficult and requires an expert whose time is constrained.

rhelmer··on Firefox Test Pilot
As others have mentioned, while this article is about Test Pilot and focused around how you can help with UX experiments, there are lots of wonderful devs hard at work on platform features.

Some are just starting to land after literally years of work:

You might be more interested in reading about platform improvements like getting Servo/Rust components into Gecko: https://blog.servo.org/2016/05/09/twis-62/

Or progress in multi-process support (codename e10s): http://arewee10syet.com/

While these are focused on Firefox to improve performance, stability and responsiveness, there are also experiments like the Positron project, which is making Gecko able to host Electron applications: https://github.com/mozilla/positron

rhelmer··on Cross-platform Rust rewrite of the GNU coreutils
Redox has been working on smaller, more BSD-like versions of the basic Unix utilities, also written in Rust:

https://github.com/redox-os/coreutils

I am excited to see this as I was working on a similar project last year (rewriting the BSD userland in Rust), but it's from pre-1.0 Rust so not really as idiomatic as what is coming out of the Redox project.

rhelmer··on Firefox Can Now Get Push Notifications from Your Favorite Sites
Ben Bangert has given a presentation about this that was discussed here: https://news.ycombinator.com/item?id=10402307

The above links to the slides only, here is a video of the talk: https://www.youtube.com/watch?v=_F2peRzJzhU

rhelmer··on Firefox Can Now Get Push Notifications from Your Favorite Sites
Firefox supports profiles, you can use the Profilist extension which makes it easy to switch between (I keep a separate profile for sites I use my work login on) https://addons.mozilla.org/en-US/firefox/addon/profilist/
rhelmer··on Amazon has no idea how to run an app store
For FirefoxOS "hosted" apps this is true, but they also don't have access to any significant APIs. Only "packaged" apps do.

This is also not true for add-ons (for desktop/mobile or FirefoxOS), these are packaged as zip files and can't be arbitrarily changed.

However, there is the problem however of the app or add-on downloading and running code from the internet unchecked, which is probably intractable to do in an automated way (at least for the current APIs exposed, and for a dynamic language like JS), manual review is required.

Mozilla requires manual review, and Apple disallows interpreters. I'm not sure what if anything Google does about this problem for Android.

rhelmer··on Is OpenSMTPD worthy of OpenBSD inclusion?
Note I said "BSD World" :) FreeBSD is already using LLVM (Clang) instead of GCC, and support fewer platforms - I think this would be a more pragmatic place to push something new like Rust.

If it works out there, OpenBSD could audit and import things at their leisure, at least in theory.

rhelmer··on Is OpenSMTPD worthy of OpenBSD inclusion?
I don't know, I think it's a pretty fair treatment - there are links to an advisory that Ted thinks Rust could have prevented (http://www.x.org/wiki/Development/Security/Advisory-2015-02-...) and to a blog post disagreeing with his http://tonyarcieri.com/would-rust-have-prevented-heartbleed-...
rhelmer··on Is OpenSMTPD worthy of OpenBSD inclusion?
I am hoping that Rust will make in-roads into the BSD world, since it interoperates well with C and is much safer by default while not imposing overhead like a managed language+runtime would. It also has very liberal licensing (GCC being GPL has always been a tough pill for some to swallow, FreeBSD at least has already switched to Clang) https://github.com/rust-lang/rust#license

The OpenBSD folks have done great work through auditing and writing safer code in C, and I agree that using a language that ameliorated at least some of the common mistakes programmers make would be a net positive.

Related - this blog from @tedunangst is worth reading, regarding the limit to which even a language like Rust can protect against specific exploits (the OpenSSL "Heartbleed" vulnerability, in this case) http://www.tedunangst.com/flak/post/heartbleed-in-rust

rhelmer··on Marijuana tax take nearly double expected in Colorado
Well one argument is that teen brains are not done developing, and something that has a negligible effect on an adult might not be so for teenagers... even if there are no harmful long-term effects it might interfere with schoolwork or other things that teenagers are responsible for. I have read these arguments but I don't know what the available evidence points to, this seems like the kind of thing I'd want this sort of education to cover.

Alcohol and tobacco are most definitely harmful for everybody, and it's certainly possible to argue that choosing to use a potentially harmful substance is not something minors are prepared to make a reasoned judgement about.

More generally, I think that showing teenagers that people who buy ads in magazines don't necessarily have their best interests at heart is a good thing!

rhelmer··on Flash-Free Clipboard for the Web
Websites should not be able to overwrite the clipboard unless the action is user-initiated, from the blog post: The execCommand("cut"/"copy") API is only available during a user-triggered callback, such as a click. If you try to call it at a different time, execCommand will return false, meaning that the command failed to execute.
rhelmer··on Lock freedom without garbage collection in Rust
What do you feel is rough around FFI? Safer, zero-cost bindings to C libraries - what's not to like? :)
rhelmer··on Can Servo be a clean and modern reference platform for developers?
This is a false dichotomy. Multi-process and sandboxing are sorely needed, so is a way to make the surface area available to extensions more stable/safe/secure.

Waiting for a whole-cloth Servo-based browser to be totally competitive would be not learning from the not-so-distant past, where Netscape 5 was canceled in favor of the "correct" option of shipping the totally-rewritten Mozilla Suite. Netscape 4 withered away in the market, and it took additional years for the Mozilla browser to be ready and Firefox for it to find its footing.

Making these changes to Firefox benefits users now, and deprecating XPCOM-based extensions in favor of Web Extensions helps pave the way to supporting other rendering engines, which will never support XPCOM (like Servo).

In the meantime Rust is finding its way into Firefox, so code and lessons being learned in Servo (and elsewhere) can find their way to users sooner.

← PreviousPage 3 of 6Next →