kccqzy

Many other Electron apps also have a web version. I just make them pinned tabs in my Firefox.

> As people need to review more and more pull requests, time spent scrolling adds up

I can’t believe people would write this as the justification. You can press PgDn on your keyboard a few times or just End once to go to the bottom. If you are on a MacBook and your keyboard doesn’t have these keys, press Fn-Down instead of PgDn and Fn-Right instead of End. When done, use the opposite keys (PgUp/Home/Fn-Up/Fn-Left). I have never once found that scrolling takes too much time.

That doesn’t make sense. I use my own global git ignore all the time because there are files that only I produce that I definitely don’t want committed (flycheck looking at you). A fresh clone wouldn’t contain these files because they are not committed in the first place. You will have to use a non-git transport mechanism to transfer the repo without also transferring your global git ignore.

Anyways this probably indicates that these repos don’t have a good code review process. The settings.local.json file name screams it’s local and shouldn’t be committed.

Yet another person who is unaware of TCC. I guess you are one of the lucky ten thousand today.

You misconfigured your security settings for your terminal app. You need to give it full disk access, or otherwise just open the folder in Finder.

Perforce is not bad, but using exclusive locking is just bad practice, for both humans and agents. Especially for agents. Agents are good at resolving merge conflicts.

Not a wild take at all. Most server use cases already use containers to precisely specify what the server workload depends on, and can only access what's in the container. I see no reason for the base system to move slowly with proven versions. Even if you don't use containers, you most likely already use language-specific tools to lock in your dependencies. Leave these to the app developers and the sysadmin can move at any speed.

The kind of security researchers who prefer to be entirely anonymous are not seeking monetary rewards from bug bounties. No company would pay such researchers anonymously (like using Monero). If they accept bitcoin well they aren’t really that into being anonymous.

My employer has similar plans. Ubuntu 24.04 will be the last Ubuntu release in use for production. Once the support period ends, we are migrating to NixOS.

Not just construction site supervisors, but the actual workers also do around-town driving. Range is a nonissue for them. Driving from your home to the supply store to the customer site and back does not usually require 90 miles of driving.

In the age of AI, there are only more and more security vulnerabilities to be discovered, and backporting all of them to outdated kernels will be nigh impossible. I’d not rather make such security patches dependent on the timeliness of backports especially if it is done by a distro rather than upstream. I suggest you use a rolling distro rather than anything with LTS kernels. The CVE in the original post CVE-2026-98432 is fixed since 7.3. If a distro doesn’t offer kernel 7.3.1 today, rule it out. (7.3.3 is also out today.)

In general I find distros using old kernels annoying because Linus treats compatibility seriously and “don’t break use space” has been a mantra for many years. On desktops in particular, GPU driver improvements like https://www.phoronix.com/news/Linux-7.3-DRM make it super worthwhile.

As for exactly which distro, it matters less than you think. I use openSUSE Tumbleweed but plenty of my friends prefer Arch.

First, the intended customers of the Cybertruck don’t need to haul anything; it’s a lifestyle vehicle. Second, EVs have solved the torque problem.

When done properly (i.e. in LaTeX with microtype, with good line breaking algorithm and character expansion) justified text is easier to read. The web is not that.

What if your coding project is related to wine? So you would want facts about wine to be inside the weights, not through web search.

Yeah I agree. I also think western tech companies try not to display the fact that they could know a lot about you in their content recommendation algorithms as a sign of deliberate restraint.

In contrast go try out a Chinese social media such as Rednote, and the recommendation algorithm is creepily good at displaying that it knows what content you like. Yes it does feel creepy. But in this case I wanted it to know my interests.

Your comment is self-contradictory. In one sentence you say “these days” and in another you say “never, ever.” These are contradictory. What if your computer is so old that it doesn’t have a TPM?

I was already pointing out that if you have secure enclave for your private key you should use key-based authentication. That’s what I do on iOS. Otherwise a password is better than your private key in plain text on disk. So much malware steal your private SSH keys (along with your other saved passwords and browser cookies); no malware that I know of performs social engineering and tricks you into giving up your SSH passwords.

C99 and all subsequent versions.

