Live data from Hacker News

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

blogs.msdn.microsoft.com

71–80 of 152 posts

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

#72

Earlier quoted context omitted.

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.

Where is the empirical evidence of a mother's love? Have you sent a PR for the joy of playing with a puppy in sunshine?

> Where is the empirical evidence of a mother's love?

Everywhere? When they care for you when you're sick, drive you to sports practice, clean up after you and what not?

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

#73

>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.

If you're running a pirated OS, are you really going to go to court over a missing disclaimer in the pirated EULA?!

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

#74

I don't understand the logic here. 1. Download a preview build because you want "the latest and greatest". 2. Build is full of horrible bugs. 3. Microsoft needs to employ psychological tricks to get you to download the next preview build, as you cling to the previous one with both hands.

There might be more reasons, but here is the author's answer to a similar question:

The imperative is that these machines can screw up the network they are connected to, so they’re affecting other machines. Generally, people don’t look kindly when a Windows system starts screwing up a network.

https://blogs.msdn.microsoft.com/oldnewthing/20160906-00/?p=...

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

#75
post #69

Heh, sounds much better than my previous employer's way of occasionally sending company-wide emails along the line of "The employee who was responsible for the XXX leak was found and terminated. We remind you that leaks damage our culture and make it difficult to share ideas inside the company." For some reason such emails made me feel like I was inside a tech cult. Guess my culture fit wasn't good enough... Well, to…

I never received an email like that when I worked at Microsoft. Granted, maybe they would send emails like that within a specific department, and my department was probably less prone to leaks.

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

#76
post #73

Earlier quoted context omitted.

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.

If you're running a pirated OS, are you really going to go to court over a missing disclaimer in the pirated EULA?!

Burglars have been known to go to court over getting injured in the commission of a crime, suing the property owner.

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

#78
post #24

Earlier quoted context omitted.

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.

Ok, so they see it in some screenshot. "Hey if you get this, your desktop will look different" and that somehow motivates them. :)

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

#79
post #69

Heh, sounds much better than my previous employer's way of occasionally sending company-wide emails along the line of "The employee who was responsible for the XXX leak was found and terminated. We remind you that leaks damage our culture and make it difficult to share ideas inside the company." For some reason such emails made me feel like I was inside a tech cult. Guess my culture fit wasn't good enough... Well, to…

Google right? I used to work there too. I thought Google was especially open internally, which really allowed me to thrive.

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

#80
post #29

Earlier quoted context omitted.

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)

"help track down leaked builds of Windows"

If you're talking about public leaks (rather than just private leaks to a few individuals), surely they're not that hard to find?

I wonder if you mean the leakers?

(for the record, I'm a moderator of a forum which discusses said "leaked builds of Windows"; and I help try to find and preserve those that leaked long enough ago such that they have almost disappeared)

Post reply on HN