Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to get people who installed a leaked build to stop using that build?

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

41–50 of 152 posts

Re: How to get people who installed a leaked build to stop using that build?

#41

Post by sirn »

mikestew wrote: post #36
gwbas1c wrote: post #6

Include a remotely-activated kill switch; and kill with plenty of warning. What do I mean? I no longer use iPhone because I installed a beta iOS. When the official build came out, I kept "checking for updates" but I never got an update. One day, Apple remotely killed my phone. Manually updating to the production iOS would be fine; but remotely disabling my phone without warning was not acceptable. This is why I refus…

I no longer use iPhone because I installed a beta iOS. ...and didn't know what I was doing, nor did I read the well-documented warnings that are printed in multiple places. Then when things went down exactly as Apple warned me, multiple times, I went on the Internet to complain about it. What warnings? Apple tells you up front that you can't upgrade to release from beta, you'll need to load it via iTunes or Xcode. Ap…

>How this currently works with public betas, I know not.

Not sure about iOS, but for OS X public beta user are on the beta update channel even after release. If user happen to apply for OS X 10.11 Public Beta, then user will continue to receive beta for 10.11.1, 10.11.2, and so on, but not 10.12 Public Beta. To go back to release channel, user will need to switch off the beta update channel in System Preferences.

iOS Public Beta, on the other hand, seems to go directly from beta to release, per FAQ (Developer Beta seems to be different story, though):

> To get a shipping release of iOS on your iPhone, iPad, or iPod touch, you can simply install the final version of the software you are testing when it appears in Software Update.

https://beta.apple.com/sp/betaprogram/faq

Re: How to get people who installed a leaked build to stop using that build?

#42

Post by [deleted] »

tekklloneer wrote: post #10
failedPatch_002 wrote: post #4

Change the wallpaper. Oh, I thought it was going to be: Prevent users from disabling automatic updates, and require persistent internet connections, and then deploy updates every 7 days, so that users lose 10 or maybe 20 hours a week, waiting for failed patches to retry, and display ominous warning messages like "DO NOT POWER DOWN OR UNPLUG YOUR COMPUTER WHILE WE CONSTANTLY WASTE YOUR TIME WITH BULLSHIT." But I was p…

As much as I'm not a fan of the forced automatic update (even on pro), I think your post is extremely mis-representative on multiple levels.

[deleted]

Re: How to get people who installed a leaked build to stop using that build?

#44

Post by gol706 »

cududa wrote: post #33
gol706 wrote: post #28

Earlier quoted context omitted.

Once an iOS build expires, you can't take a backup, so you can do that to get the phone working again, but you lose any un-backed up data on the device like photos and app data. In the days before iCloud it was a huge pain.

Why didn't you just upgrade to the production build when it was released?

Can't speak for the OP, but in my case, I had it happen twice between beta 1 and beta 3 when I tried to skip beta 2 because I didn't care that much. It was also an iPad that left upstairs and was too lazy to carry it downstairs to update. Not a primary device, so all I lost was some progress in a few games, but I can see how someone could have suffered the same fate with their main phone and have lost a lot more.

Re: How to get people who installed a leaked build to stop using that build?

#45

Post by monochromatic »

tedunangst wrote: post #40
monochromatic wrote: post #27

Earlier quoted context omitted.

What would the Mac-person or Linux-person solution look like?

The linux solution would provide a new mechanism to configure sound.

... which wouldn't work properly until version 3.5 or so.

Re: How to get people who installed a leaked build to stop using that build?

#46

Post by DougWebb »

Mithaldu wrote: post #23
tekklloneer wrote: post #10

Earlier quoted context omitted.

As much as I'm not a fan of the forced automatic update (even on pro), I think your post is extremely mis-representative on multiple levels.

With the group policy editor you can disable the automatic updates on pro and up. The UI won't change, but the setting will take effect.

If I could buy the Pro version as an individual, and run it on an isolated machine, as I've done with every prior version of Windows I've purchased, I probably would have upgraded by now.

Since they don't offer that, and the non-pro version treats ALL users as imbeciles who cannot manage to keep their machines secure and up to date, and who are unable to decide for themselves if the benefits of participating in usage metrics gathering, voice-operation, and integrated web and local search outweigh the risks and costs, I'll be sticking with Win7.

Re: How to get people who installed a leaked build to stop using that build?

#47

Post by andrewbarba »

zoffix222 wrote: post #38

The article mentions none of the evidence this strategy actually worked at all. Is it all just conjecture or are there more articles/evidence supporting this technique?

Oh c'mon not everything on this site has to be riddled with statistics, trials, and evidence of something working. The article gave me a chuckle, and plays on our instinct to gravitate to shiny new things. I think all we need to take from this is not every technical problem needs a technical solution. Understanding your audience, in any product, is crucial; use it to your advantage however you can.

Re: How to get people who installed a leaked build to stop using that build?

#48

Post by AdmiralAsshat »

Seems like you could've achieved the end-goal by just warning of the danger and coming across like their safety is your primary concern rather than finding the leaks, i.e.:

"Build 97241 contains a potentially fatal bug that could wipe your computer. If you are using Build 97241, please upgrade it to a more recent build or otherwise cease using this build immediately. We do not care how you acquired this build. We simply do not want you bricking your computer."

Re: How to get people who installed a leaked build to stop using that build?

#49

Post by civilian »

Frank2312 wrote: post #26
loeg wrote: post #19

Earlier quoted context omitted.

If the PC reboots with your work unsaved, you could lose a day's work, for example.

Hit that Ctrl-S now. And in 5 minutes. And 5 minutes after that. Repeat until you stop working today. Hit Ctrl-S every start of the day after 5 minutes of work. And 5 minutes after that. Repeat until you stop working that day. There you go. Saved you a lot of hours of work.

We're power users. We've already been burned by this, and we know how to defend against it.

That doesn't help my mom when she's writing a long letter and (rightly) expects her computer's RAM to hold the information and warn her before it does anything destructive. That doesn't help the middle-schooler who is suffering through their first 5-page essay.

Re: How to get people who installed a leaked build to stop using that build?

#50

Post by Mithaldu »

DougWebb wrote: post #46
Mithaldu wrote: post #23

Earlier quoted context omitted.

With the group policy editor you can disable the automatic updates on pro and up. The UI won't change, but the setting will take effect.

If I could buy the Pro version as an individual, and run it on an isolated machine, as I've done with every prior version of Windows I've purchased, I probably would have upgraded by now. Since they don't offer that, and the non-pro version treats ALL users as imbeciles who cannot manage to keep their machines secure and up to date, and who are unable to decide for themselves if the benefits of participating in usage…

Are you thinking of the Enterprise version?

Pro is available just fine: https://www.amazon.com/dp/B00ZSHDJ4O/

And my Win 10 is Pro since i upgrade it from Win 7 Pro.

Post reply on HN