HN user

bilkow

429 karma
Posts5
Comments153
View on HN
98% isn't much 15 days ago

Ah you're right! You were actually very clear by saying Android 9 or below, but I misinterpreted while multitasking here, sorry for that.

If you're arguing that it is Google who is dropping support/making people have insecure browsers, we're in agreement. As with Safari (or at least those at Apple who control/fund Safari), the Android team is very anti-Web/Chrome. Lots has been written about all of that at https://infrequently.org.

Oh, haven't seen that blog before. Incredible resource, thanks! And yeah, Google, Apple, and also a situation with vendors (e.g. Qualcomm, due to drivers) that makes it so miserable. Not only due to the way they favor their stores, but also indirectly due to how hard they make to have updated or custom OSes for older devices. I believe it's a consequence of the amount of control they exert, Apple by plainly not allowing bootloader unlocking and Google by gatekeeping essential APIs (especially Play Integrity) on "secure" (read: controlled by Google) OSes.

It's a bit insane that we live in two completely different realities on desktop vs mobile, where it's easy to install a current OS and browser in 15+ year old computers but can't even have an up-to-date browser on an 8 year old device, much less and up-to-date OS.

98% Isn't Much 15 days ago

There seem to be updated stats here: https://composables.com/android-distribution-chart

Which seems to indicate about 4.8% are below Android 9.

But also, Firefox for Android still supports Android 8, of which there are 1.7% below.

There's a discussion to be made here about who is dropping support for these users, is it Google (and especially Apple, who doesn't allow other browsers on iOS) or the site owner? Especially given how insecure it is to use outdated browsers.

Sorry, I am a bit confused about the caching delay, which seems to suggest you can switch kernels without rebooting? That's not what the wiki suggests[0], and what even happens to running programs?

Or do you mean just changing the "default" boot to a different kernel, which in other distros would require changing the boot loader config?

[0] https://nixos.wiki/wiki/Linux_kernel

If they have access to the "dark web" they can already do anything that requires age verification there. In the same way you expect that the rule to "not sell UUIDs" wouldn't be respected there, I wouldn't expect other age-verification rules to be respected, no matter the verification method.

Have you checked the install date? I'm not sure which are the compromised version numbers, but if they were installed before June 10 you're probably safe. (I think libgdata 0.18.1-5 used to be on the main repos in February, and has recently been downgraded to AUR, so you may be fine).

Only packages from AUR have been compromised, meaning a normal update `pacman -Syu` won't install them, they'll only be installed by `makepkg` or AUR helpers (such as `paru`, which asks you to review the PKGBUILD diff).

Also, if you had installed a compromised version, uninstalling the packages is not enough, you'd probably need to reinstall your system and rotate all credentials. More info here and on the linked blog: https://discourse.ifin.network/t/400-aur-packages-compromise...

I mean we got relativity because of a minor discord with newtonian Laws. (the orbit of Mercury).

I don't think that's true. One of Einstein's test for General Relativity, using Mercury's orbit, came around 10 years later after special relativity was proposed, which is understood to be motivated by both Maxwell's equations and experimental results suggesting that the speed of light (electromagnetic waves) not depending on the frame of reference. General relativity (explaining gravity) seem to have been motivated by Newton's gravity not playing well with Special relativity (with mass being relative and all).

I understand the frustration with Dark Matter, but my understanding is that Dark Matter is a guess that is known to be incomplete. Scientists are shooting everywhere to try to explain the discrepancy in gravitational effects and some form of undetected matter is currently the best hypothesis (but not the only one). You say that "we accept 90% observation disaccordance", but the source of its effect is being searched for.

See:

- https://hsm.stackexchange.com/questions/622/what-was-einstei...

- https://en.wikipedia.org/wiki/History_of_gravitational_theor...

- https://en.wikipedia.org/wiki/Tests_of_general_relativity

Edit: formatting, updated links

This is how I'd do it:

    jj new branch1 branch2 branch3
This creates an empty commit that merges all 3 branches, you can think of this as your staging area.

When you want to move specific changes to an existing commit, let's say a commit with an ID that starts with `zyx` (all jj commands highlights the starting characters that make the commit / change unambiguous):

    jj squash -i --to zyx
