🔄 synchronize

Two machines, one project, and the good version is always on the other one. You end up mailing yourself a zip, or pushing half-finished work just to move it across the room. I got tired of doing that and wrote syn.

It's a thin wrapper around git on a timer.

🚪 Sit down and your work is already there.
⏱️ Every ten minutes it quietly catches up.
🔌 Shut the machine down and it commits, publishes, and makes the shutdown wait until that's actually finished — that last one has saved me more than the other two put together.

⚠️ The part I'm proudest of is what it refuses to do. It will not guess at a merge. The second a pull goes wrong it aborts, copies your branch somewhere safe, tells you which repo needs you, and then stops touching that repo at all until you've dealt with it. Nothing half-merged gets committed, conflict markers never reach the remote, and if you ignore it, it reminds you once a day rather than silently not syncing for a week.

⬇️ The other half of it is servers. Tell syn a repo is a deploy target and it only ever pulls — whatever your service scribbles into its own folder stays on that box. It restarts your bot when new code lands, and if the new version won't come up it puts the old one back. The command it runs lives on that machine and never in the repo, so a push decides whether something restarts, never what gets run.

🐙 Underneath it stays ordinary git the whole way: same commits, same branches, any client you like. Stop using it and your repos don't notice.

🧾 syn auto on — that's the entire setup.

🪟 Windows 🐧 Linux 🍎 macOS · MIT
🐙 github.com/FalconTechDev/synchronize

📦 Builds and changelogs live in the FalconTech group — there is a topic for each project.

⛓️vk-chain

Six Degrees of Separation is a lie you can't actually walk.

Everyone knows the theory. Almost nobody can actually walk the graph — you click through profiles one friend at a time and give up after the third ring.

I wanted to know how I'm connected to literally anyone on VK, and how my own circle of friends is shaped. So I wrote vk-chain.

⛓️ Handshake chains: shortest path between any two people, found by bidirectional BFS — the search runs from both ends at once and stops the moment the fronts meet.
Ask for several paths and each next one dodges the people the previous ones already used.

🔒 Relatives and same-surname people: scans up to 4000 of your friends-of-friends, understands translit, and can match by surname root — Иванов = Иванова = Ивановский.

✨ The graph view: your friends and their most-connected friends, drawn in 2D or 3D with profile photos on the nodes, colored by ring, with a force simulation that settles into clean circles. One toggle cuts the edges that don't belong inside your circles.

🔧 Plus: mutual friends of up to five people at once, and your friend list auto-clustered into circles of acquaintance.

🪟 Windows installer — no Python needed, WebView2 does the windowing, everything (fonts, React) ships inside so it works offline apart from the VK calls themselves.
🧾A console version does the same for anyone who prefers a terminal:
python vk_chain.py durov id123456789

⚠️ The honest part: it only sees what VK lets you see. Friends hidden by privacy settings stay hidden, and VK rate-limits are respected — the app tells you when it's being throttled instead of hammering the API.

🪟 Windows 🐧 Linux 🍎 macOS · MIT
🐙 github.com/FalconTechDev/vk-chain

📦 Builds and changelogs live in the FalconTech group — there is a topic for each project.