Net savings of what, one keypress? It's rare for me to issue more than one or two git commands without issuing a non-git command. Unless the intention is to have a seperate shell up that you switch to whenever you need to do get stuff, maybe?
I tried to install it and verify for myself, but it required a newer version of Ruby than is available on my distribution. (Thanks, Canonical.)
...don't give two shits about us or the company they work for for credit card security.
Signature vs PIN: The thing you know.
Try signing with a line or an X sometime. Try writing expletives into the signature pad. Try writing "SEE ID" in the signature area of your card with a sharpie. The cashier that will notice and/or comment on this is far or few in between. What difference does it make to them if you're committing fraud? None. They still get paid. They (probably) won't be fired. The pin is marginally more secure, if only because it has a computer actually enforcing it, rather than a minimum wage cashier who can't be bothered to check.
MagStripe vs Chip: The thing you have.
The important part of the "Chip and Pin" system is more the "Chip" part than the "Pin" part. It's meant to make the cards far more difficult to duplicate. Right now, it's trivial to duplicate a magstripe. A few hundred bucks worth of equipment and a strategically placed skimmer and you can have your own private criminal enterprise. As I understand the weakness that's been described, it's a replay attack that only works once. (This may be incorrect. It's just what I remember.) That's a damn sight better than the the mag stripe.
Is this some excuse for the banks to push more responsibility onto their consumers for their own data security? Yeah, it is. But I'll take the higher security.
I'm not too worried about having chunks go missing. The moon has enough gravity to hold itself in in a sphere-ish shape. The mines will collapse in on themselves long before a huge chunk goes missing. (Plus, if we have things that can do that kind of damage to the moon, damage to the moon will be the least of our worries.)
As for knocking it out of orbit, the moon weighs 7.35*10^22 kg. The largest nuclear weapon ever detonated, Tsar Bomba, had a yield of 2.1*10^17 J. So, uh, not too worried about it. We're a few orders of magnitude off on that.
There's some legitimate concern about scarring the face of the moon for future generations. Yes, the moon is really big and really far away such that you probably wouldn't notice even a very large mine with the naked eye, but telescopes are cheap and plentiful. Possibly something you could deal with by treaties limiting the size of mines to less than utterly huge? At least there are no indigenous people to worry about. (Or, as history has demonstrated, not worry about.)
From reading the article, it looks less like "getting a permission slip from NASA" and more like "agreeing to cooperate with NASA." This seems reasonable to me, for US companies. Obviously, if commercial space exploration takes off, we're going to need some international agreements in place.
This previous line was supposed to read "Like UTF-8 Support." in Unicode look-alike characters.
Incidentally, I don't think they need to throw out the new layout entirely. Just fix the things about it that are horribly broken. Like the huge swaths of empty space at the sides of the screen. Especially the right. Also the comment system.
Alas, I fear that it's only marginally less likely that Apple would build an Android phone than Slashdot is to address any of the community concerns about the layout.
... that's about the only nice thing I have to say about them.
It's been a good five years since I worked in computer repair, but at the time they are overpriced for their specs and incredibly difficult to repair. I don't know if this has changed, but a recent trip to a Sony store suggests to me that it hasn't.
Also, Sony's blunders with DRM and their ties to the content industry have not exactly helped their reputation with being trustworthy. (VAIO! Comes with rootkit already installed!)
Also, what is this beta shit? I can live with "Web 3.0: The war on saturation." But not all of us have 1920x1080 monitors sitting on our desks...
... Google promptly returned the thousand of D-Wave devices they bought in attempt to bolster their failing conventional infrastructure. A Google representitive stated that they are looking into legal proceedings, but wouldn't comment further. A Google employee who asked to remain anonymous was quoted as saying, "What can I say? We fell for their shtick hook, line and sinker. Now we're left to pick up the pieces after the biggest technology blunder in our company's history!"
Oh, wait. That didn't happen. What actually happened is that they found some extra money between the couch cushions and bought a shiny toy to play with. I bet it won't be the last time, either.
But I'm sure that gutting the corporate culture that gave us things like MotoBlur and setting a major Android manufacturer on a path to sell "almost but not quite Nexus" devices also plays a fairly large part in their greater strategy for Android.
The person who did this has gone a long way to ensure that @N has minimal resale value. If I was some company that was looking at @N for my online presence, would I want my online presence to be associated with this story in any way, shape or form? No. At least, not until the story dies down. And that could take a while, since people will happily drag it out again when someone sets up shop.
It could be for personal use, but that seems like a lot of trouble to go through for a personal account. Stranger things have happened, though.
The only place I've ever worked that had an "open office plan" was because the boss was a penny-pincher who had deemed cubicle walls to be an unnecessary expense. Our "desks" were mostly mismatched folding tables that he'd picked up from various places and all desks faced the wall so he could watch what you were doing. (Think "panopticon.")
Fortunately, I got out of there quick.
That's not to say *all* open office plans are a result of that, of course. But it has soured my opinion of the concept.
Yes. This is an excellent point. The Chinese brands are known for their superior reliability, high standards of quality control and strongly-enforced privacy policies, after all.
(The real point: Know what you're buying and how to secure it.)
Actually, XP x64 just used WS2K3 x64 drivers. So hardware you would find in and connected to servers and high-end workstations (network cards, RAID cards, office and enterprise grade printers and scanners, workstation video cards) tended to work just fine while consumer gear (cheap printers, scanners and multifunction devices, gaming video cards) tended to be quite hit-and-miss.
The situation improved when Microsoft started forcing hardware manufacturers to support 64-bit in order to get the "Made for Vista" branding, but only for devices where the driver interface didn't change significantly. I could install Vista x64 drivers for my scanner on XP x64 by modifying the INF file and forcing it to install. That wouldn't work so well for a video card.
I don't think anyone is saying that PS4/Xbox1 emulation will be easy. Just that it will be easier than PS3/XBox360 emulation.
Both generations will have a significant amount of hacking and reverse engineering involved and will be fraught with legal challenges. The current generation just has the advantage of being more or less based on hardware that's readily available at a reasonable price. The previous generation is not even remotely similar to anything you can buy easily or cheaply. (Other than the PS3 and XBox360, of course.)
I actually do own a pocket watch that belonged to my grandfather. I need to take it to a watchsmith, though, since the spring is going bad and it won't stay... er... charged for more than a few hours.
I guess the people who bought it realized that having a watch you have to charge every night isn't all that useful.
(Contrast with a regular watch which, at the very worst, you replace the battery twice a year. Or other smart watches that you can go a week between charging them.)
What they say: "This will reduce costs for most users! Only the top users will have to pay more."
What they mean: "We're going to keep our pricing structures exactly the same and continue increasing them by 10-20% every year. With usage caps, if you actually use the service for anything more than checking your email and updating facebook, you'll be assessed additional fees."
And if you think they're not all tooled up to implement caps already, I present you with this: https://pic.twitter.com/kbGNJiMIWU (To see if your area has that, sign into your Comcast account, click "My Account" and then "My Services." It's in the sidebar under "Equipment.")
I've always wanted a device that I could use to tell me how many miles my car has gone. Maybe even a way to track individual trips by resetting it. Perhaps, since it's tied to the car's computer system, it can also track fuel usage and display my average fuel economy since the last time I reset it.
Seriously, though. I propose that states that want to implement use tax just read the odometer. For people who do a lot of out-of-state driving, they can buy/lease/rent a widget that plugs into whatever (probably OBDII) and use that in lieu of the odometer reading.
Every OCZ drive I've ever bought has not functioned properly out of the box. One of them worked after a firmware upgrade (and has been working for several years.) The other never worked and I returned it to the vendor.
I've never had to upgrade the firmware on a hard drive before. The first one I wrote off as "It's a new product, there are some bugs." After the second one, I was done. If I bought a car and had to load a special utility and buy a special cable to flash the ECU before the car would run reliably, I wouldn't have bought the car in the first place.
I've used vBulletin for years. While it's never had a particularly stellar security record, it has only gone down hill since Internet Brands bought Jelsoft.
The only remotely secure way to run vBulletin these days is to stick it in its own php-fpm pool with its own user account and insure that all files are 440 and all directories are 550. The upload directories (customavatar, attachment, etc) need to be 770 and then be excluded from PHP execution in your httpd config. Deleting "install/" goes without saying. (And we have it behind a Basic Auth, just in case someone forgets.)
Even today, with that fairly verbose nginx config and a fully patched and up to date vBulletin, I still find delightful files in my upload directories like "r00t.php" and "shell.php".
Oh? You're on shared hosting? Good luck with that...
Oracle: "We're buying Sun. Next step is to dismantle (MySQL,) close (Solaris, Java,) dissolve (OpenOffice) and generally disrupt all of Sun's open source properties that we can."
Community: "What? You can't do that!"
Oracle: "Watch us!"
Community: "Well, we'll just fork it."
Oracle: "S---! The forks (MariaDB, Percona, OpenIndiana, LibreOffice) and their pre-existing competitors (Linux, FreeBSD, Dalvik) are getting more popular than our versions! READY THE FUD CANNONS!"
Slashdot Mirror
... five expansion slots to fit the fans, this time!
Many (most?) programmers are salaried and exempt from overtime. If you or someone else introduces a bug that stops production, you fix it.
If you can do it in your 40 hour work week, good for you.
If it takes two weeks of 12 hour, 7 day weeks to fix it, then it sucks to be you.
If it doesn't, I don't see how it saves much typing.
$ vim -p file1.c file2.c file3.c ./a.out
$ make
$
$ gitsh
@ add file1.c file2.c file3.c
@ commit -m 'some crap'
@ ^D
$ vim -p file1.c file2.c file3.c ./a.out
$ make
$
$ git add file1.c file2.c file3.c
$ git commit -m 'some crap'
Net savings of what, one keypress? It's rare for me to issue more than one or two git commands without issuing a non-git command. Unless the intention is to have a seperate shell up that you switch to whenever you need to do get stuff, maybe?
I tried to install it and verify for myself, but it required a newer version of Ruby than is available on my distribution. (Thanks, Canonical.)
...don't give two shits about us or the company they work for for credit card security.
Signature vs PIN: The thing you know.
Try signing with a line or an X sometime. Try writing expletives into the signature pad. Try writing "SEE ID" in the signature area of your card with a sharpie. The cashier that will notice and/or comment on this is far or few in between. What difference does it make to them if you're committing fraud? None. They still get paid. They (probably) won't be fired. The pin is marginally more secure, if only because it has a computer actually enforcing it, rather than a minimum wage cashier who can't be bothered to check.
MagStripe vs Chip: The thing you have.
The important part of the "Chip and Pin" system is more the "Chip" part than the "Pin" part. It's meant to make the cards far more difficult to duplicate. Right now, it's trivial to duplicate a magstripe. A few hundred bucks worth of equipment and a strategically placed skimmer and you can have your own private criminal enterprise. As I understand the weakness that's been described, it's a replay attack that only works once. (This may be incorrect. It's just what I remember.) That's a damn sight better than the the mag stripe.
Is this some excuse for the banks to push more responsibility onto their consumers for their own data security? Yeah, it is. But I'll take the higher security.
I'm not too worried about having chunks go missing. The moon has enough gravity to hold itself in in a sphere-ish shape. The mines will collapse in on themselves long before a huge chunk goes missing. (Plus, if we have things that can do that kind of damage to the moon, damage to the moon will be the least of our worries.)
As for knocking it out of orbit, the moon weighs 7.35*10^22 kg. The largest nuclear weapon ever detonated, Tsar Bomba, had a yield of 2.1*10^17 J. So, uh, not too worried about it. We're a few orders of magnitude off on that.
There's some legitimate concern about scarring the face of the moon for future generations. Yes, the moon is really big and really far away such that you probably wouldn't notice even a very large mine with the naked eye, but telescopes are cheap and plentiful. Possibly something you could deal with by treaties limiting the size of mines to less than utterly huge? At least there are no indigenous people to worry about. (Or, as history has demonstrated, not worry about.)
From reading the article, it looks less like "getting a permission slip from NASA" and more like "agreeing to cooperate with NASA." This seems reasonable to me, for US companies. Obviously, if commercial space exploration takes off, we're going to need some international agreements in place.
I mean, I've always fantasized about being able to run Windows applications on Windows!
---
.
---
This previous line was supposed to read "Like UTF-8 Support." in Unicode look-alike characters.
Incidentally, I don't think they need to throw out the new layout entirely. Just fix the things about it that are horribly broken. Like the huge swaths of empty space at the sides of the screen. Especially the right. Also the comment system.
Alas, I fear that it's only marginally less likely that Apple would build an Android phone than Slashdot is to address any of the community concerns about the layout.
... that's about the only nice thing I have to say about them.
It's been a good five years since I worked in computer repair, but at the time they are overpriced for their specs and incredibly difficult to repair. I don't know if this has changed, but a recent trip to a Sony store suggests to me that it hasn't.
Also, Sony's blunders with DRM and their ties to the content industry have not exactly helped their reputation with being trustworthy. (VAIO! Comes with rootkit already installed!)
Also, what is this beta shit? I can live with "Web 3.0: The war on saturation." But not all of us have 1920x1080 monitors sitting on our desks...
... Google promptly returned the thousand of D-Wave devices they bought in attempt to bolster their failing conventional infrastructure. A Google representitive stated that they are looking into legal proceedings, but wouldn't comment further. A Google employee who asked to remain anonymous was quoted as saying, "What can I say? We fell for their shtick hook, line and sinker. Now we're left to pick up the pieces after the biggest technology blunder in our company's history!"
Oh, wait. That didn't happen. What actually happened is that they found some extra money between the couch cushions and bought a shiny toy to play with. I bet it won't be the last time, either.
But I'm sure that gutting the corporate culture that gave us things like MotoBlur and setting a major Android manufacturer on a path to sell "almost but not quite Nexus" devices also plays a fairly large part in their greater strategy for Android.
The person who did this has gone a long way to ensure that @N has minimal resale value. If I was some company that was looking at @N for my online presence, would I want my online presence to be associated with this story in any way, shape or form? No. At least, not until the story dies down. And that could take a while, since people will happily drag it out again when someone sets up shop.
It could be for personal use, but that seems like a lot of trouble to go through for a personal account. Stranger things have happened, though.
The only place I've ever worked that had an "open office plan" was because the boss was a penny-pincher who had deemed cubicle walls to be an unnecessary expense. Our "desks" were mostly mismatched folding tables that he'd picked up from various places and all desks faced the wall so he could watch what you were doing. (Think "panopticon.")
Fortunately, I got out of there quick.
That's not to say *all* open office plans are a result of that, of course. But it has soured my opinion of the concept.
Create a password: password
Everyone is using "password." We need to stop that.
Create a password containing both letters and numbers: password1
Everyone is using "password1." We need to stop that.
Create a password containing numbers and both capital and lowercase letters: Password1
Everyone is using "Password1." We need to stop that.
Create a password containing numbers, both capital and lowercase letters and a special symbol: Password1!
And so it goes.
Yes. This is an excellent point. The Chinese brands are known for their superior reliability, high standards of quality control and strongly-enforced privacy policies, after all.
(The real point: Know what you're buying and how to secure it.)
Actually, XP x64 just used WS2K3 x64 drivers. So hardware you would find in and connected to servers and high-end workstations (network cards, RAID cards, office and enterprise grade printers and scanners, workstation video cards) tended to work just fine while consumer gear (cheap printers, scanners and multifunction devices, gaming video cards) tended to be quite hit-and-miss.
The situation improved when Microsoft started forcing hardware manufacturers to support 64-bit in order to get the "Made for Vista" branding, but only for devices where the driver interface didn't change significantly. I could install Vista x64 drivers for my scanner on XP x64 by modifying the INF file and forcing it to install. That wouldn't work so well for a video card.
I think some people here are missing the point.
I don't think anyone is saying that PS4/Xbox1 emulation will be easy. Just that it will be easier than PS3/XBox360 emulation.
Both generations will have a significant amount of hacking and reverse engineering involved and will be fraught with legal challenges. The current generation just has the advantage of being more or less based on hardware that's readily available at a reasonable price. The previous generation is not even remotely similar to anything you can buy easily or cheaply. (Other than the PS3 and XBox360, of course.)
And speed limits stop people from speeding.
(This is a post about enforcement. Laws that aren't be enforced may as well not exist.)
I actually do own a pocket watch that belonged to my grandfather. I need to take it to a watchsmith, though, since the spring is going bad and it won't stay... er... charged for more than a few hours.
Some things never change.
True. But I bet you never left your charger at home!
I guess the people who bought it realized that having a watch you have to charge every night isn't all that useful.
(Contrast with a regular watch which, at the very worst, you replace the battery twice a year. Or other smart watches that you can go a week between charging them.)
What they say: "This will reduce costs for most users! Only the top users will have to pay more."
What they mean: "We're going to keep our pricing structures exactly the same and continue increasing them by 10-20% every year. With usage caps, if you actually use the service for anything more than checking your email and updating facebook, you'll be assessed additional fees."
And if you think they're not all tooled up to implement caps already, I present you with this: https://pic.twitter.com/kbGNJiMIWU
(To see if your area has that, sign into your Comcast account, click "My Account" and then "My Services." It's in the sidebar under "Equipment.")
I've always wanted a device that I could use to tell me how many miles my car has gone. Maybe even a way to track individual trips by resetting it. Perhaps, since it's tied to the car's computer system, it can also track fuel usage and display my average fuel economy since the last time I reset it.
Seriously, though. I propose that states that want to implement use tax just read the odometer. For people who do a lot of out-of-state driving, they can buy/lease/rent a widget that plugs into whatever (probably OBDII) and use that in lieu of the odometer reading.
Every OCZ drive I've ever bought has not functioned properly out of the box. One of them worked after a firmware upgrade (and has been working for several years.) The other never worked and I returned it to the vendor.
I've never had to upgrade the firmware on a hard drive before. The first one I wrote off as "It's a new product, there are some bugs." After the second one, I was done. If I bought a car and had to load a special utility and buy a special cable to flash the ECU before the car would run reliably, I wouldn't have bought the car in the first place.
I've used vBulletin for years. While it's never had a particularly stellar security record, it has only gone down hill since Internet Brands bought Jelsoft.
The only remotely secure way to run vBulletin these days is to stick it in its own php-fpm pool with its own user account and insure that all files are 440 and all directories are 550. The upload directories (customavatar, attachment, etc) need to be 770 and then be excluded from PHP execution in your httpd config. Deleting "install/" goes without saying. (And we have it behind a Basic Auth, just in case someone forgets.)
Even today, with that fairly verbose nginx config and a fully patched and up to date vBulletin, I still find delightful files in my upload directories like "r00t.php" and "shell.php".
Oh? You're on shared hosting? Good luck with that...
Oracle: "We're buying Sun. Next step is to dismantle (MySQL,) close (Solaris, Java,) dissolve (OpenOffice) and generally disrupt all of Sun's open source properties that we can."
Community: "What? You can't do that!"
Oracle: "Watch us!"
Community: "Well, we'll just fork it."
Oracle: "S---! The forks (MariaDB, Percona, OpenIndiana, LibreOffice) and their pre-existing competitors (Linux, FreeBSD, Dalvik) are getting more popular than our versions! READY THE FUD CANNONS!"