HNHacker News
TopNewBestAskShowJobs

arghwhat

9,034 karma · joined January 12, 2017

no.
submissionscomments
arghwhat··on Edit is now open source
> You can use nano over wsl if you want

No, not when ssh'ing to a server to manage it. Pulling in a Linux VM to get a simple text editor also makes no sense.

There is also nothing to integrate - it's a basic text editor for a terminal with no fancy features. It either edits text or it doesn't.

arghwhat··on The Windows Subsystem for Linux is now open source
WSL2, in my testing, is orders of magnitude faster at file heavy operations than anything outside WSL, dev drive or not. We have an R&D department that's using WSL2 and jumping through hurdles of forwarding hardware because it's night and day compared to trying under windows on the same machine. It provided other benefits too, but the sheer performance was the main selling point.

WSL2 does not take less advantage of filesystem caches. Linux's block cache is perfectly capable. HyperV is a semi-serious hypervisor, so it should be using a direct I/O abstraction for writing to the disk image. Memory is also balloning, and can dynamically grow and shrink depending on memory pressure.

Linux VM's is something Microsoft has poured a lot of money into optimizing as that's what the vast majority of Azure is. Cramming more out of a single machine, and therefore more things into a single machine, directly correlates with profits, so that's a heavy investment.

I wonder why you're seeing different results. I have no experience with WSL1, and looking into a proprietary legacy solution with known issues and limited features would be a purely academic exercise that I'm not sure is worth it.

