• 3 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: October 22nd, 2025

help-circle





  • Thanks, really useful feedback! I’ll look into the missing sources from that issue. It could well be a problem for environmental science and ecology too, since I’m not too familiar with those fields. If you know or find any preprint servers people in your line of work use, feel free to add them to the issue, that would help me a lot. A News tab is an interesting idea, I’ll think about it. I do want to keep it lean and focused on papers, so it would only make sense if it fits without making the app heavier or less private. I also really like how you’re using it. Starting with broader keywords and then narrowing down is something I didn’t think of, but I’m happy you tried it and made it work!











  • Totally fair, Unison is solid and I was inspired by it a lot, but its also the reason why I started working on my own version. I was frustrated with it because on Synology/SMB filesystems it kept seeing changed timestamps as modified files, so I’d constantly get fake changes and transfers. Synchi only treats a file as changed if the content hash actually differs.

    Also, I once managed to delete my entire home folder because I tried syncing it with Unison to a server and it synced the empty remote folder back to my home, wiping everything. That’s exactly the kind of human error Synchi tries to prevent by being very explicit and verbose about what it’s about to do.

    Thank you for keeping an eye on it!


  • It doesn’t work that way. Conflicts are resolved before any transfer starts. The flow is:

    Scan both sides and compare (compute file hashes or just compare mtime, no data transferred)

    Show conflicts if any → you resolve them

    Show copy/delete summary → you approve

    Only then does the actual transfer begin. So you never come back to find it halted mid-transfer. All decisions happen upfront while it’s just reading metadata, which is fast even for large trees.


  • It compares everything first (scan, diff, hash), then halts before any changes are made. You see a full summary of what will happen, and approve each category separately (copies, deletes). It’s designed to be very transparent. Every change must be approved before anything is written.

    Conflicts get their own interactive screen where you pick per-file: keep A, keep B, or skip. Nothing is written until you’ve resolved all of them.

    If you want to skip the prompts, --yes flag auto-approves, but conflicts still halt for user input. Flags --force root_a or --force root_b are used for mirrors one way here conflicts are not possible.





  • Yes, but most of these national apps I mentioned are already phone number based. 

    I also hate this. Phone numbers get recycled by operators, they are not owned by user, they just get assigned. 

    Not to mention sim swapping and privacy leakage by design.