(Rant warning.)<p>Apple products have always been buggy. If you do anything slightly unusual, you quickly find that everything breaks. It&#x27;s as if they don&#x27;t actually systematically test anything and instead only fix the bugs that the developers themselves happen to notice in day-to-day use.<p>Here&#x27;s me ranting about it in 2011: <a href="https:&#x2F;&#x2F;jx4slc83qru3hgkkkt1v.oasis.sandstorm.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;jx4slc83qru3hgkkkt1v.oasis.sandstorm.io&#x2F;</a><p>Here&#x27;s me ranting about it in 2014: <a href="https:&#x2F;&#x2F;plus.google.com&#x2F;+KentonVarda&#x2F;posts&#x2F;FEUGQ7mxkUL" rel="nofollow">https:&#x2F;&#x2F;plus.google.com&#x2F;+KentonVarda&#x2F;posts&#x2F;FEUGQ7mxkUL</a><p>And here&#x27;s me ranting about it in 2016: My wife&#x27;s Macbook has a fun feature. It scans the network looking for audio receivers. When it finds one, it hijacks the receiver, switching it away from its current input and over to the Macbook&#x27;s audio. This happens for example while watching movies, while the Macbook is in the other room with no one touching it, even though it has never been intentionally asked to use the TV room receiver for any purpose (though there is <i>another</i> receiver in another room that she uses regularly). As Denon receivers have no apparent access control, there is no way to stop this except to set up some sort of firewall between the Macbook and the receiver. (I do in fact use the receiver&#x27;s network protocol, so disconnecting it is not a good option.)