But of course "lunchtime" is a completely meaningless term for me.
1 - I rarely eat a meal in the middle of my day. In fact I usually only eat once, so is that one meal lunch? or breakfast? or dinner? or what ??
2 - My day not only isn't the same as yours, it isn't even the same from day to day, so even if I agreed to call my one meal lunch instead of dinner, it does not come at the same time as yours does, and does not even come at the same time from day to day, and does not even come at the same time relative to when I am awake let alone the absoluet time.
It's inconsiderate to think this is reasonable for everyone else because it's reasonable for you. It's like how kids and the untravelled and otherwise ignorant presume everyone else's life is exactly the same as theirs.
I could translate of course, because of course I know what it means for probably the majority of everyone else, but why should I have to do that? This whole topic is about convenience and meaning, and this would be inconvenient and of only arbitrary meaning to me. It would be like calling it "triangle time" sure, I could just know that that means around noon. Why should my interface require me to translate from markers that are meaningful to someone else's life but not to mine?
A worse example just to show what's so wrong would be like calling sunday "church day". Or sunday afternoon "right after church". That would be not only inconsiderate but downright offensive. For a lot of people that would be perfectly fine and some of them would even fail to see why that should be a problem for anyone.
And the offense isn't just mentioning a religion, it's the assumption, the turning anyone else into the exception, when they are not an exception, they are equal.
Would you still be upset if I told you it has a hobbit setting where you get times like "second breakfast" and "elevenses". I'm sure you're a cool person and I don't want to denigrate your lifestyle, but the thing I'm talking about is a humorous desktop widget on an eopen-source desktop. You are certainly not obliged to use it, I'm fact you could even send in a patch that represents you - and have "only meal of the day time - ish" or "time to not attend a religious service".
If only I had explained the purpose of the church example was to illustrate with a stronger example that's merely further along the same dimension... If only I had explained anything at all instead of just saying I hate some idea for no unpackable explicable reason...
If the thought of a clock that says "about lunch time" sends you into a seven paragraph manifesto about the evils of the clock.....perhaps you should just not use it.
But this was a timer on a normal phone. It's pretty useless to tell me it's less than one minute left until the eggs are done. Do I have time to do a bit more dishes or will the phone ring in one second? Who knows?
Interesting you say that actually, I have been working on a folder synch implementation across samba with mac & win environments and the last modified times are not a reliable source of truth it seems. This fuzzy method would have been very useful as the exact minute of the modified file isn't critical.
In the end though we just used checksums, but over the wire the larger files take too long. This comment has given me an idea!
Getting off topic but most sync systems do a quick comparison then a full one.
So for example check modified, inode number against the previous version. If they are all a match consider skipping the checksum. This way you can skip almost all checksums on an incremental transfer. You can have false-negatives but this can often be mitigated by occasionally doing a full rescan or similar.
> So for example check modified, inode number against the previous version.
To be honest, I didn't even try this because the destination machine is Windows, I didnt think inode number had an equivalent in windows, but after googling, there might be a way.
Another great suggestion.
As for the full checksum, I went with a chunk size of the first and the last of the file, (the changes are very small, property based) but I don't think its as reliable.
