HN user

ryuuchin

455 karma

warpsharpened

Contact: theryuu@warpsharp.info

Posts0
Comments165
View on HN
No posts found.

These are available on Weatherbell[1] (which requires a subscription) now except for the HGEFS ensemble model which I'm guessing will probably be added later. AIGFS is on tropical tidbits which should be free for some stuff[5]. I believe some of the research on this is mentioned in these two[2][3] videos from NOAA weather partners site. They also talk about some of the other advances in weather model research.

One of the big benefits of both the single run (AIGFS) and ensemble (AIGEFS) models is the speed and (less) computation time required. Weather modeling is hard and these models should be used as complementary to deterministic models as they all have their own strengths and weaknesses. They run at the same 0.25 degree resolution as the ECMWF AIFS models which were introduced earlier this year and have been successful[4].

Edit: Spring 2025 forecasting experiment results is available here[6].

[1] https://www.weatherbell.com/

[2] https://www.youtube.com/watch?v=47HDk2BQMjU

[3] https://www.youtube.com/watch?v=DCQBgU0pPME

[4] https://www.ecmwf.int/en/forecasts/dataset/aifs-machine-lear...

[5] https://www.tropicaltidbits.com/analysis/models/

[6] https://repository.library.noaa.gov/view/noaa/71354/noaa_713...

The browser isn't exposing it to websites. It's simply due to the fact of playing media that it's lowering the minimum timer resolution on Windows. In the past it would also do this when just scrolling among other things if I remember correctly, I'm not sure if it still does this.

Firefox uses a different method that doesn't require lowering the minimum timer resolution.

Either way the global behavior of this is no longer true on modern Windows 10/11 machines (as of Windows 10 2004) as each process must now call timeBeginPeriod if it wants increased timer resolution: https://randomascii.wordpress.com/2020/10/04/windows-timer-r...

https://learn.microsoft.com/en-us/windows/win32/api/timeapi/...

I can't speak to Google forcing DNS, I don't know if this is true. However, it will respect the private DNS option (DNS-over-TLS) which you can point to whatever you want (like NextDNS for filtering).

Very concerned about the recent microtik CVE, as that is going to make for some very large botnets.

To be pedantic there is technically no recent Mikrotik CVE WRT Meris. It was patched in 2018(?) shortly after discovery.

From their response to the Meris botnet[1]:

As far as we have seen, these attacks use the same routers that were compromised in 2018, when MikroTik RouterOS had a vulnerability, that was quickly patched.

Unfortunately, closing the vulnerability does not immediately protect these routers. If somebody got your password in 2018, just an upgrade will not help. You must also change password, re-check your firewall if it does not allow remote access to unknown parties, and look for scripts that you did not create.

It goes into more detail to further check/harden the device in the blog post. A lot of issues stem from having Winbox or other admin access not properly firewalled off and open to the world. Blessing and a curse of the power you have with these devices I guess.

[1] https://blog.mikrotik.com/security/meris-botnet.html

Browsers 8 years ago

Chrome distrusted Symantec certs when 70 got pushed to stable (at the end of October)[1]. Digg shows NET::ERR_CERT_SYMANTEC_LEGACY error when I navigate to it. Firefox was supposed to remove the Symantec certs in 63 (also to be released at the end of October) but I guess they pushed it back a version[2].

All major browser coordinated to distrust the certs at the same time.

[1] https://security.googleblog.com/2017/09/chromes-plan-to-dist...

[2] https://blog.mozilla.org/security/2018/07/30/update-on-the-d...

If you're using uBlock Origin or uMatrix to block third party scripts it won't matter. That's what makes using the dynamic filtering in uBlock Origin so powerful. Easily the best bang for your buck ad blocking that you can do.

I would say this used to be the case but now they've made a significant effort in order to improve reliability. It's not surprising that there's a bunch of old stuff still around.

Just look at how long it took them to implement replay and a sandbox mode. I'm not sure how much of that was design decisions or was simply because of all the old crap they had to get rid of.

It's 3 years now with the Pixel. The Google branded devices have always received timely updates. That's the only point I was trying to make. I'm not saying this is ideal, just pointing it out.

Also unless you get the Verizon version it's going to be unlocked so you can load whatever you want on it.

The obvious thing to say is to just get a Nexus/Pixel device and enjoy your updates but I'm sure this isn't an option for some people.

I think the best thing that you can do to ensure you still get security updates is either make sure you get a device with an unlocked bootloader or hope there's a root exploit available so you can put something like LinageOS[1] on it.

I picked up an Essential Phone (on the cheap) for the former even though they appear to be getting timely updates so far (one day behind pixel) if you're willing to sideload with adb (and promises of support for 3 years). Also managed to grab it for < $150 TOTAL (sprint lease after buyout on day 1). They really seem to want to offload some of the stock.

I don't think I'll ever buy an android phone that's not a pixel (formerly nexus) that's not unlocked again.

[1] https://lineageos.org/

Edit: On second thought some of what I wrote is probably not correct[2].

[2] https://twitter.com/CopperheadOS/status/852833915073056769

Back when grsecurity was still public I would've said that using it with Chrome provided the best security you could get on Linux. Between the defensive mitigations it added through PaX and all the other little things (like making chroots actually behave like jails) it greatly increased security. This is without even using any MAC system.

I'm not entirely sure how things stack up now. In the past I never had much faith in the vanilla linux kernel.

Chrome disables all win32k syscalls in its renderer/extension/plugin processes (at the very least flash and pdf). This has been the default for a while now.

I believe the specific win32k syscall filter you're referring to (where you can white/black list specific syscalls) is still only accessible to Microsoft applications (Edge uses it).

Safe browsing is now built in to Firefox (and Chrome) so I'm not sure what you're seeing there. It hasn't shipped as an addon for quite some time.

If you know the name of the field trial you should be able to opt-out on the command line provided you use the correct syntax with the --force-fieldtrials option.

However it was not established whether or not field trials (A-B testing) was even the problem merely that they existed on the chromium processes. Even the stable version of the browser will likely have these options on the command line.