ejs

I suggest looking at llm arena leaderboards filtered by open weight models. It offers benchmarks at a very complete and statistically detailed level for models, and usually is quite up to date when new models come out. The new Gemma that just came out might be the best for 1x GPU, and if you have a bunch of vram check out the larger Chinese models

I’m still not convinced there is a direct casual link between the merged attestation and some future surveillance. Your speculation that this is some deliberate political strategy for some gradual escalation from attestation to surveillance is not logical evidence, but some belief you have, which holds no weight in an argument; it stands that you have no concrete evidence against your logic being a slippery slope fallacy.

You did concede to my argument by admitting “by itself the attestation is pointless.” Good to know we agree that there is outrage over nothing.

By saying “PR vs merge is a moot point”, you’re running away from a logical/technical debate by being dismissive; you are openly stating you don’t care how the mechanics of these foss projects actually work. Again, you can have a speculative opinion, but that is not a logical argument.

When you argue parents should be using OS parental controls, you do know that that’s exactly what the systemd age attestation PR is building, right? It seems you’re fighting against the very infrastructure needed for your preferred solution.

Finally, you conflate local infrastructure with cloud APIs (vindicating my claim that people opposing this are ignorant to the actual code being merged): Systemd is a local init system. Connecting the local userdb age integer to an external, network reliant govt API is a monumental leap in implementation and architecture, not a simple “add this API” patch that can be quietly slipped in without the entire foss community noticing and revolting. The attestation PR, for instance, had around 200 comments, of back and fourth refining of implementation and discussion, before merge.

To be clear, I would also be outraged if some personal privacy nightmare got merged into foss projects I used.

However, adding an optional field to userdb for self reporting of age is definitely not a privacy concern. I honestly have not heard a valid argument against this addition of an optional field. Most are just appeals to emotion/outrage not grounded in the reality of what code was actually committed/merged.

Honest question: are you sure this thinking is not a slippery slope fallacy?

You seem to imply that adding self age attestation inherently necessitates ID verification.

I do not agree with this line of thinking. Instead, I reason that this PR was merged because it is not harmful, and a potential future PR implementing ID verification would not be merged. These are two separate things (PRs/merges), which are not in any way tied to each other causually.

i think subset of people online who are vocally upset about his code contributions (and harassing him, committing fraud, and so on) are ignorant to the actual charges in the PRs and only read the headline and assume he’s shoving ID verification down our throats. I primarily blame media outlets and social media accounts trying to capitalize on this outrage over nothing.

from a design perspective, consistency is key. light mode is on? then light mode means light mode, and apps should be in light mode.

do you want both your terminal to be dark theme and your gtk apps (including all of the gnome UI) to be light theme at the same time?

do you want settings within every single app in order to change from light mode to dark mode, as opposed to a global toggle that applies to every UI on your computer?

alternatively, is the terminal the only exception to this global toggle, and this design inconsistency by having the default contradict the default of the rest of your desktop environment is your preference?

i think you need to look into routing. Specifically, split tunneling.

https://tailscale.com/learn/what-is-split-tunneling-secure-critical-data-vpn

https://protonvpn.com/support/protonvpn-split-tunneling

https://mullvad.net/en/help/split-tunneling-with-the-mullvad-app

I’d recommend installing those python dependencies using apt, so that when you update your system packages, the python libraries get updated, too. Pip, on the other hand, is useful for development but is detatched from apt and you will definitely forget to pip update unlike apt update which you hopefully do frequently. Use the names of the packages the readme provides in the pip install … instruction. For example, for numpy, you can install this.

Then, since that python script has a shebang at the top, you can add it to a directory in your $PATH and mark it executable with chmod, and you can invoke the script in your shell from any directory with just the file name.