Unfortunately, disabling the phone while driving is a bad idea, because how is the phone supposed to know it's being used by a driver rather than a passenger? Same thing with in-car navigation systems: it's very annoying to not be able to operate it while the car is moving as a passenger. There's really no excuse there, since it could just detect if there's someone in the passenger seat using the existing sensor for the passenger seatbelt warning.
Even if everything got jammed, the drone could still potentially take out targets using GPS or other techniques. Even if you jammed GPS on top of all that, the drone could still likely return to base. Don't forget, people flew planes before electronics.
But you also lack the ability to intervene (or at least call security/police) in case of a fight, or answer question about the route. I've even had a bus driver disallow someone from riding the bus, because, I quote verbatim, "I can smell you from here". Show me a machine that will do that!
Surely it couldn't be that hard to fix. As I understand it, the only reason to let applications grab events from other applications is to allow global hotkeys to be implemented. If that's the case, then don't send alphanumeric keys to other applications, unless accompanied with a modifier other than Shift or AltGr.
The draw of it is that a normal welfare system is always going to be expensive regardless of who's running it. It becomes even worse when it's welfare concerning a specific good (food stamps, housing, etc). Think about a program like SNAP/EBT. You have to:
1. Figure out who's eligible, which means you're going to have to hire a bunch of people to review applications. You also have to prevent people from defrauding the system.
2. Figure out what stores or products should be eligible. Again, probably requires a review process, possibly some actual enforcement.
3. Build and support infrastructure for the actual distribution/payment system.
Now, the overhead for SNAP last year was only about 6%, which sounds small. But if you look at the trends in the data, you see that percentage-wise, it has lower overhead when more people are participating in the program (and hits over 20% in years with less participants). So the data hints that it's likely more efficient to have fewer but larger welfare programs, rather than smaller, more specific ones. UBI is just the ultimate extension of that, with even less overhead because of the "universal" part. You don't have to decide who receives it (everyone), so there's also less fraud (all you can do is try to nab someone else's on top of yours).
Depends on the scope... and all it takes is for one key group of people (*nix sysadmins, say) to refuse and stand firm on that refusal.
If your refusal to do knowledge transfer prevents someone from operating a system you maintain, then you are very bad at your job. If a bus hit me tomorrow, any of my coworkers could pick up the systems I maintain using the documentation. Worse case, if a bus took out the entire operations team, someone from outside of the company would be able to use the docs to come up to speed.
If you've left such sparse documentation that no one can figure out how to maintain your systems, the company is better off without you.
And who controls the documentation? If the entire IT department simply locked away the documentation, they'd be SOL.
Wouldn't people just cam the movie with their phones that they're allowed to have out in the theater? Can't wait to see the MPAA try to sue a 15 year old for $50,000,000.
Now if only Firefox wouldn't "helpfully" reopen a 200-tab session on me. Chrome seems to always ask to restore regardless of how the browser exited, while Firefox just feels like opening it after a crash (which for me is usually a shutdown). There's also the fact that I had to install the dev version so I could get 64-bit because the 32-bit version would start to run out of RAM, become flaky as hell, then eventually crash.
99% of USB devices work with completely generic drivers. The whole "I need a vendor-specific driver for a device that uses completely standard protocols" is mostly a Windows-only thing. Plus there's USB passthrough for virtualization anyway, so worst case you can jus fire up a Windows VM.
I wouldn't be surprised if Apple's margins are so high that they only need one or two successful products to stay afloat to begin with. Even if a couple of their products turn out to be subpar, iPhones will always sell, not to mention Macs are snapped up like hotcakes for a variety of reasons.
everyone will hit me with the malware issue... so let's image that they clean that up
then what's the excuse?
Let's cross that bridge when we come to it. Which is a very short bridge, since many sites aren't responsible with the amount and/or placement of ads (see: Wikia).
I just love how Steam tries so hard to use their "mobile authenticator" thing, when all that accomplishes is giving someone who exploits your phone access to the Steam credentials, steam guard auth, and recovery email all in one go. At least with the Blizzard authenticator app, it didn't hold any account credentials, and you could buy hardware ones too.
On top of that, even if you had 500-factor authentication, it wouldn't stop some luser from getting phished, since they'd just put their 500 authentication details into the fake page.
I think this is actually a good thing. It's much better (and less damaging) to put power in the hands of end-users, rather than in a central moderation authority. Ignoring a viewpoint is a much better idea than censoring it from everyone. The problem with harassment is that one man's disagreement is another man's harassment, so rather than have moderators try to decide if something is over the line or not, just let people decide for themselves. Yes, people sticking their fingers in their ears when someone disagrees is bad, but calling for censorship is even worse.
Easy enough, just have the device identify as both a flash drive AND a keyboard. Keyboard presses Win-R and types the path to the malicious file on the drive.
The problem is that many devices show up as both a keyboard and a mouse, and possibly other devices as well. Devices with macro support tend to show up as both so they can have macros for both keyboard and mouse actions. Wireless keyboard/mouse dongles usually show up as both even if you only have one type of device paired to them. I've even had a webcam with some buttons on it which showed up as a keyboard. Some devices might even show up as more than one of each to get around limitations.
Well, he wasn't entirely wrong. When the iPhone first came out, it wasn't that great for productivity. Sites weren't mobile-friendly, it only had shitty EDGE cellular internet, didn't have (official) third party app support. Back then, you had to jailbreak it for the thing to be usable.
I actually have no problem with long copyright terms for actively used IP e.g. Mickey Mouse, but anything not actively used should become public domain very fast (especially abandonware).
I'd have a good deal of sympathy for them if they were small artists struggling to make a living, where piracy might literally be starving them. But instead, these are huge artists who make shitloads of money despite this piracy they're complaining about. It would be like Bill Gates complaining that a poor person slipped onto a bus without paying. Move over global warming, MPAA/RIAA crying is the leading cause of rising sea levels.
1. Spanish class gets a reputation as being the "easy" second language class.
2. Idiots pour into Spanish class because of #1.
3. #1 becomes a self-fulfilling prophecy as the class has to be slowed down significantly for them.
As I understand it, WPA wouldn't allow clients to decode other clients' packets, even if they know the key for initially connecting. Thus, you could just designate a password (even "password") for open networks to give people encryption yet still be open. In the meantime, you could just name your network PASSWORD_IS_xyz.
I don't think it's a huge burden. First-time customers would have to put in the password, but it's not like they're going to say "oh, you're making me put in a password for the wifi? I'll go eat somewhere else". Non-first-timers would already have the password saved.
Unfortunately, disabling the phone while driving is a bad idea, because how is the phone supposed to know it's being used by a driver rather than a passenger? Same thing with in-car navigation systems: it's very annoying to not be able to operate it while the car is moving as a passenger. There's really no excuse there, since it could just detect if there's someone in the passenger seat using the existing sensor for the passenger seatbelt warning.
Even if everything got jammed, the drone could still potentially take out targets using GPS or other techniques. Even if you jammed GPS on top of all that, the drone could still likely return to base. Don't forget, people flew planes before electronics.
But you also lack the ability to intervene (or at least call security/police) in case of a fight, or answer question about the route. I've even had a bus driver disallow someone from riding the bus, because, I quote verbatim, "I can smell you from here". Show me a machine that will do that!
Surely it couldn't be that hard to fix. As I understand it, the only reason to let applications grab events from other applications is to allow global hotkeys to be implemented. If that's the case, then don't send alphanumeric keys to other applications, unless accompanied with a modifier other than Shift or AltGr.
The draw of it is that a normal welfare system is always going to be expensive regardless of who's running it. It becomes even worse when it's welfare concerning a specific good (food stamps, housing, etc). Think about a program like SNAP/EBT. You have to:
1. Figure out who's eligible, which means you're going to have to hire a bunch of people to review applications. You also have to prevent people from defrauding the system.
2. Figure out what stores or products should be eligible. Again, probably requires a review process, possibly some actual enforcement.
3. Build and support infrastructure for the actual distribution/payment system.
Now, the overhead for SNAP last year was only about 6%, which sounds small. But if you look at the trends in the data, you see that percentage-wise, it has lower overhead when more people are participating in the program (and hits over 20% in years with less participants). So the data hints that it's likely more efficient to have fewer but larger welfare programs, rather than smaller, more specific ones. UBI is just the ultimate extension of that, with even less overhead because of the "universal" part. You don't have to decide who receives it (everyone), so there's also less fraud (all you can do is try to nab someone else's on top of yours).
In theory, sure. Put more load on the server so the client can be thinner.
In reality, what happens is they bloat up the client side with tons of useless javascript, so both the server and the client need more horsepower.
Depends on the scope... and all it takes is for one key group of people (*nix sysadmins, say) to refuse and stand firm on that refusal.
If your refusal to do knowledge transfer prevents someone from operating a system you maintain, then you are very bad at your job. If a bus hit me tomorrow, any of my coworkers could pick up the systems I maintain using the documentation. Worse case, if a bus took out the entire operations team, someone from outside of the company would be able to use the docs to come up to speed.
If you've left such sparse documentation that no one can figure out how to maintain your systems, the company is better off without you.
And who controls the documentation? If the entire IT department simply locked away the documentation, they'd be SOL.
11a came out at the same time as 11b.
Wouldn't people just cam the movie with their phones that they're allowed to have out in the theater? Can't wait to see the MPAA try to sue a 15 year old for $50,000,000.
Now if only Firefox wouldn't "helpfully" reopen a 200-tab session on me. Chrome seems to always ask to restore regardless of how the browser exited, while Firefox just feels like opening it after a crash (which for me is usually a shutdown). There's also the fact that I had to install the dev version so I could get 64-bit because the 32-bit version would start to run out of RAM, become flaky as hell, then eventually crash.
99% of USB devices work with completely generic drivers. The whole "I need a vendor-specific driver for a device that uses completely standard protocols" is mostly a Windows-only thing. Plus there's USB passthrough for virtualization anyway, so worst case you can jus fire up a Windows VM.
I wouldn't be surprised if Apple's margins are so high that they only need one or two successful products to stay afloat to begin with. Even if a couple of their products turn out to be subpar, iPhones will always sell, not to mention Macs are snapped up like hotcakes for a variety of reasons.
everyone will hit me with the malware issue ... so let's image that they clean that up
then what's the excuse?
Let's cross that bridge when we come to it. Which is a very short bridge, since many sites aren't responsible with the amount and/or placement of ads (see: Wikia).
But the infringement would be on the user, not Brave.
I just love how Steam tries so hard to use their "mobile authenticator" thing, when all that accomplishes is giving someone who exploits your phone access to the Steam credentials, steam guard auth, and recovery email all in one go. At least with the Blizzard authenticator app, it didn't hold any account credentials, and you could buy hardware ones too.
On top of that, even if you had 500-factor authentication, it wouldn't stop some luser from getting phished, since they'd just put their 500 authentication details into the fake page.
I think this is actually a good thing. It's much better (and less damaging) to put power in the hands of end-users, rather than in a central moderation authority. Ignoring a viewpoint is a much better idea than censoring it from everyone. The problem with harassment is that one man's disagreement is another man's harassment, so rather than have moderators try to decide if something is over the line or not, just let people decide for themselves. Yes, people sticking their fingers in their ears when someone disagrees is bad, but calling for censorship is even worse.
Easy enough, just have the device identify as both a flash drive AND a keyboard. Keyboard presses Win-R and types the path to the malicious file on the drive.
The problem is that many devices show up as both a keyboard and a mouse, and possibly other devices as well. Devices with macro support tend to show up as both so they can have macros for both keyboard and mouse actions. Wireless keyboard/mouse dongles usually show up as both even if you only have one type of device paired to them. I've even had a webcam with some buttons on it which showed up as a keyboard. Some devices might even show up as more than one of each to get around limitations.
Well, he wasn't entirely wrong. When the iPhone first came out, it wasn't that great for productivity. Sites weren't mobile-friendly, it only had shitty EDGE cellular internet, didn't have (official) third party app support. Back then, you had to jailbreak it for the thing to be usable.
I actually have no problem with long copyright terms for actively used IP e.g. Mickey Mouse, but anything not actively used should become public domain very fast (especially abandonware).
I'd have a good deal of sympathy for them if they were small artists struggling to make a living, where piracy might literally be starving them. But instead, these are huge artists who make shitloads of money despite this piracy they're complaining about. It would be like Bill Gates complaining that a poor person slipped onto a bus without paying. Move over global warming, MPAA/RIAA crying is the leading cause of rising sea levels.
1. Spanish class gets a reputation as being the "easy" second language class.
2. Idiots pour into Spanish class because of #1.
3. #1 becomes a self-fulfilling prophecy as the class has to be slowed down significantly for them.
1. Install debian
2. apt-get install sysvinit-core
As I understand it, WPA wouldn't allow clients to decode other clients' packets, even if they know the key for initially connecting. Thus, you could just designate a password (even "password") for open networks to give people encryption yet still be open. In the meantime, you could just name your network PASSWORD_IS_xyz.
I don't think it's a huge burden. First-time customers would have to put in the password, but it's not like they're going to say "oh, you're making me put in a password for the wifi? I'll go eat somewhere else". Non-first-timers would already have the password saved.