(I personally don't use Windows, but I work with departments whose parent companies enforce it on their networks,

arghwhat··on Edit is now open source
Yay for finally having a default text editor that works over ssh. Managing windows servers over ssh is a bit of a pain without.

They could just have packaged nano, but oh well.

arghwhat··on The Windows Subsystem for Linux is now open source
NTFS is not the problem.

The problem is Windows IO filters and whatnot, Microsoft Defender trying to lazily intercept every file operation, and if you're crossing between windows and Linux land, possibly 9pfs network shares.

WSL2's own disk is just a VM image and fairly fast - you're just accessing a single file with some special optimizations. Usually far, far more responsive than anything done by windows itself. Don't do your work in your network-shared windows home folder.

arghwhat··on What is HDR, anyway?
The problem is that it just doesn't work on modern, fast displays. Without motion smoothing on a fast and bright screen, 24fps/30fps goes from "choppy" to "seizure inducing and unwatchable". Older sets would just naturally smooth things out.

Even on my LCD TV, smooth motion like credits at certain speeds are extremely uncomfortable to look at at these frame rates.

I consider it borderline irresponsible to continue using these framerates, forcing users into frame interpolation and horrible artifacts, a decision the manufacturer might even have made for them. 120 Hz is finally becoming the norm for regular content (with monitors going to 500+ nowadays), we should at least be able to get to 60 Hz as the lower bound for regular content delivery.

Going further down for artistic value, e.g. for stop motion or actual slide shows is less of a problem in my opinion. It is not as disturbing, and if regular content was appropriately paced there would be no need for interpolation to mess with it...

> Just look at the trend of frame size.

Frame size is different from the other parameters, as it is solely a physical practicality. Bigger is better in all directions, but a cinema screen needs to fit in the building - making a building much taller is less economical than making it wider, and making it whatever it isn't right now adds novelty.

The content needs to be made for the screen with the appropriate balance of periphery and subject to not be completely wrong, so screen technology and recording technology tends to align. Economy of scale causes standardization on lenses and image circles, and the choice of aspect ratio within that circle on the film, forming a feedback loop that enforces the parameters for almost all content.

If some technology somewhere else in the stack causes a change, some will follow for the novelty but others will simply follow the reducing cost, and soon all content aligns on the format, and the majority of home TV sets will be shaped to fit the majority content it can receive.

arghwhat··on What is HDR, anyway?
Indeed - I also mentioned that in the paragraph immediately following.
arghwhat··on What is HDR, anyway?
> Things like lens flares, motion blur, film grain, and shallow depth of field are mimicking cameras and not what being there is like

Ignoring film grain, our vision has all these effects all the same.

Look in front of you and only a single plane will be in focus (and only your fovea produces any sort of legibility). Look towards a bright light and you might get flaring from just your eyes. Stare out the side of a car or train when driving at speed and you'll see motion blur, interrupted only by brief clarity if you intentionally try to follow the motion with your eyes.

Without depth of field simulation, the whole scene is just a flat plane with completely unrealistic clarity, and because it's comparatively small, too much of it is smack center on your fovea. The problem is that these are simulations that do not track your eyes, and make the (mostly valid!) assumption that you're looking, nearby or in front of whatever you're controlling.

Maybe motion blur becomes unneccessary given a high enough resolution and refresh rate, but depth of field either requires actual depth or foveal tracking (which only works for one person). Tasteful application of current techniques is probably better.

> High FPS television can feel cheap while 24fps can feel premium and "filmic."

Ugh. I will never understand the obsession this effect. There is no such thing as a "soap opera effect" as people liek to call it, only a slideshow effect.

The history behind this is purely a series of cost-cutting measures entirely unrelated to the user experience or artistic qualities. 24 fps came to be because audio was slapped onto the film, and was the slowest speed where the audio track was acceptable intelligible, saving costly film paper - the sole priority of the time. Before that, we used to record content at variable frame rates but play it back at 30-40 fps.

We're clinging on to a cost-cutting measure that was a significant compromise from the time of hand cranked film recording.

</fist-shaking rant>

arghwhat··on What is HDR, anyway?
Motion resolution? Do you mean the pixel response time?

CRTs technically have quite a few artifacts in this area, but as content displayed CRTs tend to be built for CRTs this is less of an issue, and in many case even required. The input is expecting specific distortions and effects from scanlines and phosphor, which a "perfect" display wouldn't exhibit...

The aggressive OLED ABL is simply a thermal issue. It can be mitigated with thermal design in smaller devices, and anything that increases efficiency (be it micro lens arrays, stacked "tandem" panels, quantum dots, alternative emitter technology) will lower the thermal load and increase the max full panel brightness.

(LCD with zone dimming would also be able to pull this trick to get even brighter zones, but because the base brightness is high enough it doesn't bother.)

arghwhat··on What is HDR, anyway?
Absolute is also a funny size. From the perspective of human visual perception, an absolute brightness only matters if the entire viewing environment is also controlled to the same absolute values. Visual perception is highly contextual, and we are not only seeing the screen.

It's not fun being unable to watch dark scenes during the day or evening in a living room, nor is vaporizing your retinas if the ambient environment went dark in the meantime. People want good viewing experience in the available environment that is logically similar to what the content intended, but that is not always the same as reproducing the exact same photons as the directors's mastering monitor sent towards their their eyeballs at the time of production.

arghwhat··on What is HDR, anyway?
Arguably, even considering HDR a distinct thing is itself weird an inaccurate.

All mediums have a range, and they've never all matched. Sometimes we've tried to calibrate things to match, but anyone watching SDR content for the past many years probably didn't do so on a color-calibrated and brightness calibrated screen - that wouldn't allow you to have a brightness slider.

HDR on monitors is about communicating content brightness and monitor capabilities, but then you have the question of whether to clip the highlights or just map the range when the content is mastered for 4000 nits but your monitor manages 1000-1500 and only in a small window.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
They are not just looking for vulnerabilities, they're demonstrating impact which is kernel dependent.

The kernel has numerous CPU bug mitigations that change kernel behavior to make the CPU bug ineffective for active exploitation (microcode rarely fixes bugs other than just disabling a whole subsystem - they usually take silicon iterations to fix, and the kernel has to pick up the slack), and current kernel design choices may also unintentionally render the vulnerability ineffective.

That's why they specifically say what OS and version they're running, exactly because it is crucial. It's just that they are not, in fact, up to date when it comes to the kernel.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
They are running their LTS distro's LTS kernel, but that us not an upstream thing

On an LTS, you'll be running a Canonical kernel, or a Red Hat kernel, or a SuSE kernel, or an Oracle kernel, or...

Each will have different backports, different hardware enablement, different random patches of choice, and so different bugs and problems.

Unless were evaluating the security of a particular distro release, mainline is what is Linux and will ultimately be the shared base for future releases.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
CPU vulnerabilities are first fixed through kernel mitigations, only sometimes through microcode.

But security research should be done against the current state. Something as simple as a performance optimization can end up affecting the exploitability, and while that doesn't change whether the CPU is vulnerable it does change the conclusion.

Evaluering if a particular old, forked codebase is security-wise is identical is a fools errand, and then that doesn't answer whether an equivalent Red Hat kernel is vulnerable as that's a different fork with different backports and local patches. Mainline is the shared base.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
Mitigations are generally kernel workarounds, not microcode updates. Microcode updates provide some fixes or disable features, but all kernel efforts and why they specify the software at all is because of kernel mitigations.
arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
The problem is that it's downstream backports and hardware enablement - you're running an old forked artisinal kernel maintained by Canonical, you will only get bugfixes if known to be severe enough to be flagged, and all this patching deviates it from mainline and can itself introduce new security vulnerabilities not present in mainline.

This differs from an actual later release which is closer to mainline and includes all newer fixes, including ones that are important but weren't flagged, and with less risk of having new downstream bugs.

If you're going to fight pedantism by being pedantic, better be the right kind of pedantic. ;)

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
These updates mean that you are no longer running a mainline kernel, but an Ubuntu fork with whatever backports and hardware enablement (and new bugs!) this might introduce. This is also true for other software.

LTS does not mean you get all updates, it only means you get to drag your feet for longer with random bugfixes. Only the latest release has updates.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
I am saying that any version of Ubuntu is not representative of the mainline kernel, which is what is relevant when it comes to analyzing current mitigations.

Distro LTS releases often mean custom kernels, backports, hardware enablement, whatnot, which makes it effectively a fork.

Unless were interested in discovering kernel variation discrepancies, its more interesting to analyze mainline.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
My point is that it is not representative of the current state of the kernel.

The kernel has nothing to do with Ubuntu, its release schedule and LTS's. Distro LTS releases also often mean custom kernels, backports, hardware enablement, whatnot, which makes it a fork, so unless were analyzing Ubuntu security rather than Linux security, mainline should be used.

arghwhat··on Branch Privilege Injection: Exploiting branch predictor race conditions
> On an up to date Ubuntu 24.04

So not very up to date, but I suppose mitigations haven't changed significantly upstream since then.

arghwhat··on I ruined my vacation by reverse engineering WSC
> Third party endpoint protection exists.

much to everyone's dismay. :/

arghwhat··on In praise of grobi for auto-configuring X11 monitors
So the solution is to complain and get a replacement unit it seems.
arghwhat··on In praise of grobi for auto-configuring X11 monitors
> Does grobi work on Wayland?

See kanshi, which has a similar rule matching approach.

arghwhat··on A Formal Analysis of Apple's iMessage PQ3 Protocol [pdf]
That you don't want anyone to see any data doesn't make people you give your data spies. Your doctor knows a lot of personal details about you (i.e., has your data), but that doesn't make them a spy - they'd probably prefer not knowing, but they couldn't do their for-profit job otherwise.

If you fail to understand that holding or processing user data as part of providing a service is different from making a business out of selling and/or analyzing said user data, then there isn't much to discuss.

Does a small ad business use personal data? Sure, but there sure are differences in how and the extend. How blind you must be to not see that.

arghwhat··on Radxa Orion O6 brings Arm to the midrange PC (with caveats)
From the perspective of drivers Radxa is not the hardware manufacturer. They combine off the shelf hardware according to its documentation to create a product.

Sometimes the original suppliers will have drivers, sometimes they just ship documentation and let it be up to the customers to write it, sometimes someone else contributed upstream support. When you get "drivers" from e.g. Lenovo, they didn't write them - they're just sending what they got along.

Nothing would work if there weren't drivers in general, the issue is that hardware can be configured in multiple ways and it's not all going to have have proper support or be well tested. In Linux land, this stuff sorts itself out as people get their hands on the hardware, pretty similar to how e.g. laptop support comes to be.

arghwhat··on Era of U.S. dollar may be winding down
[flagged]
arghwhat··on A Formal Analysis of Apple's iMessage PQ3 Protocol [pdf]
There's a big difference between "expanding miniscule business unit" and company whose entire identity is that, so much so they're willing to pay the first company several time the revenue of their ad business every year just to decide a default setting that might boost their ad business.

And once more, you're conflating access to information and spying.

arghwhat··on Amazon's Vulcan Robots Now Stow Items Faster Than Humans
I think the horses were pretty okay with not being bred into slavery.

But there's a very, very big difference between "automate dumb task with unimpressive efficiency that beats humans because humans have to pee, eat and sleep", and AI supplanting humans in society.

Robots isn't an important step in that path tbh. Intelligence is, and we still aren't close, even when throwing entire hyperscale datacenters at the problem...

arghwhat··on A Formal Analysis of Apple's iMessage PQ3 Protocol [pdf]
None of your points is about whether or not the company spies or not. You also conflate the malice of the country they are in with the malice of the company itself.

Google's primary business is and have always been ads, and they practically invented the kind of global tracking we have all come to know and hate. Google actively tries to expand tracking and ad exposure to their own benefit. See the Google TV Streamer home screen as an example of their ad behaviors.

Apple has a miniscule ad business, and from the estimates I can find, the money in that is just a fraction of the Google search sponsorship they get (which counts towards the revenue of the same "services" bracket as their own ads). Apple actively tries to limit tracking, pissing other ad companies like Meta off. See the Apple TV home screen as an example of their ad behaviors.

In general, having access to data and using it are entirely orthogonal, and many companies that have your data consider it a liability they would much rather be without - it's just sometimes hard to provide a service without data passing through, and not everything can reasonably be E2E (either for technical or UX reasons).

arghwhat··on Amazon's Vulcan Robots Now Stow Items Faster Than Humans
The point wasn't really that workers should be the primary clientele, just that the average worker should be able to afford it, and if that wasn't the case the price of the goods should be lowered, or a trend started for higher worker compensation.

Robotic workers lower operational costs and can make goods more accessible, and it's common for various manual labour jobs to be lost when industries change - the labour shifts elsewhere, and generally higher.

(If this wasn't true, unemployment would have constantly grown worldwide since the first automaton replaced a human job or government outlawed certain manual industries, which isn't the case. Workforces do and must adapt to needs and trends.)

arghwhat··on A Formal Analysis of Apple's iMessage PQ3 Protocol [pdf]
While I'm not on the Apple bandwagon, there is a difference between insecure by default and active spying. Even as a Pixel user, I'm fairly confident that my data would be (ab)used less on the Apple side.

Users want convenience, and security always brings inconveniences (e.g., inter-client sync, no chat data before a client logged in first time, etc.).

Some vendors might provide convenience because they want to have your data. Others might provide you the convenience because you as a user want it, but see the resulting data as nothing but a liability.

Some providers are known to have the majority of their business be based around such data, whereas others might have little to no presence in that field.

← PreviousPage 12 of 34Next →