

yes, but this change only affects certified Android devices (ie, ones that run software that Google put their blessings on), and /e/OS is squarely an uncertified (and Google-free) Android fork


yes, but this change only affects certified Android devices (ie, ones that run software that Google put their blessings on), and /e/OS is squarely an uncertified (and Google-free) Android fork


On Pixel 8 and above, you can plug in external displays, but it will only mirror your phone screen. Supposedly, Android 16 will allow you to “extend” the screen, ie. treat it as a separate screen. Also, the GUI stuff for the Linux Terminal will only drop in Android 16, so yeah, I’m stoked for that release.


Are you sure you’re talking about the Linux Terminal app that’s available in developer options and not Termux? For me, all Gnome things and Xfce things are present in the repos (and it’s using the deb.debian.org default Debian repos, so it makes sense)


I mean… This is kinda close. The “Linux Terminal” app is running a full Debian install in a KVM VM. On the newest version of the app (like on Android beta or on GrapheneOS), you even have a full GUI that you can use.
In theory, we should be able to boot any mainline Linux distro in a VM, if someone writes an app for it, as AVF (Android Virtualization Framework) is just a wrapper around Linux KVM with some restrictions. (for now the built-in app only supports Debian)


Oh wow, cool story about Yasuke. Is that where Yakuake got its name from?
Most people dont use dark mode on Linux because most apps look horrible in Linux under dark mode
Among my friends, dark mode users hugely outnumber light mode users, I really don’t have any apps that struggle to support it. LibreOffice used to be really bad, but I don’t really edit documents anymore, so I don’t use it often, but when I do, I don’t see issues (although the document background is white, because paper, so the contrast is a bit weird). I’m curious about which apps didn’t work for you.
In Hungarian it says “segglyuk”, but that means “asshole”. It should be “segg” to match “ass”.


Well, the routes might manifest somewhere as files, but I don’t expect anyone to be able to viably parse them without commands like ip or ifconfig (or know where the files even are).
Some devices (like disks for example) are very straightforward to use as files, while some other special files (like USB devices) are so weird/ugly to use that everyone uses tools/libraries to access them (like libusb).
This is very off-topic, but there’s a great talk by Benno Rice that talks about this (among many others): https://youtu.be/9-IWMbJXoLM


They aren’t asking about changes to a file describing the routing config, rather the actual in-use routing config. Unless the routing rules are modified through a couple of files (which I doubt), this doesn’t answer the question.
Cool commands though.


I don’t know anything about how Firefox is packaged for snap, but snap’s “sandboxing” might interfere with getting all fonts.
You might want to try using Firefox without snap (which has some other benefits, especially around startup time) or adding ~/.local/share/fonts (which is where fonts are supposed to be installed for users) to some sort of allowlist.
Last time I checked the Snap Store was proprietary. While you could modify the Snap client, you can’t host your own store and you’re at the whims of Canonical for which apps you can get.
Meanwhile, both the Flatpak client and server are open, and you could (and some distros do) host your own repo. For example, Fedora has its own repo for Fedora-packaged Flatpak apps alongside Flathub.