alphafalcon

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

I'm hopeful that reencoding on the fly or even merging preencoded files into a single stream is too expensive because it needs a lot of compute power and invalidates caches .

Funnily enough, wikipedia has the answer

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

GNU Terry Pratchett, you shall be missed

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.

The problem is that android auto is restricted to apps installed from the play store.

The F-Droid Version supports Android Auto, but it's blocked by Google.

I managed to enable it by spoofing the installer-package during installation.

For me, the navigation is near unusable. Location tends to lag behind by a few seconds when running on Android Auto. On my phone it's fine.

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

Stopping AWS instances would be handy, but your idea to slag the drives is unnecessary.

Just set up full disk encryption for everything.

You die -> no key -> no data

Fun idea.
Making the horcrux-shares statically linked binaries that contain the share would make it more practical than trying to find the right tool to reassemble the original files after n years.

I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.

Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.

Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.

It's not "better" than compose but I like it and it's nice to have worked with it.

Yeah, from an actual usability and privacy standpoint, that's horrible design. It does make for good visuals with the actor and the display in frame at the same time. No more "closeup of a message on a phone display"

I'm personally hoping for smart stuff to get a bit more distributed. A phone-like CPU unit in my pocket streaming display content to my watch and AR glasses or a full size screen on the seat in front of me on the subway. Simple visual and vibration notifications from a smart ring.

Sportschützen, die mit Schwarzpulver hantieren, fallen relativ sicher drunter. Sonst fällt mir aber auch nichts realistisches mehr ein.