- by Firefox user 13113392, 4 years agoRated 1 out of 5All I want is a truly infinite history, going as far back as I can stretch it. Some day I want to look back at the pages I visited 10 years ago. Yes, I know that could cause performance issues. I don't care. If it gets that bad (and I haven't noticed any issues so far storing two years worth of history), I'll back up my existing history and start over.
Infinite means infinite, not capped at 999999 entries (which could easily be reached some day). Apparently though the extension developer here decided that his users were too stupid to understand the idea of "storing more history = more resources needed" and decided to remove the only thing that made his extension worthwhile in the first place, replacing it with instructions to change about:config entries that you could mess with yourself without having it installed anyway.
Unless the "disable places expiration" option is returned, this extension is pointless and you shouldn't even bother installing it. It's a shame that for whatever reason the developer decided that people weren't smart enough to use his add-on properly. That's how everything useful dies.
I'm just lucky I caught the change in the "updated" version of this extension before Firefox managed to wipe my history out. I've gone back to an old version until this issue is fixed. Shame on you for making this change so suddenly. What if somebody updated that already had more than 999999 entries in their history? You'd be wiping out the record of their digital life.
If you're going to put things under a big "scary options for experts" heading, then let those people actually pick the options that they want. Return the option to disable history expiration entirely.
Edit: If the response is true, then what does the (now disabled) preference "extensions.bonardonet.expire-history-by-days.disable_expiration" do?
Developer responseposted 4 years agoFirst: the disable expiration checkbox was just setting the pref to 999999, so nothing changes. Second, Webextensions cannot set prefs anymore, so that's why it's suggested to do that manually.