Then select your changes in the TUI. `-i` stands for interactive.

If you want to move changes to a new commit on one of the branches:

    jj split -i -A branch1
Then select the changes you want moved. `-A` is the same as `--insert-after`, it inserts the commit between that commit and any children (including the merge commit you're on).

There's one thing that's a bit annoying, the commit is there but the head of the branch hasn't been moved, you have to move it manually (I used + to get the child to be clearer, but I usually just type the first characters of the new change id):

    jj bookmark move branch1 --to branch1+

I'm curious on the source for these "facts".

- You state that PPA is enabled by default, but it was an experimental feature that was never activated and later removed: https://support.mozilla.org/en-US/kb/privacy-preserving-attr...

- You state that Sponsored “Privacy-Focused Direct Results” were added to address bar, but 1. it's direct results in general, with some being sponsored and 2. it hasn't been released: https://blog.mozilla.org/en/firefox/better-search-suggestion.... The pref defaults to false in current stable.

- Yes, Anonym is an ad metrics firm, but you missed that it's focused on privacy. I am unsure whether they are actually able to achieve privacy or if it's just privacy-washing, but that's their stated goal. https://www.mozilla.org/en-US/anonym/

- Privacy FAQ and TOS changes are true, but they rolled them back after backlash: (updated) https://www.thebridgechronicle.com/tech/mozilla-revises-fire... , (original) https://arstechnica.com/tech-policy/2025/02/firefox-deletes-...

- Privacy Notice update is true: https://www.mozilla.org/en-US/privacy/firefox/update/dec2025...

I don't really understand the point you're trying to make, I don't see anywhere in the post nor the title claiming the purpose changed and the title is directly related to the content. In fact, it seems like you are just agreeing with the post.

I think people can get frustrated at CI when it fails, so they're explaining that that's the whole purpose of it and why it's is a actually good thing.

I would personally actually frame it slightly different than the author. Non-flaky CI errors: your code failed CI. Flaky CI errors: CI failed. Just to be clear, that's more precise but would never catch on because people would simplify "your code failed CI" to "CI failed" over time, but I don't thing that changes it from being an interesting way to frame.

Even if the false-positive rate is very small (e.g. 0.01%), you probably won't be affected, but more than a hundred thousand of websites would be and that would still be an issue. I have no idea how big is the false-positive rate.

There are many of reports of the same happening to other sites, some of the top ones (you can find many more by searching HN for "google safe browsing"):

- https://news.ycombinator.com/item?id=33526893

- https://news.ycombinator.com/item?id=25802366

- https://news.ycombinator.com/item?id=45675015

You don't need primary selection to avoid the keyboard, you can also hold right-click on your selection and release it on "copy" (or right-click on your selection then left-click on copy, more intuitive but slightly more cumbersome)

I agree it's less convenient (there's an extra step: explicitly copying the text), but in my experience it's also more reliable as you don't lose it by just selecting anything.

I mostly agree, but a generalized attack at the remaining GitHub workers by calling them "losers" and then "rookies" is unwarranted and leaves a bad taste IMO.

See the edit history here: https://news.ycombinator.com/item?id=46133179

Edit: 1. just to be clear, it's very good that they have accepted the feedback and removed that part, but there's no apology (as far as I know) and it still makes you wonder about the culture. On the other side, people make mistakes under stress. 2. /s/not warranted/unwarranted/

It's probable that licenses that explicitly allows revocation at will would not be approved by OSI or the FSF.

Copyright law is also a complex matter which differs by country and I am not a lawyer so take this with a grain of salt, but there seem to be "edge cases" where the license can be revoked as seen in the stackexchange page below.

See:

https://lists.opensource.org/pipermail/license-discuss_lists...

https://opensource.stackexchange.com/questions/4012/are-lice...

I think you are correct, but you probably misunderstood the parent.

My understanding of what they meant by "retroactively apply a restrictive license" is to apply a restrictive license to previous commits that were already distributed using a FOSS license (the FOSS part being implied by the new license being "restrictive" and because these discussions are usually around license changes for previously FOSS projects such as Terraform).

