effingjoe

I think many of us are using reverse proxies, and opening port 443 (https) and maybe port 80 (http).

It’s a shot in the dark, but are you running a vpn on your phone? That might mess things up.

VanillaOS is pretty neat. It has an immutable (kind of) OS, lets you choose which package formats you want to use (flatpak, snap, appimage, etc) and leverages containers (a la Distrobox) and their package manager Apx to give you seamless access to packages on other distros. It’s Ubuntu-based right now but the next release is switching to debian.

To be fair, I don’t have much time on it. My daily drivers are a chromebook and a steamdeck, but I did dust off an old laptop just to check it out for a little bit.

Manager is the highest. (I think there are only two tiers anyway.)

There is something uniquely wrong with your setup; this is not a general google router issue. Which is good news, you don’t need a new router. The next obvious step (for me) would be to wipe the data for the Home app on the phone and re-set it up. If that doesn’t resolve it, you might consider resetting the router itself to factory, though that could be more annoying.

Port management works on mine for creating forwarded ports. Could it be that you don’t have the proper access to edit these settings?

If it matters, my home app is version 3.2.1.7 (Found under Settings -> Support)

It was mostly rhetorical. There’s no way to know that you want the application to have extra access to some folder needed for your theme. That’s the exact kind of thing that would be better handled on a user-input level. You applied your theme, you notice that it is broken with the app, you apply the new expanded permissions to get it to work with your theme.

How do you propose that they trigger that popup? How would flatpak or the application know to ask if you wanted to add those extra permissions?

I can’t say with any specifics but flatpaks are sandboxed on purpose, when you override something you’re giving it more (or less) permissions than the developer thought they’d need. “Automatically giving permissions the developer didn’t think they’d need” seems like a crazy thing to try to automate, no?

Check out Flatseal if you haven’t already. It’s a GUI for flatpak permissions. Might make your life easier in the future.

If feels like there is a system in place that will deal with this if it can be resolved by a simple command. Am I missing something?

I’m sure it does to some degree, though I don’t know if it’s enough to matter on modern computers, and isn’t that what flatpak does, too? (duplicating dependencies)

In any event, if you don’t need an application from a specific distro there’s no reason to create that container. The non-ubuntu ones get created when they’re needed. (And I think the next version of VanillaOS will be debian-based, not ubuntu; in case that matters.)

Yeah, that’s what I mean. You can use flatpak (or snap if you swing that way) but you can also install applications via containers. They’re still not installed on the OS-- even “native” applications get installed via the container. So if the application you want is maintained for arch in aur, you can add the --aur tag to the apx command and it will install that version instead of the default, which is ubuntu. This also works for fedora applications.

Edit: More info here: https://handbook.vanillaos.org/2023/01/11/install-and-manage-applications.html

They don’t hype it as much as (I think) they should on that webpage, but VanillaOS does this thing with it’s package manager, Apx, where it allows you to install applications from various distros via containers, and run them all side-by-side seamlessly. It’s neat.

Check out VanillaOS. It’s pretty neat.

I somewhat recently ran across VanillaOS, which I have only really had time to install and play around with for a few minutes, but it seems really cool. A very brief overview is that it is a sort-of-but-not-really immutable OS that leans very heavily on containerization to allow you to install packages from any other distro in a seamless-to-the-user way. So you can install an application (cli or GUI) from an ubuntu repo and use it along side an application from an arch repo. It’s ubuntu-based, but according to the info on that link, the next release switches to being debian-based.

I mostly use ChromeOS these days-- well, I guess technically I mostly use SteamOS these days-- so I don’t have a lot of hands-on experience with VanillaOS, but I found the concept really cool and from a few minutes of playing around with it, it seemed to work pretty well with respect to the containerization stuff.