This is behavior I expect of rock-bottom-price Chromebook vendors, not a MacBook Pro. This is also why never Chromebooks are unappealing to me -- soldered RAM is one thing (SODIMMs are big), but they can't even make room for a NGFF 2242 SSD? Not interested. I'd rather Hackintosh an i3 Acer C720, at least I can put any drive I want in there.
I'd be more worried about the damn cube flying apart with these increasing speeds, not the CPU behind it. Overshoot a rotation and then start the next one before you correct it, and the cube will explode. Humans will not generate the force necessary to break a healthy cube, but even then they still sometimes come apart under these conditions (without breaking, the center pieces are spring-loaded).
Isn't it nice that banning books makes all the content in them inaccessible? There is no international network to carry such data from outside your borders, there is no way anyone could scan and burn existing copies, and no way anyone could buy a copy outside the country and ship it in or bring it home. Good thinking UK, I'm sure this will turn out really well!
The systems used in other countries might (or might not) work better for us, but the current system works just fine for the Power Elites. And that's why they aren't going to move to change it. That would be like expecting the cat to move just because you want to sit down too.
Microsoft can provide a perfectly secure platform for this guy's research cluster. Just keep it isolated from the world. I don't doubt that they can do this.
Then again, so can pretty much any other large service provider.
CF is fucking big. It's basically a tightly packed 44-pin PATA interface. You can ask until the universe achieves heat death, but you're not getting those back.
A headphone jack takes half the space of a USB port. The SD slot takes enough space for two SD slots. Getting rid of the audio jack would have 1/4 of the effect on the design. That's why it's still there... for now. I wouldn't be surprised if that goes away in the future, though.
VM? Why not Hackintosh? I mean, an Acer C720 Chromebook runs OS X just fine, provided it's the Core i3 and not the Celeron. (If it's the Celeron, you're limited to just Windows and Linux, like the Windows 10/Mint 18 dual boot I'm on right now). As long as you confirm ahead of time that a model is amenable to running OS X, finding a non-Apple laptop for the job just isn't that hard.
I can understand if this isn't something your employer wants to get involved with, but certainly it's an option for you personally.
I've picked up ordinary USB 2 SD readers for under $5. The right answer is to have a USB-C reader for the Mac and a USB-A reader for everything else, and forget intermediate layers of adapters.
If the FCC can regulate broadband, then they can regulate the devices getting attached to those connections to make sure they're not pulling shit like DDoS attacks. They can't tell you what the device is supposed to do, provided it isn't abusing the network itself, but certainly they should be able to prevent it from being a hazard to the world at large.
Until all the Android phones still in the wild (regardless of age) get patched for the Dirty COW vulnerability, how can anyone reasonably say they're "as secure as" anything other than Goatse guy's rectum?
The home of the person who decided to sell non-upgradeable devices and let them connect directly to the Internet is the only one I'm saying should be removed from it. Part 15 rules have their analogous components in most countries that regulate the RF spectrum (which is practically all of them), I just used the reference I know.
If you want to connect your multi-color LED Christmas lights to the Internet, then you should be required to administer such a setup just as much as you would any other computer you hook up. The same is true of your thermostat. If the vendor does not allow the devices to be adequately secured, then you have no business connecting them to anything more than your own local network, and if they manage to jump past firewalls and affect the world at large, you should get disconnected until you fix it, just like everyone else who is part of a botnet should be.
Whoever decided putting devices without sufficient resources to defend themselves, or be updated, directly onto the Internet was a good idea should have his professional certifications revoked and forbidden to administer anything more complicated than his own home network. And that home should probably be denied connectivity to the world.
The IoT is not necessarily a bad idea in concept, but it has been implemented exceptionally poorly, and those devices that cannot be updated need to be disconnected forever, or at least hidden on their own private networks. Vendors who cannot or will not patch their devices should be compelled to recall them, as violations of Part 15 rules against causing harmful interference.
Columbus re-discovering America is just an example of something that would have inevitably happened anyhow. It was previously "discovered" from the northwest tens of thousands of years earlier, and again by Polynesians sailing east, and by Vikings, and possibly by others as well. Columbus finding the place merely launched the Conquista. If it hadn't been him, it would have been someone else -- even if they had a more accurate concept of the size of the planet.
They found it because there is a whole bunch of Pluto-like objects out there, which is the whole reason it got demoted once this was recognized. Take ten thousand high-albedo objects (Pluto is at least partly high albedo), and say "point there, that's where we think it is" -- even if you really have no data, just a hunch -- and there's a good chance a dedicated observer will find something. They found Pluto not because it was Planet Nine, but because it was Dwarf Planet One of Thousands. While it was unlikely that they'd find that exact one, the chances of finding something substantially similar are much greater.
The "must accept" clause simply means that the device needs to deal with such interference without aggravating the problem. Not by emitting more noise of its own to try to shout over it. It doesn't mean it has to remain in perpetual BOHICA mode.
A device isn't allowed to shoot back under Part 15 rules. That doesn't mean it has to be the goatse guy.
It doesn't really matter who was firing the shot, so much as all those loaded, pwn3d weapons remaining in the wild that can be pressed into service again and again. This is not the first such event, it's at least the third. It won't be the last either, and the only way I can see to stop it is to permanently dismantle the IoT until it can be rebuilt from the ground up with security in mind. If security is too hard for the poor vendors and end users, then don't rebuild it. The health of the network as a whole is far more important than any single purpose for which it is used -- besides which, the devices can't be trusted to do their jobs anyhow once they've been pwn3d.
Make the vendors take them back in a recall -- could be a service recall in which they are made field-upgradable, or if they're hard-coded then they get the Galaxy Note 7 treatment as the hazards they are. Those who won't take them back should be cited under FCC Part 15 rules and have their certifications revoked and fines levied. It is easily provable that the devices are "causing harmful interference". It's time to get them off the network. Like yesterday.
Time to demand recalls of all affected devices as the hazards that they are. Those who wish to keep them become responsible for what they do -- if your IoT "cloud" shits all over the network again, you get switched off.
If the end users don't care (and may not be able to care if they can't patch the devices), then it has to go a step up the food chain. If the manufacturers won't comply, pull their FCC certifications.
You have a right to your own opinions, no matter how ill-founded they may be.
You do not have a right to your own "facts", especially when in a position of authority. Feels do not trump research, and medical practitioners should know better.
They simply refuse to perform any service for you until you enter into a contract with them. Bingo, they've got you locked in just like the original owner. As it stands, there are very limited options for third-party service for the things that really matter.
Slashdot Mirror
Hipsters don't keep iPhones in their pockets. Their skinny jeans are too tight, and they'd rather everyone see their shiny.
This is behavior I expect of rock-bottom-price Chromebook vendors, not a MacBook Pro. This is also why never Chromebooks are unappealing to me -- soldered RAM is one thing (SODIMMs are big), but they can't even make room for a NGFF 2242 SSD? Not interested. I'd rather Hackintosh an i3 Acer C720, at least I can put any drive I want in there.
I'd be more worried about the damn cube flying apart with these increasing speeds, not the CPU behind it. Overshoot a rotation and then start the next one before you correct it, and the cube will explode. Humans will not generate the force necessary to break a healthy cube, but even then they still sometimes come apart under these conditions (without breaking, the center pieces are spring-loaded).
Isn't it nice that banning books makes all the content in them inaccessible? There is no international network to carry such data from outside your borders, there is no way anyone could scan and burn existing copies, and no way anyone could buy a copy outside the country and ship it in or bring it home. Good thinking UK, I'm sure this will turn out really well!
The systems used in other countries might (or might not) work better for us, but the current system works just fine for the Power Elites. And that's why they aren't going to move to change it. That would be like expecting the cat to move just because you want to sit down too.
Microsoft can provide a perfectly secure platform for this guy's research cluster. Just keep it isolated from the world. I don't doubt that they can do this.
Then again, so can pretty much any other large service provider.
Sure they do. They're just not particularly useful in this case.
CF is fucking big. It's basically a tightly packed 44-pin PATA interface. You can ask until the universe achieves heat death, but you're not getting those back.
A headphone jack takes half the space of a USB port. The SD slot takes enough space for two SD slots. Getting rid of the audio jack would have 1/4 of the effect on the design. That's why it's still there... for now. I wouldn't be surprised if that goes away in the future, though.
VM? Why not Hackintosh? I mean, an Acer C720 Chromebook runs OS X just fine, provided it's the Core i3 and not the Celeron. (If it's the Celeron, you're limited to just Windows and Linux, like the Windows 10/Mint 18 dual boot I'm on right now). As long as you confirm ahead of time that a model is amenable to running OS X, finding a non-Apple laptop for the job just isn't that hard.
I can understand if this isn't something your employer wants to get involved with, but certainly it's an option for you personally.
I've picked up ordinary USB 2 SD readers for under $5. The right answer is to have a USB-C reader for the Mac and a USB-A reader for everything else, and forget intermediate layers of adapters.
If the FCC can regulate broadband, then they can regulate the devices getting attached to those connections to make sure they're not pulling shit like DDoS attacks. They can't tell you what the device is supposed to do, provided it isn't abusing the network itself, but certainly they should be able to prevent it from being a hazard to the world at large.
Until all the Android phones still in the wild (regardless of age) get patched for the Dirty COW vulnerability, how can anyone reasonably say they're "as secure as" anything other than Goatse guy's rectum?
The home of the person who decided to sell non-upgradeable devices and let them connect directly to the Internet is the only one I'm saying should be removed from it. Part 15 rules have their analogous components in most countries that regulate the RF spectrum (which is practically all of them), I just used the reference I know.
If you want to connect your multi-color LED Christmas lights to the Internet, then you should be required to administer such a setup just as much as you would any other computer you hook up. The same is true of your thermostat. If the vendor does not allow the devices to be adequately secured, then you have no business connecting them to anything more than your own local network, and if they manage to jump past firewalls and affect the world at large, you should get disconnected until you fix it, just like everyone else who is part of a botnet should be.
Whoever decided putting devices without sufficient resources to defend themselves, or be updated, directly onto the Internet was a good idea should have his professional certifications revoked and forbidden to administer anything more complicated than his own home network. And that home should probably be denied connectivity to the world.
The IoT is not necessarily a bad idea in concept, but it has been implemented exceptionally poorly, and those devices that cannot be updated need to be disconnected forever, or at least hidden on their own private networks. Vendors who cannot or will not patch their devices should be compelled to recall them, as violations of Part 15 rules against causing harmful interference.
Columbus re-discovering America is just an example of something that would have inevitably happened anyhow. It was previously "discovered" from the northwest tens of thousands of years earlier, and again by Polynesians sailing east, and by Vikings, and possibly by others as well. Columbus finding the place merely launched the Conquista. If it hadn't been him, it would have been someone else -- even if they had a more accurate concept of the size of the planet.
They found it because there is a whole bunch of Pluto-like objects out there, which is the whole reason it got demoted once this was recognized. Take ten thousand high-albedo objects (Pluto is at least partly high albedo), and say "point there, that's where we think it is" -- even if you really have no data, just a hunch -- and there's a good chance a dedicated observer will find something. They found Pluto not because it was Planet Nine, but because it was Dwarf Planet One of Thousands. While it was unlikely that they'd find that exact one, the chances of finding something substantially similar are much greater.
Pepper spray is classified as an offensive weapon in the UK. You can't carry it.
Privacy Badger will not be working with Pale Moon 27 because its underlying SDK is being removed from the code.
The "must accept" clause simply means that the device needs to deal with such interference without aggravating the problem. Not by emitting more noise of its own to try to shout over it. It doesn't mean it has to remain in perpetual BOHICA mode.
A device isn't allowed to shoot back under Part 15 rules. That doesn't mean it has to be the goatse guy.
It doesn't really matter who was firing the shot, so much as all those loaded, pwn3d weapons remaining in the wild that can be pressed into service again and again. This is not the first such event, it's at least the third. It won't be the last either, and the only way I can see to stop it is to permanently dismantle the IoT until it can be rebuilt from the ground up with security in mind. If security is too hard for the poor vendors and end users, then don't rebuild it. The health of the network as a whole is far more important than any single purpose for which it is used -- besides which, the devices can't be trusted to do their jobs anyhow once they've been pwn3d.
Make the vendors take them back in a recall -- could be a service recall in which they are made field-upgradable, or if they're hard-coded then they get the Galaxy Note 7 treatment as the hazards they are. Those who won't take them back should be cited under FCC Part 15 rules and have their certifications revoked and fines levied. It is easily provable that the devices are "causing harmful interference". It's time to get them off the network. Like yesterday.
Time to demand recalls of all affected devices as the hazards that they are. Those who wish to keep them become responsible for what they do -- if your IoT "cloud" shits all over the network again, you get switched off.
If the end users don't care (and may not be able to care if they can't patch the devices), then it has to go a step up the food chain. If the manufacturers won't comply, pull their FCC certifications.
You have a right to your own opinions, no matter how ill-founded they may be.
You do not have a right to your own "facts", especially when in a position of authority. Feels do not trump research, and medical practitioners should know better.
They simply refuse to perform any service for you until you enter into a contract with them. Bingo, they've got you locked in just like the original owner. As it stands, there are very limited options for third-party service for the things that really matter.
Oh it will install. But the network functionality that makes it worth running in the first place will be thoroughly broken.