Slashdot Mirror


User: gzuckier

gzuckier's activity in the archive.

Stories
0
Comments
3,846
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 3,846

  1. It is in their best interest to study us in detail. A space-faring civilization will, for purposes of survival, need to know the distribution and rate of development of other technological civilizations in order to get an idea of what their potential competition will be like. Raw data about the development of technological space faring species is the most valuable commodity in the universe.

    Daddy daddy, can you take us to Sol-3 so we can watch the monkeys again?

  2. When was the last time you shot a mouse in a mouse trap?

    One morning I shot a mouse in my pajamas

  3. If god really didn't want them to eat the fruit, he wouldn't have put that tree there, or at least would have made it somehow inaccessible. Punishing them for something that is essentially his fault is bad parenting.

    Or, it reflects a very strict, authoritarian, Old Testament way of thinking: "You do not do this thing that I tell you not to do, because I told you not to do it. You don't need any reason other than "I told you not to do that," and if you disobey, the punishment will be harsh. I am your Lord, and you will do as I command. Putting this temptation here is a test for you. Yielding to temptation is YOUR own personal failure and no other, and your punishment will be deserved."

    You darn kids, keep the Hell out of my apple orchard!!!

  4. Re: Good lord.... on iPhones and iPads Fail More Often Than Android Smartphones (softpedia.com) · · Score: 1

    Arguably, a device which allows itself to be crashed by a shitty app has failed, given that the existence of shitty apps is well known prior to the design phase of the device.

  5. Re: Good lord.... on iPhones and iPads Fail More Often Than Android Smartphones (softpedia.com) · · Score: 1

    That's OK the audience is equally clueless.

  6. Re: Good lord.... on iPhones and iPads Fail More Often Than Android Smartphones (softpedia.com) · · Score: 1

    Define definition.

  7. Re: BS on iPhones and iPads Fail More Often Than Android Smartphones (softpedia.com) · · Score: 3, Funny

    I recently purchased anot expensive phone from a well known brand, and after less than a day it stopped. I was told the "battery" was dead and it needed "recharging". This is unacceptable!

  8. Unless a platform is absolutely trouble free, quality of service is equally important.

  9. Re: It seems pretty clear who to blame on Tesla Owner in Autopilot Crash Won't Sue, But Car Insurer May (bloomberg.com) · · Score: 1

    Most supercars these days are equipped with a lot of driver assistance.

  10. Re: Splitting Musk's Pubic Hairs Pretty Fine There on Tesla Owner in Autopilot Crash Won't Sue, But Car Insurer May (bloomberg.com) · · Score: 1

    Pickled nits are an acquired taste.

  11. Re: Driver or Autopilot? on Tesla Owner in Autopilot Crash Won't Sue, But Car Insurer May (bloomberg.com) · · Score: 2

    Slightly reminiscent of those "sudden unintended acceleration" cases a while back, the audi ones, before drive by wire confused things. When the driver claims he was standing on the brake pedal but the car just leapt forward, and there is no way the engine could overpower the brake, and the gas pedal is bent from being stood on forcefully and the brake pedal isn't, you kind of have to entertain the possibility of driver error, no matter how certain the driver is of his innocence.
    in this case he's not disputing the possibility.

  12. Re: Driver or Autopilot? on Tesla Owner in Autopilot Crash Won't Sue, But Car Insurer May (bloomberg.com) · · Score: 1

    Ah, that's the key to the whole thing. He thought it was a break pedal, so he took a break from driving.

  13. Re: Driver or Autopilot? on Tesla Owner in Autopilot Crash Won't Sue, But Car Insurer May (bloomberg.com) · · Score: 1

    He doesn't have to sue, the insurance will cover him and they will sue. Not uncommon in car crashes.

  14. Terrible malfunction on Tesla Owner in Autopilot Crash Won't Sue, But Car Insurer May (bloomberg.com) · · Score: 1

    I simply stepped into the back seat to make myself a sandwich and, being overcome with fatigue, decided to take a nap...

  15. Re: Suicide bomber? on How The Navy Tried To Turn Sharks into Torpedos (undark.org) · · Score: 1

    Actually they started out with this shark bomber project, but it was considered too wasteful to train sharks and then blow them up on their first and only mission. So they started thinking "what if we could attach some other device to the sharks, maybe something like a really strong beam of light that can burn through hulls" and that lead to the invention of the laser shortly afterwards. So next time you see Jaws on DVD or blueray, remember you have sharks to thank for that.

    followed by the invention of the sharknado, and the rest is history

  16. Re:Obligatory Star Trek: TNG episode on Maybe There's No Life in Space Because We're Too Early · · Score: 1

    I think the first few seasons of Babylon 5 is a better analogy. In fact, the first few seasons of Babylon 5 is basically about the struggle between the older races and the younger races. It's possible that we are one of the "old ones" but an early stage. It's also possible that we are one of the younger races but, to the "old ones" we are nearly indistinguishable from ants (G'Kar gives a nice speech about this).

    On a more serious note, anyone who has sat and given some thought to what the TFS talks about has probably realized that we could be one of the earliest sentient races. The universe didn't start with the ingredients of life. It was brewed in stars and then spread by the exploding of stars and the re-coalescence of that material. That shortens the possible time frame for sentient life but, you also need a fairly quiescent part of the galaxy to give sentient life enough time to form. So, really, it's impractical for sentient life to arise until *all* nearby giant stars have gone supernova. Then you have the time it takes for new solar systems to form and stabilize, basic life to come into existence, mass extinctions, the possibility that lifeforms unsuitable for sentience will dominate a planet, etc, etc.

    It really takes an extraordinary amount of luck, over an extraordinary amount of time, for sentient life to form. And, as we've seen in the last century, it also takes a lot of luck for a technological society to not destroy itself.

    it seems at least reasonable that the same instinct to expand territory that drives us to expand into space is related to our instinct for aggression, which could make any sufficiently organized effort capable of deep space exploration/expansion impossible.

  17. Re:Ready to on US Air Force Declares F-35A Ready For Combat (defensenews.com) · · Score: 1

    Yes exactly, both the US and Russia are in the wrong on that sort of issue. The US doing it doesn't act as justification for anyone else to, quite the opposite, it highlights why no one should do it given how badly it fucked the region up. The US has been heavily criticised for it since it did so, and so should Russia be.

    yes

  18. Re:The mandate to change passwords every three mon on Frequent Password Changes Are the Enemy Of Security, FTC Technologist Says (arstechnica.com) · · Score: 1

    In the meantime no one can remember all these passwords and writes them down, making it super easy for anyone to know the persons password. I have worked at a college with a 90 day password change policy (and long complex passwords) and 75% of people had a sticky note somewhere around their desk with their current password on it because almost no one could remember them all. At the time I worked support and when going onsite I could easily have collected almost everyones passwords if I wanted. Most of IT didn't really remember the (multiple) sets of passwords either and so made use of password keychain programs to remember for them.

    I always found concepts like ITSM silly. Very little of it has any proof backing up their 'scores', but yet so much of the industry just accepts it.

    of course, there are simple workarounds for this, like using a simple and invariate code to write down your password, like writing down the character on the keyboard to the left of the real one for each character in your password on the post it, every time you change it

  19. Re:Social engineering story HERE on Frequent Password Changes Are the Enemy Of Security, FTC Technologist Says (arstechnica.com) · · Score: 1

    Stop listening to stupid fucking people, wow.

    The problem is that people who don't know much about a field like security can't identify those people. They don't know who to listen to.

    Scott Adams had it right when he created his character Mordac the Refuser, Preventer of Information Services..

  20. Re:Consider the Human Factor. on Frequent Password Changes Are the Enemy Of Security, FTC Technologist Says (arstechnica.com) · · Score: 1

    I encourage users to make up passwords based on some useless obsolete memory occupying a permanent place in their brains. I tell them to start with the name of their childhood dog, that's easy, but then add onto that the entire phone number for their best friend growing up.... the one you'd dial 12 times a day? that's 10 digits you can always recall, occupying some space in your head that you otherwise don't have any use for. Tag that onto your dog's name and you have a memorized 18-digit password. Your head is full of this stuff. An old gym locker combination. An weird nickname you used to call someone. The punchline from a comedy bit you heard when you were 11. There's actually a lot of defunct, untraceable fodder permanently stuck in your head you can use to construct a decent password that you couldn't forget it you wanted to.

    As a diehard geek, i use a combination of the base codes in my dna sequence and the digits in pi, both beginning at the place numbered by the integer representation of the datetime value at which i change the password, and include the symbol for my favorite element in the periodic table in Iroquois as the required nonalpha, nonnumeric character.

  21. Re:Social engineering story HERE on Frequent Password Changes Are the Enemy Of Security, FTC Technologist Says (arstechnica.com) · · Score: 1

    Let's say you change your password every day or every other day.

    BOOM. You just forgot your password. You now have to use their backup recover password features with another account.

    BOOM. linked.

    Stop listening to stupid fucking people, wow. There are not millions of deadly assault hackers armed with paramilitary live cd's out to get your fucking noodz. If you are using Windows they already got your shit. If you are using Apple, well ask Jennifer Lawrence. It *WAS* Tim Cook that leaked her noodz, not the patsy they blamed.

    Just use Linux or BSD and common sense your passwords. Your router is Linux if it is not Cisco so you are fine behind it. You don't have to be paranoid about your password unless it is password and you use Windows.

    Do you think the people running supercomputers change their passwords every 8 hours or something? This is a social engineering bait story. It attempts to mislead younger age people. Slashdot is some sort of mutant from what it used to be. I still haven't figured that out yet. Too many Microsoft stories and Pokemon GO's. Dice has lost their fucking Vulcan minds.

    in absolutely theoretical logical terms, if IT will reset your password and tell you what it is over the phone, based on stuff like your social security number and the date you were first hired, then it makes no damn difference how often you change your password or how secure it is; what you need to change periodically is your social security number and the date you were first hired.

  22. Every time I change my password, I have to change my dog's name, then he never realizes that I'm calling him.

  23. Re:Why should it have a remote? on TVs Are Still Too Complicated, and It's Not Your Fault (theverge.com) · · Score: 1

    Some people need a remote that they can throw in the dishwasher occasionally. Just saying.

    Anybody remember when Audio magazine reviewed the A11-1n-1sky audio system by Lirpa Laboratories of Bucharest, in the April 1983 issue? The system achieved a tiny shelf space footprint by moving many of the functions to the remote, which was the size of a small refrigerator and required a 12 volt car battery.

  24. Re:Why should it have a remote? on TVs Are Still Too Complicated, and It's Not Your Fault (theverge.com) · · Score: 1

    Yes, what a wonderful idea. I would love to put all my controls in the same device... oops hold on, I have a phone call... damn, where's the mute button? Oh, gotta launch that app... oh wait, I have to unlock the device first... ah crap! the battery is dying...

    That seems so much easier than just having a nice, dumb IR remote.

    An IR remote with tactile buttons, on the other hand, is a great design. It just works and needs line of sight to work which means that if I drop it into the couch or sit on it or look at it funny, it won't register... unlike an RF remote or app (looking at your Roku remote control)

    Plus, there is something to be said about tactile feedback... all this touch screen stuff is driving me crazy.

    like when your remote car unlock is an app in your phone, and the battery dies. ah, fun.

  25. Re:Why should it have a remote? on TVs Are Still Too Complicated, and It's Not Your Fault (theverge.com) · · Score: 1

    Why should each TV come with its own remote these days? The default should be that people use an app on their phone, with an option to buy your own universal remote. Instead we're wasting resources with the sale of every piece of living room electronics and middle-class houses get cluttered with remotes to different devices. It's inefficient.

    Of course, only a portion of the market would acknowledge that, so you would need a good marketing strategy and probably a phase-out period.

    as a connoisseur of obsolete but functional hardware that I get from Goodwill for $15, I attest that any manufacturer who builds equipment where vital functions are only accessible via the remote and not on the equipment itself, and furthermore only via proprietary codes which no "universal" remote can duplicate, needs to go out of business ASAP. Because that remote is going to vanish magically at some point and never reappear.