If you don’t like the term “toot” it’s fine, it shouldn’t matter who coined it. Don’t make your likes or dislikes dependent on who stuff or ideas come from.
I just wanted to explain some history of that term.
The knowledge of that history and context is what should influence your taste, not the specific individuals involved.
There is a bigger history on this. Involving the Mastodon developer Gargon and a famous YouTuber Hbomberguy:
https://mastodon.social/@Hbomberguy/146524
Gargon, at that time wasn’t aware of the double meaning, as they where non-native English speaker.
It got changed back to “publish” relatively recent.
Personally I liked “toot” it was unique and funny. Many Mastodon-Users still prefer or use “toot”.
An interesting concept would be if all hand on the 12 clocks would work, but the hands of the clock in the middle are stuck at 12 position, this way the hands in the middle would point to the clock showing the correct time.
This is the same between many different software development disciplines, fpga devs (or hardware devs for that matter) vs. driver devs, driver devs vs. backend dev, backend devs vs frontend devs, integrators vs everyone.
Nix on non-NixOS distributions would be great, if it would support installing apps into the users home directory instead of a global directory (without recompiling everything).
(When I looked into it, it wasn’t possible, but if you made it work, please share.)
I used to use Ubuntu in the past, and it wasn’t Unity, Upstart, Bazaar, Mir, Launchpad, Snap, Amazon ads integration etc. that convinced me to look elsewhere, it was that I found out how other, not commercial distributions, integrated and instrumented its user base into their development.
Instead of having to sign a CLAs when contributing and signing your right away to some corporation, you become part of the community. (Update: It seems they have switched from their Copyright assignment, so something not as invasive in 2011, which is good. But they still require you to sign a CLA.)
So always look who is developing the distribution first, are they individuals or is it one company. And don’t let yourself be bated into the dependency of one company, because then you will be the victim of enshittyfication eventually.
Were I buy bread it is on a rack, and you use tongs to put it into a paper bag. You can also put it into a slicer first and then in the bag, but I rather slice it myself at home.
Or I buy it a a bakery, where some employee packs it for me, you can ask them to put it into your cotton bag, if they only have plastic bags.
I don’t buy prepackaged bread.
I don’t throw away the plastic bag, because I don’t have the plastic bag. Because the bread I bought was in a paper bag.
I you live in a country where you don’t get bread in paper bags and you want to avoid plastic waste, you can put the bread in a cotton bag in the store, which you can wash and reuse.
Nobody? That was a general statement, sorry if that was unclear formulated. I just see many people that first set a label for themselves and then try to fit into it, instead of just doing what ever they want and just use them as a short hand to explain themselves.
Well, you can always bring your own cotton bag…
Yes, and labels suck. Don’t limit your yourself involuntarily just to fit into one.
Isn’t all of it evil, because they bought bread in a plastic bag? Use a paper bag. And if the bread gets hard, steam it, bake it, and its fresh again.
So similar to kakoune? I tried that for a while, but it was missing some features so I went back to vim/neovim.
I need to know vi anyway, because that is available everywhere (as part of busybox), so using vim/nvim for bigger systems just fits.
What about Lua/Luajit?
In most scripting languages you have the interpreter binary and the (standard) libraries as separate files. But creating self-extracting executables, that clean up after themselves can easily be done by wrapping them in a shell script.
IMO, if low dependencies and small size is really important, you could also just write your script in a low level compiled language (C, Rust, Zig, …), link it statically (e.g. with musl) and execute that.
I started using Fedora Silverblue on a tablet, seems to work fine so far, but requiring a reboot in order to install new system packages is a bit cumbersome and the process itself takes a while, but ordinary Fedora also doesn’t win any races when asked to install a new package
I think switching to FCOS or Flatcar on servers that just use containers makes sense. Since it lessens the burden of administrating the base system itself. Using butan/ignition might be unusual at first, but it also allows to put the base system configuration into a git repo, and makes initial provisioning using ansible or similar unnecessary. The rest of the system and services can be managed via portainer or similar software.
I also do not have long term experience with FCOS, but the advertised features of auto-update, rolling-release, focus on security and stability makes it a good fit for container servers, IMO.
An alternative to Debian on servers might also be Apline Linux. Which also has more a focus on network devices, but some people use it on a desktop as well.
If you have many different systems, and just want to learn to operate them all, maybe NixOS might be interesting. Using flakes, you can configure multiple machines from just one repo, and share configurations between them. But getting up to speed on NixOS might not be so easy, it has a steep learning curve.
What’s ACC?
ACC - Advanced Charging Controller, which allows to set charge limits, thus extending the battery life, which should have been part of Android from the beginning,
Anyway I would strongly discourage using root under Android as it breaks the security model.
Security isn’t a binary, security works like an onion, you have multiple layers of security and multiple decisions to make on every level. Currently you might be right, that having root access to a device might compromise it in some ways, but that isn’t necessarily so and depends on how it is done.
You should find ways around using root and if you can’t you probably shouldn’t be doing on your phone anyway.
This kind of thinking is the ‘I know better than you’ mentality, that I sometimes see around people advertising GrapheneOS. Having ‘root’ permissions to the device is owing it, I want to decide what to do with it, not the vendor of the ROM, or who ever else. They aren’t me, they don’t know what I want to do with it.
The goal of security models is allowing me, the owner, to do what ever I want with my device, while preventing others, non-owners, un-trusted applications or the internet from doing what they want with my device. If the security model doesn’t allow me, the owner, to do what I want, then it failed its job at least partially.
Root is very dangerous as it can survive a factory reset.
Why is that dangerous? The first thing I do, when I get a new phone is boot into the boot loader, and overwrite the whole partition, then the system is trusted again, at least if I trust the vendor of the boot loader. When I want to do a factory reset, I do the same, overwrite the flash with a fresh OS image.
IMO, there are other reasons why the current implementation of root are dangerous: They currently considered binary and I think they could be implemented more gradually. Like one application having root over individual other applications, e.g. accessing their files. Allowing/Disallowing individual privileged system calls, or access to specific system files, etc. All of this could be hidden behind a switch in the developers menu. Maybe only allow applications to gain root access when using a registered hardware token, etc.
As for MicroG, it is sandboxed but it does require device admin for full functionality. It isn’t running as root but it requires a lot of device permissions. You can turn off the permissions you don’t need but that could break things.
In order for MicroG to work full, you need to fake the signature, which requires a patch to the system, or root privileges.
Like others already said, you can still root your GrapheneOS, there are two ways to do this:
Just unlock your bootloader, flash Magisk or whatever, done. Disadvantages, you cannot lock your bootloader again, thus creating a huge security gap where an attacker, when gained physical access to your phone, overwrites your boot partition and you boot your compromised system without noticing. Which is bad, IMO.
Recompile GrapheneOS with Magisk installed, signed it with that key and use this key in your bootloader to lock it. You essentially created a GrapheneOS fork, can no longer use their OTA update server and use the security updates, etc. You need to create this yourself.
Yeah, they don’t prevent you from doing it, the same as original ROMs don’t prevent you from doing it.
Exactly right. However all the downsides you have when doing that sort of defeats the purpose. So a GrapheneOS native way to control your device would be nice.
Well, I never really missed being able to pay via NFC on a phone, but I also never done it. My NFC chip in my card works fine.
When my baking app started detecting my rooted phone, I just switched to using their web-app via Firefox, which allows you to create a direct link to it as an “App”. Which is probably better anyway, than installing random proprietary apps on a phone. And logging into it every time is also easy with a password manager.
So I guess, as long as the banks still offer a website, I am good.
That might make it even more dangerous, because you get used to flash to usb sticks on “/dev/sda”. And when you then use a device with a built-in sata drive, you might forget checking in a hurry.
Happened to me a once or twice. I am now only using bmap tools for this.