tomatoely

joined 2 months ago
[โ€“] tomatoely@sh.itjust.works 12 points 19 hours ago* (last edited 19 hours ago) (1 children)

When an app supports linux, it can do so by either:

  • packaging it for popular distro repositories,
  • giving instructions on how to build the app from the source code

or

  • package it on distro-agnostic, package management solutions like flatpak or appImage.

These last ones are sandboxed environments. That means they have their own dependencies isolated from your system, so they dont have to deal with every distros pecularities at the cost of using more storage space. This is very useful for developers and in your case benefitial for the user because you can have both steam and zoom via flatpak on mint, arch or any obscure distro that has flatpak available, without any major problems.

Edit: Formatting

[โ€“] tomatoely@sh.itjust.works 5 points 1 month ago* (last edited 1 month ago)

Oh yeah. My initial plan was to install termux on it and use it as a server for a simple webpage I wanted to make, but the official rom i had was 32bit and the newer termux releases only support 64bit os.

I was going to give up, but while digging for more info I found out that for some reason the chip on my moto g4 was 64bit but not the OS. So I searched in the depths of the xda forums for a 64bit rom, which resulted in way too many dead links and dubious sources. Ended up using some obscure anime themed custom rom that crashed whenever I wanted to open the camera or use the flashlight BUT, it installed and ran termux nicely.

Overall I got what I wanted, but there wasn't any good quality rom I could find as they all had some sort of flaw. Hope you get better luck though! Those phones are still perfectly usable if not for lack of software support

[โ€“] tomatoely@sh.itjust.works 14 points 1 month ago (5 children)

For the moto E4, Motorola has a guide in their support site to unlock the bootloader. I used it to be able to flash a 64bit rom for my moto g4 plus and the process was pretty straightfoward, although you do need a pc to use the adb command line tool.

Kinky cazzu ๐Ÿ˜ˆ

 

As Google tries to hinder ad-block extensions with their new platform Manifest V3, it seems to me Chrome or any Chromium derivatives are no longer a viable way to browse the web safely. So it got me wondering, how much big of a task would it be to still suport Manifest V2 on newer releases of Chromium? Maybe implement some legacy option for backwards compatibility with older extensions. I think it would be a great alternative to have, but I haven't seen anyone coming up with something similar.

[โ€“] tomatoely@sh.itjust.works 1 points 2 months ago

I know it is an old post, but I have the same cpu in my hackintosh and also encountered this same error, but later on fixed it! Turns out I was following the instructions of coffee lake cpus instead of kaby lake (very intuitive naming scheme, intel) for the config.plist. If you're still interested I can share you my EFI folder, see if you can fix the error