HN user

kiririn

552 karma

OwO

Posts0
Comments210
View on HN
No posts found.

It still blows my mind that no OLED TV has yet added simple temporal blending between frames, the kind of which MPV has had for decades. They could even take it a step further and emulate the colour-dependent blending of LCD screens. But no instead it's the same terrible motion interpolation algorithms of 15+ years ago, or nothing.

I solved mine by chronically exposing myself to very low noise during sleep - wearing good earplugs in an already silent room. To the point where you can hear your eyeballs move etc. I guess this may be where the link to good sleep comes from, which implies a quiet sleeping environment

A bug(?) exists to disable liquid ass on the Home Screen that still works in 26.3 - enable Reduce Motion globally in accessibility settings, then add a per app accessibility override for “Home Screen & App Library” with Reduce Motion off, then reboot. Somehow this disables liquid ass throughout the Home Screen, back to iOS 18 gaussian blurs

My solution to this is a pair of udp ports relayed to each other on a VPS via socat. Then you can point a home WireGuard server (behind cgnat etc) at one, and clients at the other, with no need to trust the vps

While I do like tone controls, I'm skeptical of the argument of adjusting bass/treble based on volume, e.g. the likes of 'Dynamic EQ' in D&M receivers. It has always sounded like it is doubling up something that my brain is already doing

Full-text search is entirely client side (not via IMAP)

Setting up server-side Xapian full-text search and disabling the crap client-side one in Thunderbird was one of the best improvements I made to my email usability. What makes your client-side search better? It's usually not speed I'm looking for, but rather precision, such as double quoted phrases (sorely missing from Thunderbird's client-side search), filtering by a mixture of things, etc.

I wish more clients had an option for server-side-only search (looking at you, iOS Mail.app) and/or had a nice UI for it (ctrl+shift+f dialog in Thunderbird is janky but gets results)

IPv6 Is Hard 1 year ago

Turning off the firewall could just as easily be a unnoticed configuration error that causes it to die on startup

IPv6 Is Hard 1 year ago

Parent poster is making the (good and underrated) point that NAT makes this logic failsafe: Turn an IPv6 firewall off and you’ve got all incoming connections allowed. Turn IPv4 NAT off and you’ve got no connectivity at all

The source sentence on cheese.com was: "It is the most popular Dutch cheese in the world, accounting for 50 to 60% of the world's cheese consumption."

The glorified autocomplete failed to detect the nuance in this (admittedly poorly written) sentence that the 50-60% statistic was of the world's Dutch cheese consumption

This is missing a good justification for digging into realtime processing. For me that was to create a DIY receiver, so the equaliser/room correction needs to happen quickly and consistently to maintain lip sync. I'm not sure it's quite so justified for an audio/music server

FreeBSD never crossed my radar as a viable platform for realtime audio processing, instead I had good luck with Linux + RT patch + Pulseaudio + https://github.com/bmc0/dsp. (Pulseaudio really shines in this kind of use case, will resample to correct for slight differences in input/output clocks etc)

Also an aside, "USB cable: WireWorld ULTRAVIOLET 8" is a controversial thing to mention

Please don't force low contrast ratios on users. Not everyone is calibrated to >100 nits and viewing your content in a bright but sensible ambient environment

The recommended grey-on-grey may be unreadably low in contrast when viewed on, for example, 0 brightness in a pitch black room, or in direct sunlight

The full SDR colour range is there to be used, this isn't HDR where you need to limit things to not blind your users