Sindre Sorhus
Sindre Sorhus
If this is still relevant, would you be able to fix the merge conflict?
Apple reply: --- If NSURL can represent it, then it’s a valid URL. It's up to the UI client what to do with the URL. Using http:// is not always...
My reply: --- It’s an invalid URL because it’s parsed into something the user did not intend. When you construct a URL/NSURL instance from ““x.com”, the “x.com” becomes the “path”...
Apply reply: --- Thanks for your input.
That sample code has no usage of `AVPlayerView`.
This is even worse on macOS 26.1. Now it shows the app icon of my app for external drives.
I believe the issue is in the `cacheable-request` dependency, not Got's code. When a 304 Not Modified response has completely empty headers, `cacheable-request` fails to preserve the original `Content-Encoding` header...
It didn't support links until recently, so I don't think this makes sense until we can target the Node.js version that supports that. Node.js 22, I think.
Apple reply: --- Thank you for filing this feedback report. We reviewed your report and determined the behavior you experienced is currently functioning as intended. The HI design for iOS...
My reply: --- Thank you for the clarification. However, I still believe the current approach is flawed — not in intent, but in execution. This isn't about weakening privacy, but...