Danke, das klingt verlockend.
Dein Link ist allerdings irgendwie kaputt, kannst du den nochmal checken, bitte?
EDIT: Hier ein Link, den ich für die Flugtage Wesel gefunden habe.
The manual says it works on "any phone or tablet", running Android 7 or higher. Mine is a OnePlus 6T running LineageOS 20 (Android 13). On my much slower and less well-equipped Samsung Galaxy Tab A7 Lite LTE (3 GB RAM) it installs just fine. Would it really object to being installed just because the phone has an unlocked bootloader? It isn't rooted, and even banking apps work fine.
Strange. Maybe I'll file a bug report. It looks like something I might spend $10 on if it works fine.
The Playstore says Infinite Painter won't work on my device. What are the requirements? I have 6GB RAM and Android 13. What more could it want? Or is it generally only for tablets?
--info=progress2 for long transfers involving a large number of files. Gives continuously updated statistics on the whole transfer.
Rooting your phone and unlocking the bootloader are separate (and mostly independent) things. E.g., by default, LineageOS is not rooted, but it requires an unlocked bootloader to install. Now, rooting without an unlocked bootloader is harder.
a future where all computing/devices are locked down
And who would mandate and control such a requirement? And how would it be enforced? And why?
The only reason Apple is locked down as it is, is that Apple as the only manufacturer has absolute control over architecture, hardware and software.
Being open will always be a unique selling point by at least some competing companies, so there will continue to be some, absent a dictatorship rigorously controlling the manufacture and sale of such devices. But I think not even China has managed to accomplish that. Open devices are an absolute necessity if you want research and technological progress. And if the industry needs it, some of it will inevitably become available to citizens, too.
Und die dritte im Bunde ist eine Piper PA-28-181 Archer III, ein komfortables Reiseflugzeug mit Garmin GX3 Touch-basierten elektronischen Instrumenten ("EFIS") und Autopilot.
Noch eine, die Cessna 172S unseres Clubs. Auch zur Schulung, aber gern genommen als bequemes Vier-Platz-Reiseflugzeug.
For large storage, ECC helps a lot for avoiding storage corruption. In combination with a redundant architecture in zfs it is almost bullet-proof. (Make no mistake, redundant storage is no substitute for backups! You still need those.)
One option is to use comparatively old server hardware. I have some pretty old stuff (around 10 years) that uses DDR3 RAM, which is dirt cheap, even with ECC (somewhere around 1 €/GB). And it will be fast enough by far for most applications. The downside is higher power consumption for the same performance. The Dell T320 I have with eight 3.5" SAS disks and 32 GB RAM uses some 140 W of power, to give you a ballpark figure.
What's your problem with DAVx^5? It's completely and permanently free and fully-featured on f-droid. Only the PlayStore version costs money. The authors don't want to make money, but motivate you to move away from Google infrastructure.
If you only need address/phone number sync, then nextcloud is probably overkill, but I use it, and it works great. Also for calendar sync and file storage.
(You don't need to put the community name in the title, especially not with "@", which signifies usernames. Communities are prefixed by "!".)
Yes, that's my workaround, too. Not a dealbreaker if it doesn't get priority. Just nice to have it in-app.
ZFS raidz1 or raidz2 on NetBSD for mass storage on rotating disks, journaled FFS on RAID1 on SSD for system disks, as NetBSD cannot really boot from zfs (yet).
ZFS because it has superior safeguards against corruption, and flexible partitioning; FFS because it is what works.