• 0 Posts
  • 71 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle


  • Don’t use JSON for the response unless you include the response header to specify it’s application/json. You’re better off with regular plaintext unless the request header Accept asked for JSON and you respond with the right header.

    That also means you can send a response based on what the request asked for.

    403 Forbidden (not Unauthorized) is usually enough most of the time. Most of those errors are not meant for consumption by an application because it’s rare for 4xx codes to have a contract. They tend to go to a log and output for human readers later, so I’d lean on text as default.



  • Officials said that at the police station, Love admitted to being involved in the attack and said he had become acquainted with the victim beforehand.

    “The defendant added he was possibly drugged and someone inserted an unknown object in his rectum,” the report says. “Although the defendant is not certain the victim is responsible for this, the defendant made a statement indicating he needed to hurt whoever hurt him and was prompted to purchase the knife at a Target store near Miami International Airport.”







  • NU7400 has a peak of 337 nits and that’s with the poorer contrast ratio of LCD. My LG C1 is 780 nits. I still find it a bit weak with the lights on so I can’t imagine 330 on LCD.

    Yeah, HDR is meant to be watched in a 5-nit environment, but sometimes that’s just not reasonable. While my LG is technically better, bright TV shows like Rings of Power are more enjoyable with the 1500 nits my TCL can output. Once that ABL (Automatic Brightness Limiter) kicks in for the OLED, you absolutely need the blackout curtains.


  • I have both:

    • an 85" TCL R655 with a bunch of dimming zones that works great in my sunlight-heavy living room for both daytime viewing and family movie night.

    • a 55" LG C1 in my gaming/home-office/theater room with blackout curtains that is great for PC gaming and awesome theater experience.

    I would say it depends on your viewing environment. The inability of an OLED to get bright can ruin the experience. But my game room has blackout curtains and it’s enclosed.

    I just recently moved from 34" Ultrawide to just mounting the 55" onto my desk. It’s oversized for my viewing distance, but 4K resolution is 8million pixels so I rarely run apps in or near fullscreen anymore. I think a 42" LG OLED is perfect for PC. (Great out of the box calibration and 120hz G-Sync). Though QD-OLED on Samsung are technically better, I don’t trust them to run compensation cycles.

    If you’re worried about burn-in on PC, just set a screensaver to black your screen in 2 to 5 minutes. That’s why they were invented anyway (CRT era). For regular media consumption it’s a non-issue. Rtings set a static image for 120 hours on a Sony OLED and it basically went away with one compensation cycle.


  • The TL;DR is now pixels get tracked for how long they’ve been lit. Then the device can evenly burn out the other pixels so the usage is uniform. The trade off is you are going to lose max brightness in the name of screen uniformity.

    The other point is a shifting of the TFT layer that people think is burn-in, but it’s actually image retention. But, it is solved by these TV maintenance cycles. Just hope that this compensation cycle actually runs since some panels just fail to run them.

    Checkout this RTings video for a good overview of lots of different TV brands and how they perform.

    PS: Burn-in is actually a misnomer from the CRT era. There’s nothing burning in; the pixels are burning (wearing) out.





  • You’re mostly right, if not completely right. VPN is encrypted with SSL so the ISPs only see that you exchanged information with a VPN, but not what is being exchanged.

    You may consider that maybe the ISPs can also figure out who else connects to the VPN and maybe deduce some information that way, but they can’t know everyone who uses the VPN, only those on their ISP that use it. So you can exchange information with somebody in Antarctica and the ISP has no way of knowing if it’s somebody outside or inside their ISP.

    Also, on the point of services that are not HTTPS, don’t confuse encrypted protocols with the SSL of the VPN. Your ISP will not see your unencrypted packets either if you tunnel it through your VPN. They can’t see your DNS or ping requests (assuming you are using an IP based proxy, not using a SOCKS proxy). But your VPN provider can see those unencrypted requests. So you’re choosing to trust the VPN provider with those opaque requests over your ISP.

    And last, about DNS-over-HTTP, a reverse DNS is enough for your ISP to know what domain you’re connecting to in a lot of the cases, regardless if you hide the domain name resolution. Of course, sites using shared CDNs mitigate this, but not all do.