Hacker News Reader

Comment by msoloviev | Hacker News Reader

I made a fork of this that gives you some additional control over how links are treated - specifically, you can set it up different rules for what container to open a page in depending on what container it was opened from: https://addons.mozilla.org/en-US/firefox/addon/containers-wi...

The rationale is that you rarely want pages that you open from random Facebook posts or Reddit submissions, or pages that you arrive at by following more links from those, to have access to your Facebook or Reddit login information.

View on HN

This seems really similar to the Facebook container (made by Mozilla, https://addons.mozilla.org/en-US/firefox/addon/facebook-cont...) and the Google container (a fork of the previous, https://addons.mozilla.org/en-US/firefox/addon/google-contai...)

The annoying thing about your extension is that the end-user would need to know about and update the domains they want to keep isolated. It would be great if all these extensions/features were built into the original extension and there were updating isolation lists similar to the uBlock Origin lists (EasyList, Peter Lowe's list, etc.).

I use Temporary Containers (https://addons.mozilla.org/en-US/firefox/addon/temporary-con...) to do this. You can customize how you want links handled when they target different domains. It takes some getting used to as there are a handful of options to understand/customize. Plus you can have customizations where you're replacing the current container with a new one which kills off your back button history. Just need to be aware of the quirks. It's definitely still in the realm of power-user UX.

Perfect! This is the functionality I've been looking for. I already had a container addon for Amazon and Facebook for this which should be unnecessary and with your fork it is.

Thank you.

I'll be trying this— I like Firefox containers a lot, but I dislike how session-oriented they are. You can force a particular site into container X, but every click from there will stay in container X unless another rule forces it to a different containers.

What I want is something more like "jail site X in container X, and open every non-X link in a temporary container / container Y / whatever."

I use containers + Cookie Auto delete [0]. In the HN container, I keep HN cookies. Anything opened from HN will stay in the HN container and non-HN sites get cookies deleted shortly. This reduces some tracking for me, but doesn't do anything for something like an XSS against HN that the GP seems to be referring to.

[0]: https://addons.mozilla.org/en-US/firefox/addon/cookie-autode...

Conex (https://addons.mozilla.org/en-US/firefox/addon/conex/) has an option that allows the user to select container for incoming links

Same for https://addons.mozilla.org/en-US/firefox/addon/simple-tab-gr...

Ymm this should be included in the official version. Tried making merge request?

Reply on news.ycombinator.com