Live data from Hacker News

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

blogs.msdn.microsoft.com

111–120 of 152 posts

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

#111
post #84
post #82

Earlier quoted context omitted.

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.

Cupertino

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

#112

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.

This thread is predicated on the assertion that users lose 10 or even 20 hours per week to reboots. Not just once.

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

#113

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

In Australia there are R&D tax concessions that apply differently based on whether something has shipped. That is, bug fixes on an unreleased feature are eligible as R&D, but once the feature ships work done on it is no longer R&D.

No idea if a leaked build would count as shipping for these purposes, though.

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

#114
post #86

Earlier quoted context omitted.

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 paint…

Thank you for this perspective; was a new take on a lot of the common tropes I've heard.

As said in Mr Robot, debt is the invisible hand that coerces us all

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

#115
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

Not limited to the US.

http://news.bbc.co.uk/2/hi/uk_news/england/2074077.stm

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

#117

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…

Don't think it would work.

"Super secret preview version of Windows X leaked! Download here!"

(...3 weeks later...)

"People trying Super secret preview version of Windows X get their hard drives wiped out! Was this Microsoft's plan all along? Please tell what you think!"

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

#118
post #41

Earlier quoted context omitted.

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…

this now happens on iOS but it's a relatively recent change, same for OS X.

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

#119
post #84
post #82

Earlier quoted context omitted.

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.

Another alternative is to work in an organization (most likely not a private company) that does not care about leaks. Non profits, administrations, many people work there and love it.

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

#120

This is such a Windows-person kind of solution. Come to think of it, I bet that this is why its so easy to change the wallpaper in Windows.

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

The Mac solution is that nobody installs an OS X upgrade until it's at the .1 release because everyone knows the .0 release breaks everything. You only install a beta if you're suicidal.
Post reply on HN