I don’t understand how having a notification is what’s keeping an app alive.

Do you remember notifications that couldn’t be swiped away in older Android versions? Their point was to keep their app alive. They still exist and still work the same way, keeping their app alive until it cancels the notification, except they can now be dismissed like any other notification (which doesn’t really have any effect other than hiding it from you - it will still keep the app alive even when hidden).

It’s possible that it’s broken in AOSP for some reason, but developer documentation says it should work like this and it does indeed work like this on stock Google ROMs on Pixels.

why would swiping away an app not kill it? why would you do that? leave it be until it’s done wtf

Because if an app has a permanent notification, it cannot get killed. Before Android 15 or 14, you couldn’t even swipe such notifications away - the idea was that the app was forced to tell the user it’s running.

Then Android added a list of apps running in the background and allowed users to dismiss the permanent notifications, but the behavior is still the same - an app can keep itself alive until it removes the notification on its own or gets force killed either by doze or from the settings.

So swiping away a browser after you initiate a download is a perfectly valid use case that is intended to work without any problems. If it doesn’t, then it’s a bug either in LineageOS or in the browser.

Also, I can confirm this works perfectly fine on stock Android 16 ROM on a Pixel with Vivaldi browser - the download finished, and then Vivaldi got killed, because nothing was keeping it alive after it cancelled its download notification.

Idk, it surprises me it took so long for TP-Link to get into trouble with how they tend to support every HW revision of their routers for about a year and then stop releasing any security updates for them. That’s awful for a device intended to sit at the edge of your network, possibly having a public IP address.

Like sure, you can look for any reasons you want, but not giving a fuck about security in a device that’s always connected to the internet and also routes all user traffic is bound to get companies in trouble when someone with the power to do something about it notices.

Yep, Droid-ify has an open feature request for it. F-Droid has had this feature since 1.22

It was a Google Play feature (a hack built around modular apps that used App Bundles instead of APKs for distribution) that later got added into Android itself in Android 15. F-Droid supports it, you just have to have Android 15 or 16.

Edit:

Android 10+ required

Apparently not according to the other comments here, but I absolutely love Material You now that a lot of apps support it. Not having every app have its own color scheme just feels comfortable and IMHO makes a lot of sense together with the system-wide dark mode.

Also, the app drawer always has unthemed icons, the themed ones are only for the home screen where I like to keep the few apps that I use often, so not having a colorful mess for a home screen is a bigger plus for me than losing the ability to recognize them at a glance, because I know exactly where on the home screen they are anyway.

I mean, first there was the 4a with its software update that rendered affected batteries nearly useless, then the battery recall for 7a, and now there are apparently some restrictions for the 6a in the new update

deleted by creator

it’s incorrect bc it destroys multibyte characters

It doesn’t. As the poster two levels up said, all bytes that don’t represent an ASCII character have the high bit set, even the follow-up bytes in multibyte sequences. So the condition b >= 32 will match and preserve them.

Maybe htop? It’s pretty configurable and has decent bars for various resources.

Also if your reason for choosing pure TUI is just resource usage (and not the aesthetics of it / cool feeling / whatever else), then you could maybe look into running something like Sway or Xorg+i3 - those are very lightweight, well suited for single window usage, and open up a lot of possibilities for lightweight GUI apps.

The “correct” way to handle “static” addresses with dynamic prefix is using tokenized network interfaces (which is pretty much just the lower 64 bits of the IPv6 address). That will then be used for SLAAC in addition to the randomly generated address. The support for dynamic prefixes in firewalls on Linux and Mikrotik is however still pretty dire (obviously, as it’s not an enterprise feature). No clue about BSDs/pfSense

The question asks for “the best” way to do it (making it opinion based) and forbids a potential solution without explaining why (it’s clearly some kind of assignment, but that doesn’t matter here). And it has plenty of answers both using Boost and in pure C++, so I’m not sure why that wasn’t enough for you. Just because it’s closed doesn’t mean the answers already provided are bad.

But ChatGPT doesn’t have a way of “knowing” that there is no such Flatpak - it’s unlikely that its training data includes someone explicitly saying that. But it’s fair to “assume” that a Linux file manager is available as a Flatpak.

(…), so it’s definitely making up stuff.

Yes, it’s an LLM

The “security wormhole” is clipboard history managed by the OS. That’s all. Crappy clickbait headline.

Honestly, this is not really technobabble. If you imagine a user with a poor grasp of namespaces following a few different poorly written guides, then this question seems plausible and makes sense.

The situation would be something like this: the user wants to look at the container’s “root” filesystem (maybe they even want to change files in the container by mounting the image and navigating there with a file manager, not realizing that this won’t work). So they follow a guide to mount a container image into the current namespace, and successfully mount the image.

For the file explorer, they use pcmanfm, and for some reason decided to install it through Flatpak - maybe they use an immutable distro (containers on Steam Deck?). They gave it full filesystem access (with user privileges, of course), because that makes sense for a file explorer. But they started it before mounting the container image, so it won’t see new mounts created after it was started.

So now they have the container image mounted, have successfully navigated to the directory into which they mounted it, and pcmanfm shows an empty folder. Add a slight confusion about the purpose of xdg-open (it does sound like something that opens files, right?), and you get the question you made up.