this post was submitted on 04 May 2024
386 points (96.2% liked)

Firefox

20372 readers
160 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.


Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner


Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.


founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] QuazarOmega@lemy.lol 2 points 1 year ago (1 children)

I didn't know, that sucks so much.
Though, someone made a post on superuser and a reply said that you can back up the database, so at least something is salvageable

[–] fine_sandy_bottom@discuss.tchncs.de 3 points 1 year ago (1 children)

Yeah but if you import a backed up db wouldn't the old entries just get deleted?

[–] QuazarOmega@lemy.lol 1 points 1 year ago* (last edited 1 year ago) (1 children)

They said you can merge without conflicts:

Making a backup every 60 days seems to be sufficient to keep all history. sqlite doesn't reuse old ids (I think?) so merging the backups shouldn't be too hard.

But they haven't tested it, also I wonder if once you do that successfully, Firefox will just delete all the extra records at the next startup, so idk

The entries would still be datestamped and as firefox clears up the history the older ones would be deleted.

In my other comment I linked something that said firefox just starts tidying up as performance starts to degrade, rather than a fixed limit of history entries.

Therefore, if your history is more or less full, and you just import a heap more history, firefox is just going to "tidy up" everything you just imported surely.