ryuuchin
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...
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/...
[1] https://docs.microsoft.com/en-us/windows-hardware/drivers/au...
It's not really recent (2018) just that it's still being used after all this time. If you're using a default config on the home router you're basically already fine (save for changing the default login).
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.
https://www.realworldtech.com/tile-based-rasterization-nvidi...
He describes it as "tile-based immediate mode" in the article and the video should go into more detail about it. It's been a while since I watched it.
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...
[1] https://blogs.technet.microsoft.com/secguide/2017/06/15/drop...
[1] https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium...
[1] https://mpv.io
[1] https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-l...
I would recommend "Medium mode"[1] as defined in the uBlock wiki.
[1] https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium...
This is just my opinion but both have better and more intuitive interfaces as well.
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.
Also unless you get the Verizon version it's going to be unlocked so you can load whatever you want on it.
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.
Edit: On second thought some of what I wrote is probably not correct[2].
[2] https://twitter.com/CopperheadOS/status/852833915073056769
I'm not entirely sure how things stack up now. In the past I never had much faith in the vanilla linux kernel.
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).
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.