• 6 Posts
  • 25 Comments
Joined 5 months ago
cake
Cake day: October 22nd, 2025

help-circle

  • 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.








  • Please correct me if I am wrong, but I understand it like this: Wero is just a UX layer and to identify the user and their bank. It uses “SEPA Instant Credit Transfer (SCT Inst)” as the protocol. This was made mandatory to support for all EU banks in October 2025.

    So wero is not the only app, there are plenty other national apps, which again, are just UX for SCT Inst protocol.

    Examples: Poland - Blik, Netherlands - iDeal, Sweden - Swish, Slovenia - Flik, Spain - Bizum…

    I guess wero tries to replace all this so people can send money across eu countries.




  • It’s similar on the surface, but the 24h cake part is the core idea.

    The entire day is visualized as a 24-hour circle, so both work and breaks are visible.

    Psychologically, that makes it very obvious how the day was actually spent, not just how much time an activity took.

    And no, there’s no enforced structure. You’re free to work however you want. You can follow pomodoro or whatever best suits you.

    Edit:

    If you are interested, check out the screenshots on GitHub readme or give it a try :)


  • No haha, that would be alot xd. The 24 hours represent the day. Each focus session is a slice on a 24-hour circle, not a single 24h session. (you start/stop the sessions to log them) Does it really read like 24-hour focus sessions? If so, I should probably rewrite the info. :) thanks for the feedback!