Hacker News Reader

Comment by wintermutestwin | Hacker News Reader

The Temporary Containers extension is unmaintained: https://github.com/stoically/temporary-containers/issues/618

The containerise extension has pulled in most of the features of temporary containers and is still semi actively maintained.

https://addons.mozilla.org/en-US/firefox/addon/containerise/

https://github.com/kintesh/containerise

Thanks for pointing this out! I was using Containerise + Temp Containers. The "Default Container" section of Containerise has now replaced Temp Containers for me. In case anyone else is interested, here are my settings:

Default Container: On

Container Name: tmp_{domain}

Lifetime: Until last tab is closed

Rule Addition: *.{domain}.{tld}

I still use it. It's been working fine for me bug free. They must have been a good developer.

It leaves the containers behind when I use it so my container list is polluted with all of the temporary numbered containers. It stops me using it when it can’t cleanly handle itself…

Probably Firefox sync, but most likely the extension. I’ll use it again once it works.

I launch FF in a shell function that first calls BleachBit and calls it again when FF terminates. Not sure if that would help your case but it works for me. The reason I do this from a shell function is to redirect the output of FF console to a ramdisk just in case I needed it but did not have it prior to seeing something odd.

There are options to define how container numbering is handled. Right in the General Tab. These settings work for me...

Container Number: Reuse available numbers

Delete no longer needed Temporary Containers: After the last tab in it closes

Terrible news about the maintainer, but is that a problem? If it works it works?

Are there any critical issues with this plugin?

Reply on news.ycombinator.com