They should not be worried, they should be educated.

If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.

We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.

Yeah, inductive charging is basically a must.

Especially because it eliminates the guesswork if the watch is correctly seated to charge

Oh, they’re putting a lot of thought into it I’m sure.

That thought being “Money, Money, Money, Profit, Profit” of course.

No actual technical solution here, but it smells slightly of XY-Problems.

From what you described it seems the main issues are

• too many calls
• not knowing who’s calling
• not wanting to answer the phone
• not reaching the phone in time

Maybe you could look into solutions like setting a custom ringtone for important callers or having the phone announce caller names so your mother can decide if she wants to make the effort to get her phone.

I’m speculating a bit here but I can imagine that getting up and answering the phone is exhausting for your mother. Also if her mindset is " a ringing phone means it’s important" that could make it even more stressful.

Maybe you could find a way to let her silence all calls except caregivers and ICE contacts. (On Android DND exceptions could work for that)

That way she doesn’t feel pressured to answer the phone every time it rings and stays reachable.

If it’s actually just the physical issue of reaching the phone in time, does she have a convenient way to carry the phone indoors like a lanyard?

Hope some of this helps you

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.

That feature is right on the border between real neat tech and deeply unsettling.

“Hey, my phone uses its last few electrons to turn into a bluetooth beacon to stay findable” sounds like sci-fi “reserve power emergency mode”

“I can’t turn off the locator chip in a device that holds half my life and memories” is just dystopian.

I’m wondering if there would be a way to keep it useful while minimizing impact for people who stay off the grid. A hardware switch would probably be a good start but they won’t fly with current all-touch designs.

Spannendes Detail:

Es ist möglich, formal fehlerhafte Rezepte an die TI zu übermitteln. Funktionierende Validierung gibt’s nicht.

Warum nicht gleich ein PDF des gescannten Rezepts ablegen, das wär wenigstens einfacher…

In welcher Luxus-Ecke von Deutschland lebst du denn, dass es bei dir Videosprechstunden gibt?

Und die Gründe für Videosprechstunde nicht möglich reichen vermutlich von zu wenig Bandbreite über keine Kamera bis zu “machen wir nicht”.

Und was ist das Problem, mit Video ist ja auch ne AU möglich.

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

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.

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

Very neat idea, but I’d explicitly add strong encryption to that method, cars do get broken into.

I’d encrypt every off-site backup, but a car is a bit more exposed than a rented safe box.

Mullvad stopped providing port forwards, so they’re not ideal for torrenting anymore. They were great before.

Thanks for the pointers that sounds quite doable. I’ll give it a shot to mash it into my helm chart. Will report back.

Edit:
Got ProtonVPN and qbittorrent working with manual port-forwarding. The natmap-docker image wants to use the docker socket which is not available in my kubernetes cluster.
I’m currently reworking the script to run without docker access.

Mind sharing some details of your trickery? I’m in the same situation currently