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

81–90 of 152 posts

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

#81

Post by dimgl »

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 an iPhone because of my extremely convoluted and totally self-created problem."

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

#82

Post by yongjik »

verst wrote: post #79
yongjik wrote: 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.

Yeah, I really liked Google's internal openness too, but the way they protected it felt a bit overzealous. As if I'm live-action roleplaying a spy organization or something.

Almost nobody seemed to have any problem with it, so I guess it's just me. ¯\_(ツ)_/¯

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

#83

Post by IntelMiner »

rodgerd wrote: post #76
0x0 wrote: post #73

Earlier quoted context omitted.

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.

Is this one of those "only in America" stereotypes? I'd love to see how the hell they justified that, much less if they won

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

#84

Post by khuey »

yongjik wrote: post #82
verst wrote: post #79

Earlier quoted context omitted.

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

Yeah, I really liked Google's internal openness too, but the way they protected it felt a bit overzealous. As if I'm live-action roleplaying a spy organization or something. Almost nobody seemed to have any problem with it, so I guess it's just me. ¯\_(ツ)_/¯

The alternative, where people don't share information internally because they're afraid of leaks, is pretty shitty.

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

#85

Post by aaronsnoswell »

cududa wrote: post #29
monochromatic wrote: post #25

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)

This is fascinating to me - do you know of any documented cases where a leak prevented someone filing for claim(s)?

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

#86

Post by nols »

IntelMiner wrote: post #83
rodgerd wrote: post #76

Earlier quoted context omitted.

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

Is this one of those "only in America" stereotypes? I'd love to see how the hell they justified that, much less if they won

The justification for a lot of these frivolous injury lawsuits are often very similar. The person suing has thousands or tens of thousands of medical debt. They could spend years paying it off or they could look like a moron in the hopes of a settlement that will pay off the debt or at least make a dent in it.

Probably the most famous case, Bodine v Enterprise High School, involved a teenager who fell through a painted over skylight while stealing (or redirecting to play basketball) a spotlight off the roof. Because of the fall he became a quadriplegic, he didn't really have much to lose suing the school district because, well, his life as he knew it was over. He had a lifetime of medical bills to pay and no way to earn an income.

There are definitely plenty of scam artists or leeches or whatever you want to call them abusing the legal system because it's easier than getting a real job, but don't underestimate the people backed into a corner by debt.

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

#87

Post by Klathmon »

cmdrfred wrote: post #68
devopsproject wrote: post #53

Earlier quoted context omitted.

Have you ever taken a support phone call? Many people won't read a simple error message, let alone a message that includes numbers and other "technical mumbo jumbo" customer: I'm trying print and it just says "error" me: It just says error? customer: yes me: Are there any other words or error numbers? customer: yeah, it says "No printers are installed. Add a printer and try again" me: facepalm Their solution works be…

How many of those types of users stay abreast of the latest preview builds from Microsoft?

Those with friends, family, or an IT worker that's a bit too clever with saving money.

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

#88

Post by optimiz3 »

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.

Patents. If you have features you need to file patents on, that needs to be done before the feature is publicly disclosed/exposed.

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

#89

Post by [deleted] »

cmdrfred wrote: post #68
devopsproject wrote: post #53

Earlier quoted context omitted.

Have you ever taken a support phone call? Many people won't read a simple error message, let alone a message that includes numbers and other "technical mumbo jumbo" customer: I'm trying print and it just says "error" me: It just says error? customer: yes me: Are there any other words or error numbers? customer: yeah, it says "No printers are installed. Add a printer and try again" me: facepalm Their solution works be…

How many of those types of users stay abreast of the latest preview builds from Microsoft?

[deleted]

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

#90

Post by dragonwriter »

IntelMiner wrote: post #83
rodgerd wrote: post #76

Earlier quoted context omitted.

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

Is this one of those "only in America" stereotypes? I'd love to see how the hell they justified that, much less if they won

> I'd love to see how the hell they justified that, much less if they won

There are general principles of responsibility of property owners for dangerous conditions on the property that apply even when the harm done by them is done to trespassers (and regardless of the purpose of the trespass.) IIRC, these are largely common law principles, and older than the US.

Of course, they don't relieve any criminal liability for crimes committed by the trespasser on the property, or any civil liability for torts committed on the property, but if you are already on the hook for those and can't try to claim that you weren't the intruder, there's no reason not to try to pursue any colorable claim you have.

Post reply on HN