I feel like there was a Black Mirror episode that covered nearly exactly this. Or there's several other series like Amazon's "The Feed" that quickly shows why this sounds nice.. but in practice is probably a Very. Bad. Idea. without limitations.

Holy crap, mobile input is NOT parsed well. Sorry for that eyesore comment.

I suspect you and I used to work together on some middleware servers, and itâ(TM)s probably a good reason that we share near identical opinions and likelihood of jury selection on this! Iâ(TM)m no longer in Cole though.. Iâ(TM)m pretty confident the Governor doesnâ(TM)t understand this issue on his own, so Iâ(TM)m really curious who advised him on this. And thankful I wonâ(TM)t ever have to deal with them!!

If you still might have to deal with them, my condolences!!!

Background play was a FREE feature of Youtube. On the ORIGINAL iPhone.

Now, it's expected you should pay for something that used to be free. (mostly so they can ensure to advertisers that they have captive attention)

Because Netflix will still work.. but Airplay wonâ(TM)t. People will blame Apple for that, public pressure will grow for Apple to cave. I just donâ(TM)t think that many people use AirPlay for this to work as well as Netflix wants with Bluetooth speakers, smart TVs, consoles etc in mix.

Netflix is glad to support airplay as long as they know their DRM/licenses will be properly enforced. They donâ(TM)t care about third parties so much as they canâ(TM)t guarantee that third parties will prevent piracy the way they want it done. Thatâ(TM)s a part of what this pissing match is about. That, and money of course.

Hot grits.

Had I mod points and the roof wasn't 5, this would be +1. There's some things you don't touch on.. but you really nail an elephant in the room!

IANA.. anything relevant here. I work in construction management (many years prior in IT, security, etc, hence me being here), and often at my desk on the jobsite the grinding, hammering, cutting, you name it gives piercing noise that makes it f'ing near impossible to concentrate. So I've been eager to use noise cancelling.. however there are issues.

The obvious one, pointed out, is possible cancellation of noise you really need to hear instead of ignore, like something collapsing, someone calling you, etc. (especially when walking the site instead of at the desk) In a construction environment, it'd be very hard to programmatically distinguish the good loud noise versus bad loud noise- scaffolding may be collapsing, or it may just be a steel worker cutting an extra toe angle off of a joist that was manufactured incorrectly and that falling to floor. It's probably kind of like if an active shooter scenario happened at a gun range- which gun shot is bad? You can perhaps tell by direction sound was aimed in that case, but standard folks listening will mostly just hear shots until they notice something amiss. (I pray I never experience that.) I suspect the best answer in industrial application would be "partial cancellation," a bit more noise let through than Bose currently lets through, kill plainly regular noises like compressors but let irregular noises like crashes or hammering through.

However, my sister is an audiologist and pointed out something else- there really hasn't been a study of noise cancellation in loud environments, and it's benefit to ear health. While the cancellation is creating opposing waves and all, there's no study on the actual sound pressure that gets to the ear drum and possible effects of that, even if it is in an inaudible range. I can say when sitting at my desk and I turn on cancellation with my Bose QC20i's, it does WONDERS for noises like compressors and such- but I can tell there's a pressure in my ear from the cancellation. So there's still a valid health concern to be investigated before they'd be OSHA approved for use- I'd rather not lose my hearing thinking the cancellation was a good noise reducer when it had negligible health effects. As such, right now OSHA doesn't really approve noise cancellation in any construction environment, just standard NRR rated blocking materials.

I actually wonder why it's so hard for any company to say "Here's what we collect, here's why we use it. Here's an option to submit automatically, review before submit, or not send at all. And oh yeah, here's an option to remove data from reports or to decline to ever send a selected field."

I can say this- if a company were transparent and provided a means to verify what they were doing (IE not secretly sending a few extra undocumented pieces), I might be more inclined to send data based on that honesty than I should be. There might still be stuff I take out, but if I know what's being sent instead of just "Hey there's a crapton of data on my line, I've no clue what it is, where it's going, or why!!"

