Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Normalize Identifying Corporate Devices in Your Software

lgug2z.com

Post reply on HN
Print view View original

51–60 of 62 posts

Re: Normalize Identifying Corporate Devices in Your Software

#51

Post by FateOfNations »

stoltzmann wrote: post #35
TrueDuality wrote: post #32

Having a device enrolled in an MDM package does not make it a corporate device. Many corporations require personal devices be managed to support remote wiping. If I install a productivity or developer tool on my personal phone or laptop for personal non-corporate use I would get mistaken as a corporate user by this process. If you want to collect this information you should be clear about it and know and understand y…

>Many corporations require personal devices be managed to support remote wiping. Corporations cannot require you to have your personal devices be managed by them. If you're surrendering your own gear to a company, it stops being your own device.

On iOS there is the concept of "Managed Apps" that is appropriate for a BYOD scenario. They are info sandboxed and can't share information (either direction) with unmanaged apps. That would count as an MDM enrollment, if you are looking for it.

Re: Normalize Identifying Corporate Devices in Your Software

#52

Post by TZubiri »

thewebguyd wrote: post #50
immibis wrote: post #27

Earlier quoted context omitted.

Ah, the Oracle and Broadcom model - Java, Virtualbox, VMware, etc. Woe betide thee who doesn't notice the difference between Oracle Java and OpenJDK.

No joke. Oracle will (happily) sink your company in license fees and litigation if they so much as git a whiff of Oracle Java being used commercially, accidentally or not.

As a software dev, that looks good to me. Software devs need to get paid.

Re: Normalize Identifying Corporate Devices in Your Software

#53

Post by WatchDog »

branon wrote: post #43

There appear to be ulterior sociopolitical motives held by the author, which involve using the blanket term "genocide-friendly software" [1] to refer to anything OSI-licensed (implicitly suggesting all contributors to anything not using his homebrewed license are supporters of genocide?) This does not look like a technical or business decision, but rather a malicious function used to identify users (and/or their empl…

He describes OSI licenses as “genocide-friendly”, and links to the OSI page about how their licenses don’t prohibit the software being used for “evil”.

Yet his own license also has no such prohibition. You are free to commit genocide using his tiling window manager, provided that your genocide is strictly non-commercial.

Re: Normalize Identifying Corporate Devices in Your Software

#54

Post by Dylan16807 »

dragonwriter wrote: post #29
kotaKat wrote: post #7

Earlier quoted context omitted.

This happens in a lot of software in the Windows world, too. As soon as you run it on a non-Home SKU you’re suddenly The Enterprise, even as a home-gamer.

I’ve used Pro (or Ultimate under Win 7) instead of Home for my personal devices since sometime in the XP era and literally never experienced this with anything.

I've never had a problem with Pro either.

I ran actual server windows for a while, and one single program refused that (Backblaze).

Re: Normalize Identifying Corporate Devices in Your Software

#55

Post by Dylan16807 »

TZubiri wrote: post #52
thewebguyd wrote: post #50

Earlier quoted context omitted.

No joke. Oracle will (happily) sink your company in license fees and litigation if they so much as git a whiff of Oracle Java being used commercially, accidentally or not.

As a software dev, that looks good to me. Software devs need to get paid.

Purchases should be consensual. Including the ones that pay for software devs.

Re: Normalize Identifying Corporate Devices in Your Software

#56

Post by groby_b »

layer8 wrote: post #13
groby_b wrote: post #9

Earlier quoted context omitted.

> People that run an AD domain for their home lab, people that use apple configurator to create profiles for their own devices (can enable some settings/features that are otherwise gated behind using an MDM profile - like shared iPads), etc. That's a tiny minority of your user base. You'll live. They'll live. > So who are you going to catch, really? Enterprises that are big enough to manage their fleet, but small eno…

The minority are typically also enthusiasts who serve as a multiplier. Alienating them isn’t the best strategy.

If you aim for large-scale Enterprise sales (which you should if you take this step), no, the folks running home labs are not usually the ones making decisions.

Re: Normalize Identifying Corporate Devices in Your Software

#57

Post by TZubiri »

Dylan16807 wrote: post #55
TZubiri wrote: post #52

Earlier quoted context omitted.

As a software dev, that looks good to me. Software devs need to get paid.

Purchases should be consensual. Including the ones that pay for software devs.

I don't find this to be always the case, there's many relationships were the nature of work cannot be established beforehand and we have open accounts, if you ever received an invoice you were part of such an account.

The proposal is simple, if you ever need a service and you request it of me, I will send you an invoice. It is implied in the request of my service that I would get paid, absent any negotiation for payment, I will send my best estimation.

Similarly if you download my software, absent any license, I have the right to send you an invoice. The fact that there's a license that explicitly mentions this is a nail on the coffin on the part of Oracle, but even without it there's quantum meruit.

Re: Normalize Identifying Corporate Devices in Your Software

#58

Post by Dylan16807 »

TZubiri wrote: post #57
Dylan16807 wrote: post #55

Earlier quoted context omitted.

Purchases should be consensual. Including the ones that pay for software devs.

I don't find this to be always the case, there's many relationships were the nature of work cannot be established beforehand and we have open accounts, if you ever received an invoice you were part of such an account. The proposal is simple, if you ever need a service and you request it of me, I will send you an invoice. It is implied in the request of my service that I would get paid, absent any negotiation for paym…

Oracle makes it very easy to hit by accident and charges way too much when it happens. It's bad behavior.

They are not charging based on benefit or use, or triple that.

Re: Normalize Identifying Corporate Devices in Your Software

#59

Post by immibis »

TZubiri wrote: post #52
thewebguyd wrote: post #50

Earlier quoted context omitted.

No joke. Oracle will (happily) sink your company in license fees and litigation if they so much as git a whiff of Oracle Java being used commercially, accidentally or not.

As a software dev, that looks good to me. Software devs need to get paid.

You have violated my license by replying to my comment. Pay me $10,000 or my lawyer will be in touch.

Obviously this is sarcasm. But what if it wasn't - would you think it was sensible? Comment writers need to get paid, so it's reasonable, yeah?

Part of Oracle's business model is tricking you into thinking you don't need to pay to use stuff, then extracting a much bigger payment in the resulting lawsuit.

Re: Normalize Identifying Corporate Devices in Your Software

#60

Post by yjftsjthsd-h »

TZubiri wrote: post #41
yjftsjthsd-h wrote: post #34

Earlier quoted context omitted.

If it gets normalized for software to notice when there's MDM in play, do you really think it won't be treated as a strong signal and used to break things?

Curb your slippery slope buddy. I think it's more productive to speak about concrete news presented to us instead of the hypothetical consequences it might have, real or imagined.

And that's how we get an industry full of entirely predictable consequences.
Post reply on HN