As a kid I watched my mom produce plots in Microsoft Excel and even then as a first grader Microsoft Excel had a pretty steep learning curve. Some school computers had the whole creative suite, from Adobe stuff like Photoshop to Macromedia stuff like Freehand and Fireworks. All of these seemed overwhelming to me when I was in the first few years of elementary school. It only began to make sense in the later years of elementary school and in middle school.

Yeah because if attackers are already finding a way in, they can easily read my ~/.ssh/id_ed25519. A password is strictly better, although not by much because lateral movement is very easy anyways. The only exception is if the private key is actually on a HSM, which is the case for all my SSH private keys on iOS.

I run SSH with password authentication on but the port binds to a ULA address. It’s fine. No need to be so absolutist.

Yeah very sorry for the confusion. I should not have used the word strictly. I explained my definition of strictly in the above comment and it’s not really strictly in the dictionary sense. I apologize for my bad writing.

LPEs are frequent enough that people no longer use low-privilege user accounts to sandbox potentially malicious software. They are only used to control access for well-behaved users without any intent to subvert the system, not attackers.

The difference here reminds me of the distinction between the regular Paxos algorithm and the Byzantine Paxos algorithm.

Yeah that’s what I mean by strictly. Does your implementation take shortcuts or does it hold itself to a higher standard and not do that? Does it only use available memory as the ultimate limit?

A lot of specs contain these optional limitations. The C standard allowed implementations to truncate variable names to 31 characters if they have external linkage and 63 if internal linkage. Would you be happy if your implementation actually does that? Of course not. Neither LLVM nor GCC does that. That’s because people writing compilers also hold themselves to a higher standard. Now imagine this kind of attitude being pervasive.

Some languages have a culture of doing things correctly and conforming strictly to the spec. These languages have indeed sorted it out years ago. Haskell for example. Any language that doesn’t have a special number type for JSON is a half-assed implementation, because 1e1000 is a perfectly valid JSON number that is beyond the typical IEEE754 double precision floating point numbers; does your language handle that correctly? Haskell does. This is but a small example of a strong culture bias towards correctness.

People love to throw out these buzzwords describing their ideal “maximum security” setup suitable for “sensitive production workloads” without ever defining what the threat model is.

The most grating thing is requiring every workload to be in a dedicated VM. You are throwing so much performance away. What kind of threat model would justify this? Usually there’s no threat model analysis at all.

Banning opensshd is again mostly a fool’s errand. It’s much more productive to design a system that writes the authorized_keys file read by opensshd. For example you can design a system that requires peer approval before your own key gets written to authorized_keys.

A pet peeve of mine is websites thinking oh you prefer dark mode so let’s make the background pure black. I cannot take it because the contrast is too much: #fff on #000 is way more uncomfortable than #000 on #fff for me. There are certain developers who continue to think that dark mode is for conserving battery life with an OLED screen so pure black is preferable. I hate that so much that I have turned off dark mode globally. If websites can’t be bothered to implement an actually nice dark theme like Solarized Dark, I’d rather prefer the light mode.

Besides Solarized Dark, GitHub’s Soft Dark theme is quite well done, but unfortunately it’s not the default for a logged-out user with dark mode. So with dark mode I need to log in to GitHub to get acceptable colors.

Now that I think about it, I need a feature to limit the darkness of colors anywhere on the page, background or text except images. Remap #000 to #222 and #fff to #ddd.

Wikipedia allows you to write any custom CSS. In 2012/2013 when Facebook IPO’ed and was the cool thing I made a user CSS that made Wikipedia look like Facebook.

It’s not. The feature is implemented deep within WebKit so it makes sense to be on this blog.

> It’s precisely because Adaptive Dark Mode is happening deep within the WebKit browser engine that we are able to find creative ways to solve the most complex challenges, apply the transformations with great speed and power efficiency

Browsers lie all the time. Browsers also prevent sites from getting the color of a link because visited links can be shown in a different color and this can be used by the site to tell if a user has ever visited a link.

Don’t you love it when browsers lie to websites to enhance the user’s privacy.

Historians actually would love this. Currently many historians try to reconstruct how life was like centuries ago from accidentally preserved artifacts. Future historians would have no trouble understanding how our daily life is like.

Amazing article. It just goes to show how many problems they are solving just to work around bugs and limitations within Apple itself. I’d wager a guess that if Apple made a new Xserve with the same performance as a Mac mini but twice the price people would still buy them, because figuring out data center operations is expensive.