As allowing redistribution under at least the same license is usually a requirement for a license to be considered FOSS, you can't really change the license of an existing version as anyone who has acquired the version under the previous license can still redistribute it under the same terms.

Edit: s/commit/version/, added "under the same terms" at the end, add that the new license being "restrictive" contributes to the implication that the previous license was FOSS

200 languages that are actually used

Do you have any reference of that or are you implying we shouldn't support the other thousands[0] of languages in use just because they don't have a big enough user base?

And the fact is that the author of the web page doesn’t know the language of the content, if there’s anything user contributed. Should you have to label every comment on HN as “English”? That’s a huge burden on literally every internet user.

In the case of Hacker News or other pages with user submitted and multi-language content, you can just mark the comments' lang attribute to the empty string, which means unknown and falls back to detection. Alternatively, it's possible to let the user select the language (defaulting to their last used or an auto-detected one), Mastodon and BlueSky do that. For single language forums and sites with no user-generated content, it's fine to leave everything as the site language.

Other written language has never specified its language. Imposing data-entry requirements on humans to satisfy a computer is never the ideal solution.

There's also no "screen reader" nor "auto translation" in other written language. Setting the content language helps to improve accessibility features that do not exist without computers.

[0] https://www.ethnologue.com/insights/how-many-languages/

Your whole comment assumes language identification is both trivial and fail-safe. It is neither and it can get worse if you consider e.g. cases where the page has different elements in different languages, different languages that are similar.

Even if language identification was very simple, you're still putting the burden on the user's tools to identify something the writer already knew.

You can run niri from within other DEs, but I'm unsure whether it works well for your use-case. From the docs[0]:

"You can also run niri inside an existing desktop session. Then it will open as a window, where you can give it a try. Note that this windowed mode is mainly meant for development, so it is a bit buggy (in particular, there are issues with hotkeys)."

IIRC in this case the Mod key is by default Alt instead of Super.

[0] https://yalter.github.io/niri/Getting-Started.html

My understanding is that asymmetric fields provide a migration path in case that happens, as stated in the docs:

Unlike optional fields, an asymmetric field can safely be promoted to required and vice versa.

[...]

Suppose we now want to remove a required field. It may be unsafe to delete the field directly, since then clients might stop setting it before servers can handle its absence. But we can demote it to asymmetric, which forces servers to consider it optional and handle its potential absence, even though clients are still required to set it. Once that change has been rolled out (at least to servers), we can confidently delete the field (or demote it to optional), as the servers no longer rely on it.

Why Nim? 11 months ago

(not your parent commenter)

For me, programming is about corralling motivation more than anything else. Rust saps my motivation is ways that Zig does not.

Yes, agree with you a lot! Maybe our brains are just wired differently, for me, no other language (until now) gives me as much motivation as Rust, as it's type system and docs make me feel really good.

Zig is simply a much smaller language than Rust. I use Zig because my brain isn't big enough for either C++ or Rust.

Disclaimer: haven't really tried Zig yet. IMO you don't need to keep the whole of Rust in your brain to use it, I usually can just focus on the business logic as if I make a stupid mistake, the compiler will catch it. That (and the type system) is what makes me more efficient with it than other langs. I also stay clear of lifetimes unless I really need them (which is almost never for application code). An extreme example of the opposite is C, where I need to take care about anything I do as it will just accept anything (e.g. auto casting types) so I need to be vigilant about everything.

All of that said, there are patterns that will just be harder to reason about in Rust, mostly with self-referential things, and if you area already used to using them a lot, this can be a hassle. If you're used to smaller data structures and data-oriented programming, it will be a lot easier.

This is not trying to convince you or anyone else, just showing a different perspective. If you feel better with Zig, use it! Everyone has their own experience.

though I don't think you have to launch games through the steam app, but they try to make it convenient to do so.

It depends on the game, they do offer some kind of DRM, which requires Steam to be open when launching the game, but it's optional for the developer to use it or not. See https://www.pcgamingwiki.com/wiki/Digital_rights_management_...

PCGamingWiki also usually has information on whether the game is DRM-free or not, e.g.: https://www.pcgamingwiki.com/wiki/Hades#Availability