I use Handbrake for those things which uses the ffmpeg libraries. Never used ShadowPlay but ffmpeg generally compresses much more than anything I've seen before.
For recording, I would use an external HDMI encoder, you can stream it into a separate machine to stream composed video out with OBS Studio, you don't need anything fancy in regards video cards, I've seen it used on a Core i7 rig with a relatively cheap video card.
Android is just poor at having anything working at all. If you're used to Apple and Linux, Android and Microsoft are very poor user/power user experiences
If you've ever worked with real users, you'd know that isn't the case. We had Microsoft-boffins thinking the same exact thing about our "corporate e-mail" with ~15,000 users - nobody uses POP3/IMAP and it's a huge headache for Exchange to badly implement it, let's turn it off. We had a small riot on our hand from hundreds of users and even a number of Exchange-to-IMAP instances popping up.
That's not what the argument is about. UEFI SecureBoot has its place and reasons although an open implementation would be much better, Linux Kernel Lockdown has its place and reasons. Requiring one to enable the other is a problem or declaring that your system is broken without both enabled is a problem.
It's quite normal I'm told as long as they aren't interrupting your life and they are your voices. The problem would be when you hear voices that you don't identify as your own.
Although this is a fun exercise, you have to think about the usability in security schemes. When it is more complex than red-orange-green, people will ignore it. And as I said, if you have more than 1% of grey areas, false positives or false negatives, you've conditioned your users to ignore it.
I have between 2 and 6 voices going on internally simultaneously, typically when I'm multitasking or mulling over a difficult problem, the voice keeps going on in the background (quite literally as if you're in a shared office) and occasionally interrupts the current primary conversation. I also have conversations with myself in my head and they have different voices.
Okay, except that while you're setting up the infrastructure, pretty much every e-mail is going to be orange or red as will the e-mail for everybody that doesn't join the system. Eventually (in a matter of minutes-hours) you'll condition your users to ignore the thing.
My point was that those schemes have been tried. The problem generally boils down to the fact that a) Everyone needs to participate all at once for the plan to succeed b) Everyone needs to agree on a plan to succeed in the first place c) It doesn't account for anyone's privacy or personal security (eg. whistleblowers)
They resell it on the energy market, probably at a premium. This is similar to saying: Google is helping small business by investing in the stock market, technically true, but it doesn't mean they are adding any true value to any specific business.
You can't "buy" energy (as in the electrons) from a specific plant, it's the energy equivalent of a stock market - you buy futures for renewable electric and if you buy too much, you can sell it off at any particular point in time, eg. when there is a lot of demand.
Pay me 500k a year and I don't care if you help out the government. It's why you get paid the 500k, to focus on the job and not partisan political issues. If you pay taxes, you helped fund the Pentagon AI project more than being a part of Google's workforce.
But that doesn't prevent me from sending an unsigned message through a relay and unless the user has the technical chops to distinguish the two, it doesn't matter much.
Should the President have an unguarded wooden interior door as an entrance to the White House? You just don't use e-mail for highly secure communications. If you receive an e-mail, you should distrust it.
There is this checklist that pops up here on Slashdot once in a while. There is no way of making e-mail secure. Yes, I could send an e-mail from obama@whitehouse.gov from my personal e-mail server and nobody would be able to prevent it. There are ways of verifying, but all parties have to agree on the method of verification and how that is done depends on whether you're Yahoo, Microsoft or Google
Bricked means you can't even JTAG it. As long as there is a way in with software, there is a way to fix it. Bricking meant at some point overdriving the CRT or over-volting the CPU to the point they burnt out or breaking the fuses in an EPROM. These days most of that is impossible through various safety measures both in firmware and hardware, you could technically still 'brick' a solid state drive by doing weird stuff with it.
Apple releases beta and developer software updates WELL ahead of release and it's free. I got this update in mid-January. If your vendor does something very low-level and can't be bothered to fix their shit in 3-4 months, then the problem lies with the vendor, not Apple.
It could be either, just depends on what the original spec said. I would find it useful to be able to cover an entire set of numbers simply by leaving them blank, very similar to eg. IP addresses. Even in some configuration files, you can type in 10/8 and it will recognize it as being "10.0.0.0/8".
And the US has a great immigration policy, basically you have to be able to earn enough income in order to pay taxes (so 75k/y and up) or be somehow related to a US citizen (by birth or by marriage) and then you're very welcome in the US. I've done it, it's not hard, it takes about a half year to three years depending on your circumstances.
Slashdot Mirror
I use Handbrake for those things which uses the ffmpeg libraries. Never used ShadowPlay but ffmpeg generally compresses much more than anything I've seen before.
For recording, I would use an external HDMI encoder, you can stream it into a separate machine to stream composed video out with OBS Studio, you don't need anything fancy in regards video cards, I've seen it used on a Core i7 rig with a relatively cheap video card.
Android is just poor at having anything working at all. If you're used to Apple and Linux, Android and Microsoft are very poor user/power user experiences
Because the Windows Mail client pushes ads. That and it's emulating Office 365 which is just as poor as a mail system as Windows Mail.
If you've ever worked with real users, you'd know that isn't the case. We had Microsoft-boffins thinking the same exact thing about our "corporate e-mail" with ~15,000 users - nobody uses POP3/IMAP and it's a huge headache for Exchange to badly implement it, let's turn it off. We had a small riot on our hand from hundreds of users and even a number of Exchange-to-IMAP instances popping up.
That's not what the argument is about. UEFI SecureBoot has its place and reasons although an open implementation would be much better, Linux Kernel Lockdown has its place and reasons. Requiring one to enable the other is a problem or declaring that your system is broken without both enabled is a problem.
It's quite normal I'm told as long as they aren't interrupting your life and they are your voices. The problem would be when you hear voices that you don't identify as your own.
Although this is a fun exercise, you have to think about the usability in security schemes. When it is more complex than red-orange-green, people will ignore it. And as I said, if you have more than 1% of grey areas, false positives or false negatives, you've conditioned your users to ignore it.
Wonder if staffing that office for the last decade cost more than the license will bring in?
I have between 2 and 6 voices going on internally simultaneously, typically when I'm multitasking or mulling over a difficult problem, the voice keeps going on in the background (quite literally as if you're in a shared office) and occasionally interrupts the current primary conversation. I also have conversations with myself in my head and they have different voices.
Okay, except that while you're setting up the infrastructure, pretty much every e-mail is going to be orange or red as will the e-mail for everybody that doesn't join the system. Eventually (in a matter of minutes-hours) you'll condition your users to ignore the thing.
My point was that those schemes have been tried. The problem generally boils down to the fact that
a) Everyone needs to participate all at once for the plan to succeed
b) Everyone needs to agree on a plan to succeed in the first place
c) It doesn't account for anyone's privacy or personal security (eg. whistleblowers)
They resell it on the energy market, probably at a premium. This is similar to saying: Google is helping small business by investing in the stock market, technically true, but it doesn't mean they are adding any true value to any specific business.
You can't "buy" energy (as in the electrons) from a specific plant, it's the energy equivalent of a stock market - you buy futures for renewable electric and if you buy too much, you can sell it off at any particular point in time, eg. when there is a lot of demand.
Pay me 500k a year and I don't care if you help out the government. It's why you get paid the 500k, to focus on the job and not partisan political issues. If you pay taxes, you helped fund the Pentagon AI project more than being a part of Google's workforce.
But that doesn't prevent me from sending an unsigned message through a relay and unless the user has the technical chops to distinguish the two, it doesn't matter much.
Should the President have an unguarded wooden interior door as an entrance to the White House? You just don't use e-mail for highly secure communications. If you receive an e-mail, you should distrust it.
There is this checklist that pops up here on Slashdot once in a while. There is no way of making e-mail secure. Yes, I could send an e-mail from obama@whitehouse.gov from my personal e-mail server and nobody would be able to prevent it. There are ways of verifying, but all parties have to agree on the method of verification and how that is done depends on whether you're Yahoo, Microsoft or Google
They're offering low-level driver downloads that go deep in the kernel of your OS. Yeah, I don't want SSL on that at all!
Bricked means you can't even JTAG it. As long as there is a way in with software, there is a way to fix it. Bricking meant at some point overdriving the CRT or over-volting the CPU to the point they burnt out or breaking the fuses in an EPROM. These days most of that is impossible through various safety measures both in firmware and hardware, you could technically still 'brick' a solid state drive by doing weird stuff with it.
Apple releases beta and developer software updates WELL ahead of release and it's free. I got this update in mid-January. If your vendor does something very low-level and can't be bothered to fix their shit in 3-4 months, then the problem lies with the vendor, not Apple.
*whoosh*
Use Dhrystones and Whetstones
The employment route doesn't make you an indentured servant, H1B is not the only option.
It could be either, just depends on what the original spec said. I would find it useful to be able to cover an entire set of numbers simply by leaving them blank, very similar to eg. IP addresses. Even in some configuration files, you can type in 10/8 and it will recognize it as being "10.0.0.0/8".
And the US has a great immigration policy, basically you have to be able to earn enough income in order to pay taxes (so 75k/y and up) or be somehow related to a US citizen (by birth or by marriage) and then you're very welcome in the US. I've done it, it's not hard, it takes about a half year to three years depending on your circumstances.
Lol slashdot cuts the url at just the right length to know it's a partisan site.