alphafalcon

Hmpff, ich fand ihn ja schon immer latent unsympathisch. Dass er jetzt mit den "Christ"-"Demokraten" Politik machen will bestätigt das irgendwie.

The good thing is that you don't need to know which ports to block. You just set your firewall up to deny by default and then start whitelisting the things you want to allow.

Even easier if you put your "smart" devices in a separate network, then it's just:

• Allow traffic from home net to Internet
• allow traffic from home net to iot-net
• drop the rest

Now you can surf the internet, control your devices and they can't phone home

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 .

That has some major Lovecraft vibes... Have you read Equoid by Charles Arrows?

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.