Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AL
Posts
0
Comments
42
Joined
2 yr. ago

  • That's the equivalent of leaving the door open and hanging a sign "Internet over there" pointing at a wall.

    Programs don't need to respect those registry keys. If you're worried about internet access, set up a firewall.

    Also, if you're worried about malware, the damage is probably done before anything connects to the internet.

  • To a certain degree, yes. If someone at Google decides to wage all-out war against ad blockers they have a good chance. But if that costs more money than it generates, odds are that someone will stop it. Google / Alphabet is publicly traded after all and that means profit above all else.

  • Embedding ads into the stream would be hard to counter, but it's far away. That would invalidate caches along the way and need extra performance to reencode the stream with the ads inserted.

    That's extra costs that are hopefully orders of magnitude above the lost ad revenue from ad blockers

  • 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.

  • 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.