Aside from budget and time overruns it looks like they overshot the target of "futuristic" and landed in the middle of dystopian...

Not the only one.

Threema is decent, too. Crypto is comparable, and allows signups without email or phone number. It's a paid app, though, but anonymous purchase options are available.

For anything I don't control, like door locks at work, I'm with you.

For a device controlled by me, the tradeoff for convenience is so much better.

If it's properly implemented, extracting biometric features is hard, so stolen fingerprints are less of a concern.

It allows me to use a long password, which in android also serves as an encryption key for the filesystem, while allowing me to unlock my phone without entering that password every time.

There should be an external hard drive full of portable game installs in some drawer that fits the time period.

Should easily kill a week.

Currently:

• VR
• Uncategorized

Soon to be added:

• Linux (tested/works on)

Wow, that sounds like a decent start for an architecture.

I'm tempted to spin up a few Jellyfin instances to see how it might work...

No, No, they don't understand everything and nothing!

Funnily enough, wikipedia has the answer

https://en.m.wikipedia.org/wiki/Wikipedia:Database_download

I built a custom app to do it since I couldn't manage to fire the relevant intents from an adb shell without root.

I lifted the code from AAAD

Specifically the InstallAPK method in MainActivity.java

Intent intent;

            if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
                intent = new Intent(Intent.ACTION_INSTALL_PACKAGE);
                intent.setData(getUri(file));
                intent.setFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION | Intent.FLAG_ACTIVITY_NEW_TASK);
            } else {
                intent = new Intent(Intent.ACTION_VIEW);
                intent.setDataAndTypeAndNormalize(Uri.fromFile(file), "application/vnd.android.package-archive");
                intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
            }

            intent.putExtra(Intent.EXTRA_NOT_UNKNOWN_SOURCE, true);
            intent.putExtra(Intent.EXTRA_INSTALLER_PACKAGE_NAME, "com.android.vending");
            getApplicationContext().startActivity(intent);
        } 

Basically you construct an Intent ACTION_INSTALL_PACKAGE with data pointing to the APK file and the extras EXTRA_NOT_UNKNOWN_SOURCE=true and EXTRA_INSTALLER_PACKAGE_NAME="com.android.vending" which tells the installer that this APK is not sideloaded and it's the play store asking to install it.

You might still need to enable unknown sources in Android Auto developer settings (separate from phone developer settings).

If I remember, I'll try to pull the code for my app from my PC and post it.

IT changes usually affect management as well, while "cost saving" in production doesn't.

Software licenses would be a good example of a possible blockchain application, but they could be easily represented by classic tokens, no need for non-fungibility, as all licenses should be exchangeable.

You're asolutely right, IP addresses are kind of a grey area since the are needed for lot of troubleshooting and debugging.
Nevertheless, you can always strive to reduce the stored data.
For your application, you wouldn't even need to store the historic IP adresses, just a rough geo-location and maybe a mobile/landline/whatever-flag and comparing the current login attempt to that. Even saves you some performance by not repeating the geo-lookups everytime.
Implement your failed-login counter separately by account and source IP and you've got decent security without linking an account to an IP.