Activity
Stars and mentions · Last 30 days, Oct 7 – Nov 5
Top repositories
mickael-kerjean’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside mickael-kerjean’s account where mickael-kerjean opened or reviewed pull requests in the past 365 days.
Who noticed mickael-kerjean
Everyone who starred or forked mickael-kerjean’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories mickael-kerjean owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
I have been working on a shared folder that sync between agents (filestash.app). The control plane [1] handles pretty much all storages protocols / platform (S3, SFTP, NFS< SMB, ....), you add the controls / permission boundaries and everything is auditable + traces, and the sync client is at the edge [2] to sync the data it actually has access. [1] mickael-kerjean/filestash [2] mickael-kerjean/fdrive
Yes they can. I have been working on the filesystem part with the idea to provide a "a shared folder that syncs for your agents" github.com/mickael-kerjean/fdrive/tree/master/cra…
Yes. That's exactly what I'm currently doing with my sync client: mickael-kerjean/fdrive The core contains the logic all the underlying platform uses and the platforms only handle wiring and ux
I work in this space with my oss work on Filestash, and its sync client mickael-kerjean/fdrive. A proper sync client is nowhere near a two week hackathon unless you vibe code it and don't have much care. I've been on it for 6 months and it's far from finished. Linux alone has a fragmentation problem. The sync engine can be shared, but the integration can't: tray, status, file manager overlays and notifications all work differently on GNOME, KDE, COSMIC, Omarchy, Sway. Electron looks out of place everywhere, so you end up maintaining one frontend per desktop, plus packaging for each distro. Then there's the sync itself, which is a long tail of edge cases, often platform specific. Last week I optimised the rm -rf case, FUSE hands you one unlink per file, so a folder with 10k files becomes 10k API calls unless you do clever things. Today, I've tried to optimise thumbnails, problem is the file manager opens every file in a folder just to render previews, so browsing a directory of videos can easily get uggly as well, let's not talk about the state of atomic save which if you are not clever here too will create multiple files on your server and waste bandwiths. There are many dozens of these edge cases just on linux and that's before you tackle window, mac, android, how do you handle delta sync ....