Barely related side note- crap like this actually makes me miss dialup. With broadband, sending these little reports back isn't too noticeable if you're just on a workstation on a dsl line at home, and while you might have firewall or other setup, most folks including IT nerds "set it and forget it.". People really don't tend to care if there's no user experience impact.

Back in Win XP days a friend of mine, who *damn well* shoulda known better, linked a pretty cool Matrix screen saver in group chat about the time the movie was gaining steam in media. Everyone knowing he's competent admin, always does due diligence etc, checks it out. At the time I was at bumfuck Missouri visiting family where dialup was the only option (even until less than 5 years ago.) Well, after installing the screensaver, I noticed that the modem activity indicator was going in the systray for 10-20sec periods. I only had IRC loaded, no web browser, nothing else that would be hitting the network, and knew what to expect traffic wise of standard OS functions. (I HEREBY ACCEPT MY PUNISHMENT OF ETERNAL JUDGEMENT, UNPAID MALWARE REMOVAL, AND FINGERPOINT AND LAUGHING- You guessed it, this screensaver had a new nasty riding its coattails. Yes, I should have checked myself etc etc, trust me I knew instantly my errors, and have used that lesson well in life since. The screensaver actually wasn't sending much data at all, apparently a C&C check that had no new instructions at that time.. but enough data that I noticed- only because of dialup. The group chat of admins did some reverse engineering on it, reported to McAfee and Norton (back when, relatively to today, they didn't suck, and were the big AV players, we hit several minor ones as well)- both companies worked with us, updated defs within 6hr, gave us credit for the find. Seriously though- dialup was the hero here, it would have likely gone undetected for a while if not for seeing small data being forced to take a long time to transmit.

Kinda sucked, because for the time, it really was a dang decent screensaver with 3d effects that by today's standards wouldn't be awesome but not aged/antiquated.

FWIW- I worked with a small business server (I didn't choose the OS, I inherited.) around 2008. It got deactivated due to hardware change (HD failure, we upgraded RAM while at it before reinstalling new drive and restoring backup). SBS wouldn't activate. I called MS per phone number listed clearly on screen, they asked a few basic pieces of info to ascertain the original license and I assume find the reason for decline in their records. I told them the situation and basic, not precise, details of HW changes that occurred, they provided an activation over the code, no purchase necessary. Total time was 10 minutes on phone. They really weren't unreasonable at all about it, pretty solid customer experience with individual on phone not treating me like idiot or pirate or etc. I'm no fan of them, but I do give them props for how smoothly that process went.

If it's substantially the same hardware, even if their system flagged it, they're actually not out to gouge on this side of things. (I make no claims about gouging in any other part of the process here.) If someone were reactivating constantly due to reinstall/hardware/etc, they would have needed to call MS at some point I'm pretty sure, and would have explained what's going on. I'm sure that MS keeps records of that, and looked for such before pursuing in court.

I'm sitting here thinking it wouldn't be hard to wire the clock to stop on whistle. Put a sensor in ball, ref pushes button after he hands ball to inbounding player, it detects acceleration of throw in then starts clock on next (capacitive?) touch. (Ok probably it only transmits acceleration/touch and score table receiver does logic on that). As always human standby, if they hit start after transmitter starts clock or stop after whistle stops ignore it, but if they start/stop when a sensor missed it it accepts the human command and resumes logic. The programming seems easy here, the tech of not imbalancing the ball, durable for impact etc probably not that far off... As a bonus this system might help remove much of human skew on timing, but doesn't help refs slow to whistle etc.

On the surface this isn't news for nerds.. But really with a bit of imagination it could be!

Get a hunting trail camera. Takes pics on an SD card. Not networked, but is designed to be outside and it should get you the information you seek relatively cheaply.

You must be new here...