How to get people who installed a leaked build to stop using that build? • Hacker News Board

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

#141

Post by dragonwriter » Wed, Sep 07, 2016, 4:02 PM UTC

derefr wrote: post #124

dragonwriter wrote: post #96

Earlier quoted context omitted.

> So - if an intruder breaks in to your house, you can shoot him without repercussions In many US jurisdictions, not generally the case. The ones with a strong "castle doctrine" are notable because this is not the norm. But, even so... > So - if an intruder breaks in to your house, you can shoot him without repercussions Your loose stair carpet was not created as a specific and immediate response to a particular unla…

So you're saying that a loose carpet on stairs would be illegal (i.e. a booby trap of sorts), but a security system where I can hit an alarm button and then it'll deploy a loose carpet onto the stairs, would be just fine?

> but a security system where I can hit an alarm button and then it'll deploy a loose carpet onto the stairs, would be just fine?

It may or may not be "just fine" in general (e.g., it might violate building codes, etc.), but if you deliberately used it in a condition where you were legally authorized to use deadly force in self defense, you probably wouldn't be liable for that particular use.

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

#142

Post by AstralStorm » Wed, Sep 07, 2016, 4:23 PM UTC

The other approach is to use time limited builds, like Google does with many alpha and beta versions in their Android toolchain. After the timeout, force the users to update or fully lock it down. With a nice message why it is happening, of course.

Crackers will bypass any kind of protection or change anyway.

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

#143

Post by AstralStorm » Wed, Sep 07, 2016, 4:30 PM UTC

soylentcola wrote: post #5

kazinator wrote: post #2

How about: have a really cheesy wallpapers in the pre-release builds which conveys the message (perhaps with explicit text right in the wallpaper image) that this is not a released build. Also, how about making not-released builds simply expire. The build should know that nobody ought to run it past a certain date. (If such operation is needed internally, it can be rigged with an extension mechanism built into the ex…

Isn't that the thought behind the watermarks they've had since Win7-ish? I remember messing with beta builds and reading about people using them (again, to avoid paying for it for a bit as mentioned in another comment) and jumping through all sorts of hoops to disable or hide the watermark - aside from buying a license of course. There's probably a point at which any more effort put into carrots (new features or wall…

Expiration has an additional positive effect in that it prevents use of the buggy builds and is also relatively easy to implement, especially when the prerelease build can phone home.

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

#144

Post by AstralStorm » Wed, Sep 07, 2016, 4:34 PM UTC

voltagex_ wrote: post #103

Seems like the "real" fix was the Windows Insider program. I'm still not sure why (myself included) people do testing for Microsoft for free, though.

Some people like to be the first to try out and talk about upcoming new features and messups.

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

#145

Post by AstralStorm » Wed, Sep 07, 2016, 4:38 PM UTC

pbhjpbhj wrote: post #137

Mithaldu wrote: post #61

Earlier quoted context omitted.

I'm sorry, but i have no idea what it does in regards to privacy features. I do however have access to this, and it works: http://i.imgur.com/9dutfsY.png

[Image shows Local Group Policy Editor screen with Configure Automatic Update settings pane open.]

Important: installing many big update packs manually will toggle this setting back.

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

#146

Post by estebank » Wed, Sep 07, 2016, 5:58 PM UTC

PhasmaFelis wrote: post #65

tedunangst wrote: post #39

Earlier quoted context omitted.

If this happens every week and you haven't done anything about it, well...

It only has to happen once. Besides which, a predictable failure is still a failure. By your logic, Win95 crashing several times a week wasn't a problem either.

Win95 crashing several times a week was a feature that would let you get away with not seeing this other bug: https://support.microsoft.com/en-us/kb/216641

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

#147

Post by monochromatic » Wed, Sep 07, 2016, 6:32 PM UTC

syshum wrote: post #134

monochromatic wrote: post #25

Earlier quoted context omitted.

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

The solution that is ending software patents which should not be a thing in the first place

K.

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

#148

Post by eridius » Wed, Sep 07, 2016, 8:42 PM UTC

eridius wrote: post #17

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…

You had warning. You just ignored it. You had plenty of warnings when installing the beta, and Apple typically does not provide updates from beta to GM. Just because you ignored the warnings doesn't mean they didn't exist. Stop blaming Apple for your own failings.

Incidentally, the iOS 10 GM Seed came out today, and Apple is in fact offering OTA updates from iOS 10 betas to the GM seed.

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

#149

Post by yongjik » Wed, Sep 07, 2016, 9:12 PM UTC

derefr wrote: post #123

hota_mazi wrote: post #108

Earlier quoted context omitted.

Sounds like standard business practice to me. If you can't understand basic instructions such as not leaking internal, confidential info, you deserve to be fired.

Oh, sure; I think the parent commenter's point was in thinking that emailing everyone about the termination of the leaker served as any sort of deterrence mechanism for people's use of the leaked build.

Well, emails are not exactly deterrence against people using the leaked "build": being an internet service company, that part is usually achieved by shutting down the server.

Emails are supposed to be deterrence against further leaks by reinforcing the "company culture". (Whether they work, I have no idea.)

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

#150

Post by sinxoveretothex » Wed, Sep 07, 2016, 9:33 PM UTC

bigiain wrote: post #91

sinxoveretothex wrote: post #72

Earlier quoted context omitted.

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

But how do you know they're not just doing all that for the old age care and retirement benefits?

Because there are absurdly rich parents who still show love for their children?