Kopia might meet your needs.

https://kopia.io/

(Edit, because I’ve got more time :)

• Runs native on Windows and macOS. Doesn’t need Windows WSL or a wrapper
• Can run as client-server, or standalone, backing up to local, network, S3, WebDAV, various clouds, etc
• Open source
• Snapshots are incremental, encrypted, and deduplicated
• CLI and GUI

I’ve been happily using it for years for similar needs (mixed systems)

Syncthing has multiple file versioning strategies.

https://docs.syncthing.net/users/versioning.html

So it can provide quite solid protection beyond a trash can, but yes, it’s still primarily a syncing tool.

Yes, and their shorthand versions, like writing 9/4, have the same problem of being ambiguous.

You keep missing the point and moving the goal posts, so I’ll just politely exit here and wish you well. Peace.

Yes and YYYY-MM-DD can potentially be interpreted as YYYY-DD-MM. So that is an zero argument.

No country uses “year day month” ordered dates as standard. "Month day year, " on the other hand, has huge use. It’s the conventions that cause the potential for ambiguity and confusion.

That is great for your team, but I don’t think that your team has a size large enough to have any kind of statistically relevance at all. So it is a great example for a specific use case but not an argument for general use at all.

Entire countries, like China, Japan, Korea, etc., use YYYY-MM-DD as their date standard already.

My point was that once you adjust, it actually isn’t painful to use as it first appears it could be, and has great advantages. I didn’t say there wasn’t an adjustment hurdle that many people would bawk at.

https://en.m.wikipedia.org/wiki/List_of_date_formats_by_country

DDMMYY is perfect for daily usage.

Except that DDMMYY has the huge ambiguity issue of people potentially interpreting it as MMDDYY. And it’s not straight sortable.

My team switched to using YYYY-MM-DD in all our inner communication and documents. The “daily date use” is not the issue you think it is.