This is for file sharing, while Syncthing is for file synchronization. While you could use Syncthing for file sharing as well (and I have used it for that before), it’s definitely more complicated to use, and requires a bit more setup.

How about using M$ Edge on Linux? /s

Seriously though, one of my friends uses Edge on Windows, Linux, and Android. I still couldn’t wrap my head around his decision.

Next time you want to sail the high seas with Minecraft, try HMCL. Should be less of a hassle.

Judging by the craiglist watermark on the bottom right, it’s probably just a meme listing.

Just FYI, Arch Linux has a tool called Archiso that you can use to create live ISO image. You can copy the default releng config and edit the package list accordingly.

If you are on Plasma 6, it should be “System Settings” - Keyboard - Advanced, select “Configure keyboard options”, and you’ll find the “Caps Lock behavior” - maybe even two, but one of them have a lot of options as to what you want to do with your Caps Lock key.

Xournal++ supports other architectures. They might not have compiled binaries for other architectures ready to be downloaded on their GitHub release, but it’s packaged on at least postmarketOS (i.e. Alpine Linux) edge (I have it on my “Chromebook”) and Debian Stable.

I have a Samsung Chromebook that also has ARM SoC, 4 GB of soldered RAM and eMMC storage. I installed postmarketOS on it, with desktop KDE Plasma 6, and with 4 GB of ZRAM, it is definitely usable - I could run Xournal++ without much problem. It’s not butter smooth, the scrolling can be stuttery, but it should be enough for light notetaking. Granted, my SoC is older and weaker (RK3399), so your mileage may vary.

Translation:

今天我们吃鸡腿 - We are eating drumsticks (“The Future”) today

dog furiously eats broccoli (Wayland icon)

等下 - Wait a minute

味不对劲啊 - That doesn’t taste right

你是不是又坑我了 - You are not tricking me, are you?

我看看 - Let me see

我就知道吗 - I knew it! (⁠ﾉ⁠´⁠･⁠ω⁠･⁠)⁠ﾉ⁠ ⁠ﾐ⁠ ⁠┻⁠━⁠┻

你是真狗啊 - You are the real dog You are such a dog

Not Samsung, but I do have a Redmi 2 (also MSM8916) since I can get one for roughly $10.

On paper, the performance is closer to PinePhone (not Pro), and it would definitely be a lot less powerful than a PinePhone Pro running RK3399(S). They also typical has only 2 GB of RAM (some have even less), and that’s definitely going to be noticable. It should be fine for light use and thinkering though.

Some Samsung phones might have networking issues, and some might not even be unlockable, but I’m not really sure about it either, so definitely check before buying.

Also, not all MSM8916 is built the same - some works better than the other. Devices from the community category should be somewhat usable, but be ware of those in the testing category, since they might have major functionalities missing (e.g. touch).

You like eating eggs, don’t you?

A64 (the SoC for PinePhone) is mostly intended for set-top boxes (i.e. smart TV), so it is really not designed for power efficiency.

It’s really a bummer that most “smartphone” SoCs cannot easily be purchased, and have no proper documentations. Thinkers and smaller manufacturers are stuck with mostly Allwinner and Rockchip SoCs (most of which are engineered as embedded processors) if they want to design something from starch at all.

If you are using containers, it should be fairly trivial. Otherwise, there might be some renaming to do, but Forgejo should be 100% compatible with Gitea (at least right now). Just make sure you have a good backup in case anything would happen.

uBlacklist is what you’re looking for.

Don’t think my phone runs Nvidia… or Wayland 🤔

Let me introduce you to running postmarketOS on Nvidia Tegra SoC. /s

From what I can find it has a quad-core Cortex-A7 ARM32 chip, a.k.a Mediatek MT8321, with 1 GB of RAM and 8 GB of storage, which is not plenty for a device running Android 8.

Your best bet for running “Linux OS” is postmarketOS. But the ARM world is a lot different than the x86 world that you might be familiar with: you can’t just “install” any OS on an ARM platform, you need to port it (write code & tweak config) for each device. And the only device that has the same SoC does not look good.

So you next best choice is probably Termux. It could be installed on any Android devices, and provides a decent “Linux” environment that are pretty close to a real Linux console. Of course, it’s really difficult to run GUI applications, and running things like Docker would probably be out of the questions (ARM32 already had pretty rough Docker support as-is). But still, it’s a good way to get your hands dirty with Linux, and you can definitely use them for quite a few things: writing C or Python code on the go, get familiar with command line, or just run a few small services (e.g. SSH for remote connection, NginX for web server). The possibilities are still endless.

Now, as for the de-googling part, you will still need a custom ROM for this, and I’m not even sure if your device even support flashing third-party ROMs (some carriers would lock it down), so it might not be possible to flash an entire new OS, but someone else seemed to have already posted a potential ROM you could try. Still, you can still find some tutorials that can help you disable as much Google as possible with ADB command, which you might need to adapt to your specific device.

███████ Scratch off for password

The first link is basically an “advertisment hidden in a normal, professional-looking article”. All they’re saying is how these ways are not secure, but most importanly, how their solution is more secure, published under their own site.

When you take this into account, their claims start to break down: while yes, email and SMS MFA might be inherently less secure since the code could be transmitted via an insecure channel, saying TOTP is not not secure because “you device can be hacked” is a kinda bad take: if your device is already hacked, you’d have a much bigger problem: even if you are using security keys, the hacker would already have access to whatever service you might be trying to protect. As for the lost/stolen case mentioned in the article, if you put TOTP code in a password manager (as most would probably do if they’re doing this), that shouldn’t be a problem. The only way this would be a problem is that the TOTP secret is stored in plain text, which would be the same for any authentication methods.