I’m not sure if it’s related, but have you already tried changing adaptive sync options?

100% agreed, use the right tool for the right job, that’s what the author doesn’t get

This is just one of the comments on the Revolt E2EE issue, I guess the author felt so proud of their opinion to make it into a blog post, I wouldn’t say anything if they at least revisited the whole discussion and tried to make a reasonable summary.
The argument provided in the article against features is simply “too hard to develop, too hard to maintain, nobody cares enough”.
If nobody cared, nobody would go on Matrix, if everything that was hard to develop were just dropped before even trying, we would have stopped at the hello world (not implying I’m not a lazy developer, but I surely don’t want to imply that there aren’t brilliant people out there who can undertake scarily big tasks).
Giving another feature as a sort of replacement: federated identities, is not a replacement at all, it’s a completely different scope. I just can’t empathise with the point that they try to make

Roll the credits boys 👏👏

when during job interview the recruiter ask if you code on the weekend

I think it’s more to see if you’re actually passionate about what you do and you don’t “just” do it for work, which definitely is a bit of a twisted view, when on average you’ll already be spending 40 hours a week doing that, but I think people tend to make this sort of evaluation, because people who love programming so much to also do it on their free time will usually be better, since they simply have more experience than those who only do what they’re assigned to do

They kinda did in the README, though that’s not really how you comply with the license

What were they?

all software is shit

Based

I rudely agree with your opinion

Never done anything with 2 mics, so I’ll just throw a vague suggestion: there’s Helvum to combine the mic inputs and then Easy Effects that can apply a few noise suppression filters that can do world of a difference, maybe the first isn’t even necessary, while the second is the core and can be tweaked a lot

Let the Zucc feel the heat

I see.

tor has geo location issues.

Could you explain what you mean with this? I’m not sure I understand

mullvad for looking shit up on ecommerce sites with new ID each time

Is it sufficient? I’d always assumed it was easily targetable with the IP so I started using TOR for that purpose

That’s fair, I won’t say that it’s not as complicated as it sounds because I don’t know what you know, but if you want it put into simple words, it’s the following:

1. Install drive 1 in PC
2. Install Windows
3. Remove drive 1 from the PC and put drive 2 in its place
4. Install any Linux distro that comes with GRUB as bootloader (most of them, personally recommend Fedora if you want a suggestion)
5. Install drive 1 into the second slot that was left empty up to now
6. Start boot, your motherboard will have a specific key to launch the boot selector, e.g. F10, or go into the UEFI settings to put the Linux option first
7. Boot into Linux and trigger the GRUB detection for other OSes so it updates the list of entries
8. Reboot
9. Now without having to smash a random key to get the built-in boot selector, you will instead be able to choose comfortably from GRUB.

Anyways don’t pressure yourself into doing any of that if you don’t feel comfortable with it, of course.
One step at a time, the important thing is you’re satisfied with what you have and that it’s functional to your workflow

Why use git exactly? You’re never changing the content of the files themselves (excluding the effect of lossy compression) so you also don’t need to track those changes, right?
This seems more like a job for rsync.

Aside from that, I don’t know more for how to achieve the full setup you’re trying to create, sorry

You just need to run the installation with one drive at a time if you want to be extra sure, then each will have its own boot partition and they can still work together, for example I have 3 drives, one Linux, one Windows and one storage, the Linux one has GRUB on it and it detects the bootloader on the Windows drive just fine so you can select either from that or the UEFI boot selector. Never had updates scramble anything for neither of the two systems

The tool presents a significant privacy risk, and shows that people may not be as anonymous in the YouTube comments sections as they may think.

I don’t understand how this makes the privacy on YouTube any worse when all the information it sources from is already public, this is just automated doxxing, which, while we’ll agree to be unethical, was never a privacy violation, it is just the consequence of the actions of who posted the information to begin with.
Also does it really violate YouTube’s privacy policy? It’s new to me that service consumers can be subject to the policy when it’s not the third parties that YouTube actively sends the information to, that sounds more to me like Terms of service, which are hardly enforceable fully (thank goodness, so we can have our yt-dlp and PipePipe)

As I went further down the article, Wick just became this badass code fighter that killed OSTree with a single line of code in my mind

That’s different, it’s technically possible not to comply with that statement because the location data is sent and stored, it takes just not deleting it to violate that, it just evaluates to a pinky promise that has to be verified by inspecting their systems.
This, on the other hand, is a technically verifiable claim, the code is open and it all runs locally on the same machine, the TEE will give the green light and that’s how apps will accept your biometric verification, the only thing that might be suspicious is with the implementation of the TEE, I don’t know if every manufacturer keeps the data it gets on the device or secretly communicates outside, this unknown is also a good reason to use a Google Pixel device if you care about that

Google Pixel phones use a TEE OS called Trusty which is open source, unlike many other phones.

From the Privacy Guides Mobile phones page

I’m all for not giving more data points where it’s not needed, but is this as bad it seems? All biometric data remains stored on the device, it isn’t sent to Google, or any app for that matter, that’s how the API works