Conscientious spectre making a home in the threadiverse.

I also toot as @tojikomori.

  • 18 Posts
  • 45 Comments
Joined 1年前
cake
Cake day: 2023年6月1日

help-circle

  • Apparently not in Windows settings:

    If the BIOS says it supports Modern Standby, Windows takes it at its word and completely disables the ability to enter S3 sleep (classic standby). There’s no official or documented option for disabling Modern Standby through Windows, which is incredibly annoying.

    Side note: for a while, there was actually a registry setting you could change to disable Modern Standby on the Windows side. Unfortunately, Microsoft removed it, and to my knowledge, has never added it back.

    I’m not a Windows user, so I can’t confirm one way or the other, but toward the end of the end of the article the author gives vendor-specific instructions for disabling the S0 Low Power Idle capability from BIOS.













  • Just tried the demo yesterday. The tutorial’s integrated into the gameplay in a way that didn’t feel obstructive to me. It’s less like an old-school sandbox tutorial and more that the game makes it obvious what you have to do for the first mission. And it seems to focus on the new mechanics since the basic stuff is already made obvious by overlays showing the controls.

    There will be people who have no capacity for nuance and see this as a boolean thing, and for them: the tutorial’s not skippable, no. But for most people, it shouldn’t be an issue.



  • It’s surprising that Apple isn’t listed (among those backing the scheme) given that the company designed the HomeKit standard with security and privacy as key objectives.

    I think that’s the conflict: Apple has its own certification programs. From Apple’s perspective, a successful government-backed trademark would compete with Apple trademarks for consumer mindshare and the certification would add new overhead to Apple’s own product launches.

    Other brands backing this program have more to gain than lose from it, e.g. because their own certifications aren’t as well marketed, or because it simplifies product screening, or sets up new hurdles for competitors. Apple’s in a unique position where none of those benefits are relevant. It only sees the costs.




  • Priced at $1,599, the ViewFinity S9 has the same price tag as the Studio Display from Apple, but Apple charges an additional $300 for Nano-texture matte glass and $400 extra for a tilt and height adjustable stand.

    A lot of Apple users feel the Studio Display’s overpriced, so it’s interesting that Samsung isn’t competing on price.

    If I were deciding between the two, and it didn’t come down to unique features like portrait mode, then I’d want to see them side by side in a brightly lit room. The regular (non nano-texture) Studio Display handles most reflections decently well, but if the ViewFinity does much better then I can see that being a plus for an office setting where you have lights or windows behind you. I’m sure the nano-texture does better yet, but it has some trade-offs and cleaning requirements that make me very reluctant to recommend it. (I don’t like that the wording above suggests nano-texture is a regular matte glass. It’s not. It’s better in many ways, but it’s not for everyone.)


  • I use offline maps a lot. The article mentions a major reason: traveling, especially abroad, with limited or no data. It also comes in handy when we drop out of cell service, which happens more often than I’d expect outside of major cities in the US. My favorite app for those use cases is Organic Maps, which lets me download maps by city, state, or country.

    I use offline maps for hiking too, but it’s such a different use case that I find I want an entirely different map type and UI – one that focuses less on roads and directions and instead surfaces tools for route-planning and managing tracks and waypoint markers. Gaia’s long been my favorite app for that.



  • This later article makes it sound like the issue was with websites using UA sniffing:

    For instance, after applying the RSR updates on an iOS device, the new user agent containing an “(a)” string is “Mozilla/5.0 (iPhone; CPU iPhone OS 16_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5.2 (a) Mobile/15E148 Safari/604.1,” which prevents websites from detecting it as a valid version of Safari, thus displaying browser not supported error messages.

    I hope Apple’s use of the Rapid Security Response system here was mostly an infrastructure test. I would be miffed to learn that a patch for some zero day was fumbled because Facebook didn’t get the decades-old memo not to use UA sniffing for feature detection.