I use the assistant, because it has so many models to choose from. I hope they can make a mobile app for it in the future

You can say the same thing about any US AI company. Of course the local terrorists want in

I’ve found Kagi has been good enough to justify the subscription price. I like that I can block certain sites, pin and promote others. It has some neat AI features but they only activate when requested and never replace actual results.

The marginal extra disk spaces used by flatpak really isn’t a concern for most users, much less valve. If you do everything in flatpak and your apps only use current runtime versions, the additional space used by flatpak is in the megabytes, since libraries like libc are going to be on your host no matter what.

Not necessarily. If you trust the code running on your device then there is no backdoor they could install on a server that would break e2ee. They would have to backdoor the client where the keys are.

If it’s anything like ChromeOS, it’ll be a VM where you can do whatever you want, within that VM.

In the branding, but the name of the installed applications in the UI do not contain “gnome”.

Is gnome that bad? They seem to have been moving away from weird names for many years now.

continuously fighting against awful software

Arguably this is why some people don’t bother with a VM and use the web apps instead.

Most streaming services don’t do comment sections. That’s mostly a YouTube and TikTok thing where the sites depend on user submitted content and also function as a social network. Despite this, people talk about shows on those services, just elsewhere.

VSCode’s vim plugin is pretty great for full-color graphical terminal users

The part you’re missing is that while C++ does have newer safer ways of doing memory management, all the old ways are still present, in wide use, and are easier. Basically, C++ makes it easy to do the wrong thing and hard to do the right thing, and most codebases are built around the wrong things. It’s often easier to just rewrite it in rust than it is to refactor an existing code base, so if you’re going to expend that effort why not do it in a language that has stronger safety guarantees, a better dependency and build management system, and a growing community?

I guess I don’t see the point of removing pocket from the build since it can be disabled in a standard Firefox build with a single about:config option. That’s what I do.

Taint analysis is a real thing that several papers have been published about, but the implementations aren’t in a state where they could be run in real time without massively hampering performance. Also they’re mostly focused on findings bugs in native applications rather than privacy on the web.

Heretical, you will burn in hell

True Temple OS has no networking

Tor browser is something else, I don’t group it in with stuff like Librewolf.

For librewolf, I just took a look to try and figure out what binary blobs are being talked about. This is the repository I was looking at, I think its the right place: https://codeberg.org/librewolf/source/src/branch/main. There isn’t much documentation on the patches besides the file names for the most part, but do you have any idea which of these relates to binary blobs? Or is it in the settings file? Really nothing I see here convinces me that this project is worth anybody’s time over regular firefox, it just changes some defaults, disables pocket (they patch it out, but there’s already a setting), and changes the branding. I don’t disagree with most of their changes, I just don’t see the point of maintaining and marketing an entire derivative browser for what could just be a settings hardening guide on a wiki somewhere.

I do genuinely believe that these Firefox forks are mostly pointless rebrands of Firefox to satisfy a small crowd of people who are fine with Firefox but don’t want Firefox or Mozilla branding. Other than branding, they tweak the default config, pre-install ublock origin, and that’s about it. I guess this one exposes some already existing about:config flags in the settings UI. The best part is they are managed by small teams that run a few versions behind Firefox persistently, leaving 0-days unpatched and thus their users vulnerable. Their small userbase also opens their users up to tracking that wouldn’t be possible with larger browsers.

This is how I would describe my experience. Sometimes it’s crunch time and most of the time it’s fuck around time. After crunch time I always throw a tantrum about how if we only bothered with planning we could largely avoid it.

Instruction decoding takes space and power. If there are fewer, smaller transistors dedicated to the task it will take less space and power.