Trust also matters and a security "professional" who stabs someone in the back after supposedly reaching an understanding (the way you did me) is not trustrowthy. Neither is their software.
You may be winning in your own mind, but when you do so by violating trust you're destroying your own brand. Security is a trust-based market and nobody trusts you.
I've never tried to belittle (APK's) work, I've flat out said it's good by BronsCon
Context matters. If I recall correctly, I go on to point out that no matter how good your work may or may not be, your toxic personality makes everything you touch toxic as well. Sort of like a serial killer chef who makes the most wonderful of soufflé... which just so happens to be lethal within an hour of consumption.
I use a sleep tracking app that uses ultrasound to detect restlessness. It operates in the 20-24KHz band on devices with 48KHz DACs and up to 32KHz on phones with better hardware (like my current and last 3 devices) and seems to work quite reliably. Of course, I also have a $50 burner that I use when traveling which can't use that feature, but I really had to dig to find a device on which it wouldn't work.
That feature has to operate in the ultrasound range, as any audible sound may be disruptive to one's sleep, especially at the volume levels required to map out movement of people or objects using a single stationary emitter and receiver.
I wouldn't be so quick to claim the average phone can't put out, or pick up, ultrasonic signals.
But the tiniest bit of research will tell you that's precisely the band it uses. Yes, technically "ultrasound" starts at 20KHz, so even a 44.1KHz DAC can handle low ultrasound, up to 22.05KHz. That's a 2.05KHz band, well wider than the 1.5KHz band currently being utliized, so there's plenty of room for them to migrate to that band (or the 22-24KHz band made available by the 48KHz [minimum] DACs found in all current model phones) at any point in the future.
Workaround: start jerkin' it whenever an ad you don't care about comes on. Reinforce ineffective ads to drive ad agency success rates through the floor.
Sorry to say, but the old-folks, no matter how many generations back you go were just as lazy and indifferent about this stuff as we are now.
This is correct; it is once you stop being willing to take it up the ass from everyone who expects you to do so that you become one of the "old folks" yourself. I've been one for over a decade now and I'm only 35.
If the ad is part of the video supplied to Hulu, it would be part of the video supplied to Netflix, as well. I subscribe to both services and, well, I'll tell you it's sure nice not having to wait until the next season of a show starts and I've already had the previous season's spoilers crammed down my throat before I get to watch a show. Perhaps that's why Hulu is so successful.
Mostly commercial free, shows form some providers get "limited" ads at the beginning and end even with the $4 surcharge. WTF?
While you are correct with regard to how the $7.99/mo subscription works, I was referring to the pre-roll ads that are seen even with a $12.99/mo "ad free" subscription the commenter above me was talking about. You know, the subscription level where Hulu doesn't play their own ads during the show.
I believe, and I may be wrong about this, that those ads are actually part of the video provided to Hulu, rather than being inserted by Hulu themselves.
Because of the lack of standardization for BIOS, the only operation that I ever had to do non-remotely is configuring the BIOS for any new motherboard.
There's your use case for AMT, right there. That, and reinstalling the OS. Oh, and booting from an ISO to run things like Memtest86 and other offline diagnostic software. Basically anything where you may need to interact with the system before the OS has booted.
That said, I don't believe it's worth the risk to enable AMT and make it accessible over the public internet, but you weren't asking for that, you were seeking use cases and I gave you a handful.
I'm relying on the underlying system not to be a porous system designed to run as root.
Well, that hasn't been the case since Vista. In fact, it was that architectural change that caused the most outcry among users and developers alike. I firmly believe that Windows 7 was nothing more than a re-release of Vista with a more polished UI, timed to coincide with the majority of software vendors finally making their apps compatible with the new security architecture.
At any rate, if you're allowing the attacks to get near your system in the first place, there are many out there that will infiltrate your Mac just the same. Vault 7 revealed much of what I could not.
BTW, hackintoshes are rock stable if you purchase reliable hardware. The upgrades can be a bit tricky at times, but run time is measured in months.
Not just upgrades, updates can break things, in my experience. While the idea of uptimes measured in months does sound nice on the surface, the reality is that many of Apple's updates are patches for remotely-exploitable vulnerabilities and, on top of that, require a reboot. Yes, there are Mac OS updates that require a reboot; and they're more common than anyone with a multi-month uptime might realize. Not installing them isn't doing your system security any favors and running a Hackintosh often requires delaying the installation of updates.
That said, my hope is that the next run of Mac Pros will utilize Ryzen, as it really does make sense for Apple to go that route, and I'll be able to throw Mac OS in a VM on my workstation. I've got things sufficiently locked down that I'm not really super worried about a VM being a month or two behind on updates. For the workloads a Mac Pro is supposedly marketed toward, Ryzen absolutely thrashes Intel at this point in time; I'm sure Intel will release something faster in short order, to which AMD will respond in kind. From where I'm sitting, Ryzen will stay ahead of Intel's platforms for the foreseeable future.
All Apple needs to do to enable support is set a couple of compiler flags; or so I heard when I was looking to get a Sierra VM running on the FX-based workstation this Ryzen box replaced. It was shortly after Sierra came out, before the updated Darwin source was released, and the claims I was reading were along the lines of "I'll compile it with the right flags the moment it's released and we'll be able to run Sierra on AMD that same evening." I'm sure there's a bit more optimization necessary for Ryzen, but they'd at least have it running, which would be a start; and it might outperform the higher-end i7s (in some tasks, at least) just as it does under Windows and Linux without optimization.
I think I love you. Seriously, in all my pleading with Apple to re-release an actual Pro-level system like they used to make back in 2012, why did I never think of this?
For starters... ugh... HTML editing on iOS... not without a hardware keyboard!!! As for WebKit on iOS 9, it's up to the developers of a given site to decide what they want to support and make it work; I do find it ironic that MacRumors has issues on that particular platform, though.
One commonly missed detail about web development is that web developers must write a single codebase that works everywhere. We don't get to fork our code for Windows, Mac, Linux, iOS, Android, and BlackBerry. We don't get to provide a different binary for each platform, complete with fixes and workarounds specific to that platform.
Sure, we can throw a mish-mash of fixes and workarounds in the middle of our code, stuffed in some conditional statements, and that can work wonders if the user has Javascript enabled. If they don't, and the issues being worked around or fixed are in HTML or CSS (where the only other way to fix them is via UA sniffing), they just don't get the fix. If we opt to fix those issues via UA sniffing, and the user happens to use an add-on that masks or changes their user agent string (many proxies use their own UA string as well, so it might not always be the user doing it), they aren't gonna get the fix.
In many ways I (a web developer and thus, in the eyes of many, not a real developer) miss desktop development. It's much simpler to get everything right on a given platform, then port to the next platform you wish to support, or develop multiple platforms in parallel with conditional fixes (which are applied by the compiler once it knows which platform it's targeting during the build process) or forks (wherein you apply platform-specific fixes only to the relevant fork). Did I mention I'm also a desktop guy (e.g. a real developer in the eyes of zealots who don't understand that web development is actually more difficult)?
Desktop is simply not where my money comes from anymore, because I do web development right and clients are willing to pay a premium for that over how most web developers operate. The main difference is, with desktop and mobile development, you get to choose which platforms (and versions) you will support. With web development, the users decide and you either support them or look bad.
In this case, sadly, MacRumors has chosen "look bad" as their option. I can't really blame them; they may not have the means to test on that platform and it's better to make it clear you've abandoned a given platform than to look like you simply lack the competence to make it work.
Now, that's not to say everything I put out there is perfect. I have one client for whom I am working on an inherited codebase that is just a nightmare of intertwined dependencies and references piled on top of legacy code relying on versions of libraries that no longer support current versions of IE, so much of the javascript on their site is currently broken on IE9 and newer as a result. I know of the issue (clearly), as do they, and they have decided other matters are more pressing until I can hire someone to keep progress going while I refactor the mess and update the older code to no longer use methods which have been removed from current versions of the aforementioned libraries (and are deprecated in the versions currently in use).
I display my brand slightly less prominently than that of the original developer in the footer of their site. After the refactoring, which will more resemble a full rewrite, my logo will take up the space currently shared by both and the original vendor's logo will be removed. I intend to keep so little of the original code that it will bear no resemblance to the product it is based on; there will be nothing left to give them credit for.
Of course, if this were a desktop application, I could simply not provide a binary for that secondary platform and there would be nothing to fix. How easy the desktop guys have it, and they don't even realize!
Microsoft is moving to completely lockdown Windows so you can only install software from the Windows store
And that will be the start of the last days of their reign over the consumer desktop. Sure, they'll probably still rule business, but the moment someone can't install their old games on their new computer, that user will seek an alternative platform. By then, those old games will run fine under WINE.
That could, literally, lead to the year of the Linux desktop.
Mind you, I'm not saying the year of the Linux desktop is in sight; I'm saying even Microsoft isn't that stupid.
What the politicians supporting the laws to enforce such policies failed to understand is that, since the employee is expected to furnish their own cubby liner, the liner is, itself, a personal effect and can not be installed in the cubby prior to the installation of said employee-provided cubby liner. This, of course, renders the availability of said cubbies moot, as the employee can never actually put anything in them.
Trust also matters and a security "professional" who stabs someone in the back after supposedly reaching an understanding (the way you did me) is not trustrowthy. Neither is their software.
You may be winning in your own mind, but when you do so by violating trust you're destroying your own brand. Security is a trust-based market and nobody trusts you.
I've never tried to belittle (APK's) work, I've flat out said it's good by BronsCon
Context matters. If I recall correctly, I go on to point out that no matter how good your work may or may not be, your toxic personality makes everything you touch toxic as well. Sort of like a serial killer chef who makes the most wonderful of soufflé... which just so happens to be lethal within an hour of consumption.
Living a few miles west of it, I must say yes, it will be. Finally getting to give the rest of you all the finger as we float away...
Perhaps we can find a nice quiet diner where we can hold our weekly meetings without having to yell over the noise of all them damn kids?
I use a sleep tracking app that uses ultrasound to detect restlessness. It operates in the 20-24KHz band on devices with 48KHz DACs and up to 32KHz on phones with better hardware (like my current and last 3 devices) and seems to work quite reliably. Of course, I also have a $50 burner that I use when traveling which can't use that feature, but I really had to dig to find a device on which it wouldn't work.
That feature has to operate in the ultrasound range, as any audible sound may be disruptive to one's sleep, especially at the volume levels required to map out movement of people or objects using a single stationary emitter and receiver.
I wouldn't be so quick to claim the average phone can't put out, or pick up, ultrasonic signals.
But the tiniest bit of research will tell you that's precisely the band it uses. Yes, technically "ultrasound" starts at 20KHz, so even a 44.1KHz DAC can handle low ultrasound, up to 22.05KHz. That's a 2.05KHz band, well wider than the 1.5KHz band currently being utliized, so there's plenty of room for them to migrate to that band (or the 22-24KHz band made available by the 48KHz [minimum] DACs found in all current model phones) at any point in the future.
Workaround: start jerkin' it whenever an ad you don't care about comes on. Reinforce ineffective ads to drive ad agency success rates through the floor.
Even the cheapest bottom-of-the-barrel phones have 48KHz DACs, but that's largely irrelevant when we're talking about the 18.5-20KHz band.
Sorry to say, but the old-folks, no matter how many generations back you go were just as lazy and indifferent about this stuff as we are now.
This is correct; it is once you stop being willing to take it up the ass from everyone who expects you to do so that you become one of the "old folks" yourself. I've been one for over a decade now and I'm only 35.
If the ad is part of the video supplied to Hulu, it would be part of the video supplied to Netflix, as well. I subscribe to both services and, well, I'll tell you it's sure nice not having to wait until the next season of a show starts and I've already had the previous season's spoilers crammed down my throat before I get to watch a show. Perhaps that's why Hulu is so successful.
Mostly commercial free, shows form some providers get "limited" ads at the beginning and end even with the $4 surcharge. WTF?
While you are correct with regard to how the $7.99/mo subscription works, I was referring to the pre-roll ads that are seen even with a $12.99/mo "ad free" subscription the commenter above me was talking about. You know, the subscription level where Hulu doesn't play their own ads during the show.
I believe, and I may be wrong about this, that those ads are actually part of the video provided to Hulu, rather than being inserted by Hulu themselves.
You read that correctly, and you're welcome.
Wait... is that real?
No. It's not.
I read that as "I'm not dressed" and my first thought was "whoa, man, like... me either!"
Because of the lack of standardization for BIOS, the only operation that I ever had to do non-remotely is configuring the BIOS for any new motherboard.
There's your use case for AMT, right there. That, and reinstalling the OS. Oh, and booting from an ISO to run things like Memtest86 and other offline diagnostic software. Basically anything where you may need to interact with the system before the OS has booted.
That said, I don't believe it's worth the risk to enable AMT and make it accessible over the public internet, but you weren't asking for that, you were seeking use cases and I gave you a handful.
I'm relying on the underlying system not to be a porous system designed to run as root.
Well, that hasn't been the case since Vista. In fact, it was that architectural change that caused the most outcry among users and developers alike. I firmly believe that Windows 7 was nothing more than a re-release of Vista with a more polished UI, timed to coincide with the majority of software vendors finally making their apps compatible with the new security architecture.
At any rate, if you're allowing the attacks to get near your system in the first place, there are many out there that will infiltrate your Mac just the same. Vault 7 revealed much of what I could not.
BTW, hackintoshes are rock stable if you purchase reliable hardware. The upgrades can be a bit tricky at times, but run time is measured in months.
Not just upgrades, updates can break things, in my experience. While the idea of uptimes measured in months does sound nice on the surface, the reality is that many of Apple's updates are patches for remotely-exploitable vulnerabilities and, on top of that, require a reboot. Yes, there are Mac OS updates that require a reboot; and they're more common than anyone with a multi-month uptime might realize. Not installing them isn't doing your system security any favors and running a Hackintosh often requires delaying the installation of updates.
That said, my hope is that the next run of Mac Pros will utilize Ryzen, as it really does make sense for Apple to go that route, and I'll be able to throw Mac OS in a VM on my workstation. I've got things sufficiently locked down that I'm not really super worried about a VM being a month or two behind on updates. For the workloads a Mac Pro is supposedly marketed toward, Ryzen absolutely thrashes Intel at this point in time; I'm sure Intel will release something faster in short order, to which AMD will respond in kind. From where I'm sitting, Ryzen will stay ahead of Intel's platforms for the foreseeable future.
All Apple needs to do to enable support is set a couple of compiler flags; or so I heard when I was looking to get a Sierra VM running on the FX-based workstation this Ryzen box replaced. It was shortly after Sierra came out, before the updated Darwin source was released, and the claims I was reading were along the lines of "I'll compile it with the right flags the moment it's released and we'll be able to run Sierra on AMD that same evening." I'm sure there's a bit more optimization necessary for Ryzen, but they'd at least have it running, which would be a start; and it might outperform the higher-end i7s (in some tasks, at least) just as it does under Windows and Linux without optimization.
One can hope and dream, right?
I think I love you. Seriously, in all my pleading with Apple to re-release an actual Pro-level system like they used to make back in 2012, why did I never think of this?
For starters... ugh... HTML editing on iOS... not without a hardware keyboard!!! As for WebKit on iOS 9, it's up to the developers of a given site to decide what they want to support and make it work; I do find it ironic that MacRumors has issues on that particular platform, though.
One commonly missed detail about web development is that web developers must write a single codebase that works everywhere. We don't get to fork our code for Windows, Mac, Linux, iOS, Android, and BlackBerry. We don't get to provide a different binary for each platform, complete with fixes and workarounds specific to that platform.
Sure, we can throw a mish-mash of fixes and workarounds in the middle of our code, stuffed in some conditional statements, and that can work wonders if the user has Javascript enabled. If they don't, and the issues being worked around or fixed are in HTML or CSS (where the only other way to fix them is via UA sniffing), they just don't get the fix. If we opt to fix those issues via UA sniffing, and the user happens to use an add-on that masks or changes their user agent string (many proxies use their own UA string as well, so it might not always be the user doing it), they aren't gonna get the fix.
In many ways I (a web developer and thus, in the eyes of many, not a real developer) miss desktop development. It's much simpler to get everything right on a given platform, then port to the next platform you wish to support, or develop multiple platforms in parallel with conditional fixes (which are applied by the compiler once it knows which platform it's targeting during the build process) or forks (wherein you apply platform-specific fixes only to the relevant fork). Did I mention I'm also a desktop guy (e.g. a real developer in the eyes of zealots who don't understand that web development is actually more difficult)?
Desktop is simply not where my money comes from anymore, because I do web development right and clients are willing to pay a premium for that over how most web developers operate. The main difference is, with desktop and mobile development, you get to choose which platforms (and versions) you will support. With web development, the users decide and you either support them or look bad.
In this case, sadly, MacRumors has chosen "look bad" as their option. I can't really blame them; they may not have the means to test on that platform and it's better to make it clear you've abandoned a given platform than to look like you simply lack the competence to make it work.
Now, that's not to say everything I put out there is perfect. I have one client for whom I am working on an inherited codebase that is just a nightmare of intertwined dependencies and references piled on top of legacy code relying on versions of libraries that no longer support current versions of IE, so much of the javascript on their site is currently broken on IE9 and newer as a result. I know of the issue (clearly), as do they, and they have decided other matters are more pressing until I can hire someone to keep progress going while I refactor the mess and update the older code to no longer use methods which have been removed from current versions of the aforementioned libraries (and are deprecated in the versions currently in use).
I display my brand slightly less prominently than that of the original developer in the footer of their site. After the refactoring, which will more resemble a full rewrite, my logo will take up the space currently shared by both and the original vendor's logo will be removed. I intend to keep so little of the original code that it will bear no resemblance to the product it is based on; there will be nothing left to give them credit for.
Of course, if this were a desktop application, I could simply not provide a binary for that secondary platform and there would be nothing to fix. How easy the desktop guys have it, and they don't even realize!
As for why I'm able to "get away with" ignori
Microsoft is moving to completely lockdown Windows so you can only install software from the Windows store
And that will be the start of the last days of their reign over the consumer desktop. Sure, they'll probably still rule business, but the moment someone can't install their old games on their new computer, that user will seek an alternative platform. By then, those old games will run fine under WINE.
That could, literally, lead to the year of the Linux desktop.
Mind you, I'm not saying the year of the Linux desktop is in sight; I'm saying even Microsoft isn't that stupid.
What the politicians supporting the laws to enforce such policies failed to understand is that, since the employee is expected to furnish their own cubby liner, the liner is, itself, a personal effect and can not be installed in the cubby prior to the installation of said employee-provided cubby liner. This, of course, renders the availability of said cubbies moot, as the employee can never actually put anything in them.
This is our future.
How do you think we got rid of religion?
I'm not sure I'd use "Stack Overflow agrees with me" as a supporting argument. I mean, in this case you're not wrong, but... Just be careful with it :)
press-to-order buttons hanging on the wall
...
prime examples
I see what you did there...
Ugh... HTML quote fail... Whatever, you know which part of that you wrote and which part was written by me...