| 15 Jul 2021 |
|  Reynir changed their display name from reynir to Reynir Johnson. | 16:26:59 |
| Reynir changed their display name from Reynir Johnson to Reynir b'Johnson. | 16:29:15 |
| 26 Jul 2021 |
 teh 1 | So one of the rare moments where all the tabs opened without the designated containers happened. | 07:53:08 |
| teh 1 | (After force restarting my machine) | 07:53:31 |
| teh 1 | Restarted Firefox but containers didn't come back. Looks like Firefox just completely forgot about the extensions. | 07:55:17 |
| teh 1 | * Restarted Firefox but containers didn't come back. Looks like Firefox just completely forgot about the containers. Nuking the profile, bye. | 07:56:06 |
 Joe | Oh no. That didn't happen to me in a long while 🤞 | 22:20:47 |
| Joe | Also I'm backing up parts of the profile meanwhile, including containers.json - which actually the only thing you need to be able to restore | 22:21:40 |
| Joe | * Also I'm backing up parts of the profile meanwhile, including containers.json - which is actually the only thing you need to be able to restore | 22:21:47 |
| 28 Jul 2021 |
| teh 1 | Oh, there was that trick. But what happens to new tabs that aren't recorded containers.json? | 12:58:38 |
| teh 1 | And what kind of bug is this? Even if I'm force resetting the machine, containers.json should still be there even if it's some older iteration right? Or is the containers not applied because it's some older iteration and Firefox refuses to acknowledge it? | 13:00:33 |
| teh 1 | Either way, just straight up opening tabs without containers is just straight no form me. The least Firefox can do is ask the user what to do about those tabs instead of just dumping them straight into the no container namespace (is it even called namespace in this context?). | 13:01:58 |
| Joe | All tabs with no longer existing containers land in no container - so yeah, that's really not nice of firefox | 14:59:57 |
| Joe | (I think it's called user context) | 15:00:20 |
| 1 Aug 2021 |
| Joe | Makes me realize, you can probably generate the containers.json based on the still existing data storage directory, where the directories have the user context id in their name 🤔 | 08:25:43 |
| teh 1 | As a workaround? There's no timeline on getting the underlying Firefox bug fixed? | 11:01:43 |
| teh 1 | BTW, how does the extension keep track of containers to be deleted? Because sometimes I see old sites that should've been deleted alongside their containers, but still around in the history. | 11:02:55 |
| Joe | It stores every URL visited in a deletes-history tmp container, and when the container gets deleted, it loops over all URLs and tell the firefox API to delete that URL from history | 17:12:05 |
| Joe | So if you happen to visit an URL outside of a deletes-history container, it won't get deleted from history, even it's the same base domain | 17:12:45 |
| Joe | * So if you happen to visit an URL outside of a deletes-history container, it won't get deleted from history, even if it's the same base domain | 17:31:00 |
| teh 1 | I set TC to automatic mode with deletes-history container, definitely not opening anything in user context (besides the crashes forgetting containers and fresh profile before installing TC). | 17:45:44 |
| Joe | odd, then either TC or firefox bug, can't say without reproducable steps | 17:54:45 |
| teh 1 | I suspect possibly closing Firefox before the 15 mins to delete setting had the chance to remove the container. But I have no basis for suspicion. | 18:07:08 |
| Joe | That shouldn't matter, the containers are persisted until actually deleted | 18:19:40 |
| Joe | The only thing I could imagine is closing the browser just in the moment that stuff is in the middle of getting deleted, since it isn't a transation | 18:20:03 |
| Joe | * The only thing I could imagine is closing the browser just in the moment that stuff is in the middle of getting deleted, since it isn't a transaction | 18:20:07 |
| Joe | That'd be really unlucky timing, but if you're always in delete-history mode then the chances go up I guess | 18:21:10 |
| teh 1 | Occasionally, the different domain filter fails and opens in the same tab (and container), but I'd notice right away; I also have random color setting toggled on to tell at a glance if it's a new container or a long-running one. That's why I am pretty sure those are not history from existing containers. | 20:08:01 |
| teh 1 | Man, the containers are such an amazing concept but it's bit properly integrated onto Firefox, what a shame. | 20:09:30 |
| teh 1 | * Man, the containers are such an amazing concept but it's not properly integrated onto Firefox, what a shame. | 20:09:51 |
