Tailscale recently added local file transfers called Taildrop https://tailscale.com/kb/1106/taildrop
This really solved this issue for me, right click a file and select the receiving peer and it just appears instantly on the other device.
I would assume that limitation is because it's on the roadmap, but they want a different UI for it, or more control, or to see how beta goes with just your own devices, give some time to think about how it should work, etc.
Because they've had to specifically put that limitation in place, no way they don't realise it could be useful.
I created an automated installer to provide this functionality on KDE Plasma using Dolphin this morning to emulate the experience of sharing via TailDrop on Mac for Linux.
YYYY-MM-DD is the standard in Germany, most people don’t know that and essentially no one (including in official documents) uses it. Never seen it anywhere outside computer nerds who like sortable dates. So yeah, DD-MM-YYYY is the normal way here.
I would add that if DD comes first, the format is usually DD.MM.YYYY. Or DD/MM/YYYY, which is more common in the UK. Rarely have I seen dashes when not following the ISO 8601 YYYY-MM-DD standard.
I was taught DD.MM.YYYY in school (90s). This is the de-facto standard (short) date format in Germany and by far the most commonly used one.
First because it’s consistent with the longer written out date format used in German: „19. Januar 2022“ (19th of January 2022) – note the dot after the 19.
Second because it’s also consistent with how it’s spoken. The dot denotes ordinal numbers in German and that’s also how the date is spoken: „Neunzehnter Erster Zweitausend Zweiundzwanzig“ or “nineteenth first two thousand twenty and two”.
Dashes and slashes are highly likely to be confusing to people if used in that context, though advisable if you are using any other date format because then at least people will be weirded out and likely pay closer attention if there’s anything going on with that date.
It is true that DIN 5008 (which defines rules for word processing and does have some weight in professional circles) recommends YYYY-MM-DD, however this way of writing the date never took hold in Germany (just because it’s part of a norm doesn’t make it commonly used or accepted) and DIN 5008 does actually allow for DD.MM.YYYY.
YYYY-MM-DD is, as far as I know, merely a recommendation in DIN 5008, not in any way the standard in Germany, either officially or informally. DIN 5008 does allow for DD.MM.YYYY (with the dots and without spaces), Duden recommends spaces after the dots.
I looked it up again, you were more right than me ;) If you speak German, you can read about it on Wikipedia [0], essentially it was the only format from 1996 till 2001, but because it was completely ignored, they went back to allowing DD.MM.YYYY, since 2020 it also includes that the old format is only to be used for national mail.
To be pedantic that still requires assuming the author is using a sane convention (RFC3339) or convention including sane formats (ISO 8601) and not something ridiculous like %V-%W-%O or %Y-%D-%M. Thankfully the sane convention seems highly likely.
If you are starting with C++ right now, I'd suggest Scott Meyer's More Effective C++ (and his other books) and the books by Herb Sutter.
Don't worry too much about C++ 17/20 unless you are working for a company that use the newer standards. A lot of companies still stick to C++ 11.
I installed Nest Outdoor cams at my in laws last week. They can do person detection, thus you'd only be notified if a human being moves around the stable.
