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

21–30 of 152 posts

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

#21

Post by prplhaz4 »

ryukafalz wrote: post #20

>And there are some legal issues that are tied to the date a feature first becomes available to the public. Seeing a feature go public prematurely throws a bunch of scheduling into disarray because you now have to finish those legal documents in less time than you planned. As someone who's never worked for a company that produces commercial software, I'm curious about what he's referring to.

A simple example would be adding a feature that collects user information before you update the EULA to tell people that you're collecting their information.

The EULA will likely need to go through multiple iterations between local and partner lawyers before the language is agreed upon - so expediting is not always an option.

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

#23

Post by Mithaldu »

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.

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.

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

#24

Post by heywire »

kazinator wrote: post #12
radley wrote: post #7

Earlier quoted context omitted.

I think the critical point of their solution is they don't need to negatively affect users to get them to update.

If I'm not negatively affected in any way, why should I upgrade? Also, how does a user who doesn't upgrade notice a change in wallpaper which doesn't take place until after the upgrade? By looking at someone else's desktop which is running the release version? What if the user has changed to a custom wallpaper, and doesn't remember what the original wallpaper of the leaked OS looks like?

>Also, how does a user who doesn't upgrade notice a change in wallpaper which doesn't take place until after the upgrade? By looking at someone else's desktop which is running the release version?

The type of person who is downloading leaked pre-release builds in order to have the latest and greatest generally follows the latest news about new leaked builds.

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

#25

Post by monochromatic »

ryukafalz wrote: post #20

>And there are some legal issues that are tied to the date a feature first becomes available to the public. Seeing a feature go public prematurely throws a bunch of scheduling into disarray because you now have to finish those legal documents in less time than you planned. As someone who's never worked for a company that produces commercial software, I'm curious about what he's referring to.

Might be considered a public disclosure for purposes of patenting the feature.

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

#26

Post by Frank2312 »

loeg wrote: post #19
retox wrote: post #14

Earlier quoted context omitted.

10 hours a week to deal with patches?

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.

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

#28

Post by gol706 »

ihuman wrote: post #15
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…

Couldn't you just put it in restore mode and install the latest version from iTunes, or manually download the IPSW from the internet and install it?

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.

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

#29

Post by cududa »

monochromatic wrote: post #25
ryukafalz wrote: post #20

>And there are some legal issues that are tied to the date a feature first becomes available to the public. Seeing a feature go public prematurely throws a bunch of scheduling into disarray because you now have to finish those legal documents in less time than you planned. As someone who's never worked for a company that produces commercial software, I'm curious about what he's referring to.

Might be considered a public disclosure for purposes of patenting the feature.

This is accurate. A leak still constitutes a public disclosure (I use to help track down leaked builds of Windows)
Post reply on HN