alphafalcon

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

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.

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.

I've always held that Non-fungible is a typo. It's meant to say non-functional token.

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.

Because collecting data that is not strictly necessary is almost always a bad move. IP addresses might be relatively harmless, but might link you to other activities.

You personally might be okay with reddit knowing your IP addresses, but some people might get into trouble.

Take the insane anti-abortion laws in some US states. If an IP address from those states accesses pro-choice subreddits, that might be enough for law enforcement to start harassing someone.

You dynamically request "a port" from the vpn gateway and it returns your port number.
As long as your nat-pmp-client keeps refreshing the port, it should stay the same. The timeout is rather low (60s afaik) so it probably wouldn't survive restarts.

There's a docker image that automates this for qbittorrent, but it shouldn't be overly complicated to adapt the script to other clients, if they can be configured via an API.