m0dest

The quality perception of this user segment is relative, too. That visitor who is using a version of Chrome that is 4 years stale? Their experience on the rest of the web was not pixel-perfect today. Many sites are inexplicably buggy for them. They might even be used to having to switch devices to complete some tasks.

Continuing to surf the web with a long-unpatched browser is also overtly negligent [1]. That negligent 2% of users is not a protected class. As such, you might observe that this 2% of users contributes only 0.2% of revenue / engagement / value and make a self-interested decision to stop supporting them.

[1] Except brief windows of time when old Apple devices continue to get Safari security updates without getting feature updates. Not relevant to the author's CSS nesting example.

The build server going down means that no one's app can be updated, even for critical security updates.

For something that important, they should aspire to 99.999% ("five nines of") reliability. With a single physical server, achieving five nines over a long period of time usually means that you were both lucky (no hardware failures other than redundant storage) and probably irresponsible (applied kernel updates infrequently - even if only on the hypervisor level).

Now... 2 servers in 2 different basements? That could achieve five nines ;)

  $ dig +short txt _psl.website.one @1.1.1.1
  "https://github.com/publicsuffix/list/pull/2625"

(It's "passthrough" and not "uncompressed" because DisplayPort may use DSC depending on the resolution and frame rate.)

US$500 for an optical cable can be a lot cheaper than paying for HDMI extender sender and receiver boxes.

The major apps typically exploit selection bias to solicit 5-star reviews. They will wait until the user meets some criteria for "having a good experience" and show an app review prompt at that moment.

Then, having amassed thousands of 5-star reviews, they will turn up the threshold so that only a trickle of the most likely 5-star reviews keep on trickling in to negate any negative organic reviews.

There's a related practice of "pre-prompting" where the app first asks the user whether they are satisfied and only solicits a real app review from those who pass the screening question.

It's all quite shady and makes it hard to trust app reviews. But until the app stores solve this, app developers need to play the game.

So, with this, you can have high-quality static text in one region of the frame while there is lossy motion encoding (e.g. for an animating UI element) in another region of the frame.

[0]: https://support.apple.com/guide/mac-help/screen-sharing-type...

The Ride Request API [1] seems closed off to developers now, too.

[1] https://developer.uber.com/docs/riders/introduction

In a perfect world, the digitization of these IDs would come with modern digital privacy and security. Scanning your ID number would only provide a recipient-specific ID that couldn't be matched with other vendors. Age eligibility and driver's licensing status would be presented as separate signed attestations that share no other data.

We aren't even heading in that direction yet.

If you decide to switch from an iPhone to an Android phone, you're looking at an arduous process of enrolling a new passkey for every single site.

Android 14 added 5G slicing upsell for consumer apps: https://source.android.com/docs/core/connect/5g-slicing#5g-s...

This is imminent.

- maximum transmission unit (MTU)

- TCP maximum segment size (MSS)

- different DNS responses leading to different edge servers

- TCP reordering, which may now occur on the tunnel layer

- lost packet retransmission, which may now occur on the tunnel layer

- time to live (TTL) hop count on the packet

- IPv4 may be used for some connections that were previously using IPv6, as some VPN services are IPv4-only

- different peering between the VPN server and the edge server

ISP traffic categorization is only one variable.

QuickType Keyboard: Multilingual Typing

English, Chinese, French, German, Italian, Japanese, Spanish, Portuguese, Dutch, and Hindi

The result is bad either way. It's either A or B. (A) Canceling iCloud+ doesn't remove existing Hide My Email addresses - which makes it possible to abuse by creating tons of extra addresses before canceling. Or: (B) Canceling iCloud+ deletes all of your Hide My Email addresses, locking you out of dozens of services (e.g. anything that sends an email as a MFA).

I suspect that it is actually (A). Someone just needs to test this and report out.

Users value attention more than time. I'd bet that 4 yes/no radio buttons require a lot less attention than trying to parse the example question from the article ("Will you be travelling to any of the following countries with any of these trailers? Select all countries that apply.")

[1] https://opensource.apple.com/

https://www.facebook.com/adpreferences/ad_settings

I'm on over 300 lists. Removing myself from each one took 6 clicks. I tried to automate it with Selenium, but their bot detector caught it and banned my device from opting out of any lists (!)