↓ Skip to main content

Plakar

Flipper Zero, Plakar one

·2188 words·11 mins
TL;DR: I had an AI write a plakar integration for the Flipper Zero. It talks to the stock firmware over USB, backs up the SD card and the internal flash, restores onto the same device or another one, and for the fun of it can keep a kloset on the Flipper itself.

Plakar: an avalanche of changes

·2625 words·13 mins
TL;DR: Significant refactoring to improve its performance, implemented read and write semaphores to throttle chunkers and reduce memory usage, introduced a repository index and packfiles to decrease the number of I/O operations, also intrioduced a new HTTP storage backend. A ton of refactors # I’ve done so much work on plakar in the past few weeks that I don’t even know what to begin with…

Plakar: a TON of changes

·3855 words·19 mins
TL;DR: TL;DR: a lot of work in plakar, but also on CDC and index optimization. Optimized go-fastcdc # I ran into a benchmark which included my implementation of the FastCDC algorithm, and it made me realise that it was not on par with alternative implementations:

Plakar: snapshot forking and tagging

·2064 words·10 mins
TL;DR: plakar gained two minor features, snapshots fork-ing and snapshots tagging, which makes it possible to unlock several major new features in a relatively short future. Plakar is not only for backups # If you have followed my work on this project, you may have assumed that plakar was intended solely for backups: it’s not entirely the case.