3 ms·

Once again submitting the bug report to HN gets you much better results than sending it to Apple

by nikanj 3y ago

mschuster91 3y ago
PR and legal teams and forums frequented by employees are the only way to short-circuit the corporate feedback layers.
- miki123211 3y ago
  Also direct email addresses harvested from GitHub (sometimes) and apparently also investor relations. In some countries, if you're part of a retirement fund that owns stock in a company, you might get away with calling yourself an investor in a letter / email / phone call to investor relations. Nobody wants investors to be disgruntled, so if one asks for something and it's not a terrible imposition (think actually looking at a flagged customer instead of bouncing them from bot to script-following employee) many companies actually go for it and fulfill the request without much checking.
olliej 3y ago
Based on? You understand how betas work right?
- tumult 3y ago
  It was in the release candidate. It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first release candidate. This is covered in the article.
  - crazygringo 3y ago
    But regardless, obivously none of us here have the slightest idea whether it was in the pipeline to be fixed anyways, or if it was because of HN. It might have been HN, but it might not have been. (Surely other things have been fixed between RC and release without HN intervening.)
    - tumult 3y ago
      Release candidate means it could have gone out as a release. RC2 ended up being the release version.
KennyBlanken 3y ago
The real question is how such a major security related bug made it into the second public beta. A company with Apple's resources should have extensive in-house automated and manual testing and validation, and basic firewall rule eval / VPN problems shouldn't be an issue that makes it this far.
- LeoPanthera 3y ago
  > The real question is how such a major security related bug made it into the second public beta. Does it matter? Isn't that the point of betas?
- dvngnt_ 3y ago
  I'm sure they do, but is that specific test case in their suite?
- keyle 3y ago
  Beta still get 5% of the full release foot traffic... I installed the beta 1 of Sonoma months ago (to do work on the widgets) and my mac was fully crashing once or twice a day. You could argue "how did this even make it to beta"... /shrug My iMessage is still broken from the beta, the text gets displayed in a sub-frame 1/2 the size of the window for no reason at all. I can't seem to undo it.
deleted 3y ago
[deleted]
sacnoradhq 3y ago
I don't doubt it. They definitely don't respond to radars or ack concerns even from partner groups in MA_NG. Apple's concept of feedback is like Whitehouse petitions: ostensible appearance of engagement connected to the circular file. At least Netflix just has no feedback mechanism at all.

Once again submitting the bug report to HN gets you much better results than sending it to Apple

by nikanj 3y ago

Once again submitting the bug report to HN gets you much better results than sending it to Apple

mschuster91 3y ago

PR and legal teams and forums frequented by employees are the only way to short-circuit the corporate feedback layers.

miki123211 3y ago
Also direct email addresses harvested from GitHub (sometimes) and apparently also investor relations. In some countries, if you're part of a retirement fund that owns stock in a company, you might get away with calling yourself an investor in a letter / email / phone call to investor relations. Nobody wants investors to be disgruntled, so if one asks for something and it's not a terrible imposition (think actually looking at a flagged customer instead of bouncing them from bot to script-following employee) many companies actually go for it and fulfill the request without much checking.

olliej 3y ago

Based on? You understand how betas work right?

tumult 3y ago
It was in the release candidate. It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first release candidate. This is covered in the article.
- crazygringo 3y ago
  But regardless, obivously none of us here have the slightest idea whether it was in the pipeline to be fixed anyways, or if it was because of HN. It might have been HN, but it might not have been. (Surely other things have been fixed between RC and release without HN intervening.)
  - tumult 3y ago
    Release candidate means it could have gone out as a release. RC2 ended up being the release version.

KennyBlanken 3y ago

The real question is how such a major security related bug made it into the second public beta. A company with Apple's resources should have extensive in-house automated and manual testing and validation, and basic firewall rule eval / VPN problems shouldn't be an issue that makes it this far.

LeoPanthera 3y ago
> The real question is how such a major security related bug made it into the second public beta. Does it matter? Isn't that the point of betas?
dvngnt_ 3y ago
I'm sure they do, but is that specific test case in their suite?
keyle 3y ago
Beta still get 5% of the full release foot traffic... I installed the beta 1 of Sonoma months ago (to do work on the widgets) and my mac was fully crashing once or twice a day. You could argue "how did this even make it to beta"... /shrug My iMessage is still broken from the beta, the text gets displayed in a sub-frame 1/2 the size of the window for no reason at all. I can't seem to undo it.

deleted 3y ago

[deleted]

sacnoradhq 3y ago

I don't doubt it. They definitely don't respond to radars or ack concerns even from partner groups in MA_NG. Apple's concept of feedback is like Whitehouse petitions: ostensible appearance of engagement connected to the circular file. At least Netflix just has no feedback mechanism at all.