I remember having a Linksys WRT54G with a legitimate hardware issue years ago
Okay, I bought the story at Linksys but lost it at WRT54G. Though I suppose Cisco could have botched the newer hardware revisions;)
Our WRT54G is about... 9 years old. Still runs as our primary router with nary a hiccup. I managed to get a hold of 3 WRT600Ns as well -- the one that I've actually put dd-wrt on and put into service (with the intent of expanding our wifi coverage to the basement) can't actually hold a decent connection speed (speed from wireless device to router is fine, speed from router to WAN is fine as evidenced by an Ethernet-connected PC, speed from wireless router to WAN is abysmal...)
Personally, I run a hybrid approach: I have 2x1TB spinny disk drives mirrored, and an 80GB SSD (soon to be 240GB SSD, hurray for Black Friday deals from newegg) for anything that needs to be fast.
My phone (a Samsung Vibrant, or Galaxy S1 if you will) charges from empty to full on 2 hours.
Doubling the charge time for double the capacity doesn't seem like a problem to me, since it usually charges overnight -- and it still leaves the option of a half charge in the same amount of time for the same amount of battery life I have now.
Of course, I sometimes carry one of these around, but that's mainly because tethering is a huge battery drain. Oh, and that+the phone easily fit in one pocket, with the Nexus 7 that is using the phone-provided wifi in the other.
Before 9.2, I did this (for timestamp ranges only) using Jeff Davis's Temporal Extensions for PostgreSQL, which I've submitted a few patches to.
Which really is the direct predecessor of 9.2's Range Type support (from the same developer, too.)
Heh, I should have guessed.
It was a few years ago, but we actually tossed around some ideas on a standard format for applying the range concepts to types besides timestamps. One of the issues then was that a small handful of built-in types have a notion of infinity/-infinity, but some (e.g. ints) do not -- yet ranges really need to support the notion, even a range of ints. It looks like the 9.2 implementation uses its own definition for -infinity/+infinity unrelated to the type in question, which thinking about it now might not have been the best decision (at least, without the ability to define that [,y] and [-infinity,y] are synonymous) since -infinity (as defined by range types) is less than all other values including -infinity (as defined by the contained type).
Optimization of a constraint involving date ranges is a bit more difficult than you might think, and having it as one unified type makes queries a lot cleaner and indexes a lot more efficient (if done as GiST indexes anyways)
Old: WHERE (a.starttime BETWEEN b.starttime AND b.endtime OR b.starttime BETWEEN a.starttime AND a.endtime) New: WHERE a.timerange @@ b.timerange
The speedup when you're doing things like trying to find overlaps between two lists of tens of thousands of ranges each is phenomenal.
Before 9.2, I did this (for timestamp ranges only) using Jeff Davis's Temporal Extensions for PostgreSQL, which I've submitted a few patches to.
The better designed systems use a one-way hash of the answer. The support guy types the answer in and it's hashed and compared. Other systems use a mix of reversible and hashed answers. It can be done securely.
Until your security answer is something that can be spelled and/or punctuated a multitude of different ways and you're answering it verbally (i.e. to authenticate yourself over the phone). "Grey" and "Gray" are going to hash differently, and to say nothing about the multitude of ways of spelling various names. ("Is it O'mally or O'malley or o'Malley or...")
You can't count on the support type spelling it the exact way you do.
And you definitely can't count on the back end to be storing it with any sort of security at all, so my original point still stands.
Yup. I had an embarassing phone conversation with my state's tax department because a year earlier I set the secret question to "What is the password?" and a year later I had naturally forgotten the answer.
This is a bad idea, since security questions are probably stored unencrypted or at least using a reversible cipher -- the people on the other end of support need to be able to compare your answer, and there needs to be some leeway especially with spoken answers and spelling variations.
Unless, of course, your answer is an entirely different password...
Blizzard doesn't make a point of banning Linux users. The same source claims that there was an incident a few years ago where they inadvertently banned everyone using Cedega to play WoW, but when Cedega contacted them they determined the bans were false positives and not only lifted them but credited them with 20 days of game time.
I've read that Maptools (an open-source virtual tabletop for RPGs/etc.) currently is non-functional under Java 7, presumably due to an incompatible library.
However, the way some things are headed, why have any hardware at all? The only hardware you need is a screen to display the content/produce the sound which has been generated in the cloud...
(Which obviously proves satellites cause sea level rise. )
Well, there is one particular satellite that has been well known to cause sea levels to rise quite significantly, so I think you might be on to something here...
At least some of the MCSE-related exams do as well, though they're adaptive in a different manner -- if you miss a question on one subject area, it asks more (harder) questions on that subject to determine if it was just a tiny mistake or if your knowledge on that subject is actually lacking. The drawback to the format is you can't go back and revise your answers before time is up since, if you could, you could pay close attention to the questions being asked and go "Oh, I must have picked the wrong answer to this one, let's try this other answer."
The net result is a much shorter test than when I took the NT Server 4.0 exam (70-067) way back when (a few months before they changed to the adaptive format.)
(Disclaimer: I never actually did anything with my (now defunct) certification, I just had a high-school level class (as a pilot program) that actually taught it and included a trip to take the actual test.)
...kind of the same reasoning they use to justify high ETF's that still cost over $100 one month before the contract ends.
T-Mobile pro-rates ETFs. My wife and I are changing plans with them in a couple of weeks to save $50/mo, but it'll be costing us $50 per line in ETFs on the current plan (presumably because the new plan is unsubsidized and the existing one isn't). The reason we're waiting two weeks is because we're right on the cut from when their ETF goes from $100/line to $50/line.
I believe there was a class-action lawsuit against some other carriers (Verizon I think?) about ETFs that basically forced them to pro-rate ETFs as well, so I don't think this is exclusive to our carrier.
I'd really like to know what kind of information you have that still needs to be a secret in the year 2111 when we'll all be driving fusion powered flying time traveling cars and vacationing in hotels on the Moon and Mars and carrying petabyes of data on our iMicrosoftPods with end-to-end DRM that terminates in chip implanted in our brains.
Slashdot Mirror
Okay, I bought the story at Linksys but lost it at WRT54G. Though I suppose Cisco could have botched the newer hardware revisions ;)
Our WRT54G is about... 9 years old. Still runs as our primary router with nary a hiccup. I managed to get a hold of 3 WRT600Ns as well -- the one that I've actually put dd-wrt on and put into service (with the intent of expanding our wifi coverage to the basement) can't actually hold a decent connection speed (speed from wireless device to router is fine, speed from router to WAN is fine as evidenced by an Ethernet-connected PC, speed from wireless router to WAN is abysmal...)
Personally, I run a hybrid approach: I have 2x1TB spinny disk drives mirrored, and an 80GB SSD (soon to be 240GB SSD, hurray for Black Friday deals from newegg) for anything that needs to be fast.
In my experience, they are one and the same.
That's part of EVE's lore, actually, from the few months I tried it.
Were you two saying something? I was suffering from some, umm, what's the word? Let's make one up. Distractions. Yeah, that's it. Oooh shiny!
My phone (a Samsung Vibrant, or Galaxy S1 if you will) charges from empty to full on 2 hours.
Doubling the charge time for double the capacity doesn't seem like a problem to me, since it usually charges overnight -- and it still leaves the option of a half charge in the same amount of time for the same amount of battery life I have now.
Of course, I sometimes carry one of these around, but that's mainly because tethering is a huge battery drain. Oh, and that+the phone easily fit in one pocket, with the Nexus 7 that is using the phone-provided wifi in the other.
Clearly someone just needs to install FreeBSD on their 3D-printed toaster.
Heh, I should have guessed.
It was a few years ago, but we actually tossed around some ideas on a standard format for applying the range concepts to types besides timestamps. One of the issues then was that a small handful of built-in types have a notion of infinity/-infinity, but some (e.g. ints) do not -- yet ranges really need to support the notion, even a range of ints. It looks like the 9.2 implementation uses its own definition for -infinity/+infinity unrelated to the type in question, which thinking about it now might not have been the best decision (at least, without the ability to define that [,y] and [-infinity,y] are synonymous) since -infinity (as defined by range types) is less than all other values including -infinity (as defined by the contained type).
Optimization of a constraint involving date ranges is a bit more difficult than you might think, and having it as one unified type makes queries a lot cleaner and indexes a lot more efficient (if done as GiST indexes anyways)
Old: WHERE (a.starttime BETWEEN b.starttime AND b.endtime OR b.starttime BETWEEN a.starttime AND a.endtime)
New: WHERE a.timerange @@ b.timerange
The speedup when you're doing things like trying to find overlaps between two lists of tens of thousands of ranges each is phenomenal.
Before 9.2, I did this (for timestamp ranges only) using Jeff Davis's Temporal Extensions for PostgreSQL, which I've submitted a few patches to.
The better designed systems use a one-way hash of the answer. The support guy types the answer in and it's hashed and compared. Other systems use a mix of reversible and hashed answers. It can be done securely.
Until your security answer is something that can be spelled and/or punctuated a multitude of different ways and you're answering it verbally (i.e. to authenticate yourself over the phone). "Grey" and "Gray" are going to hash differently, and to say nothing about the multitude of ways of spelling various names. ("Is it O'mally or O'malley or o'Malley or...")
You can't count on the support type spelling it the exact way you do.
And you definitely can't count on the back end to be storing it with any sort of security at all, so my original point still stands.
This is a bad idea, since security questions are probably stored unencrypted or at least using a reversible cipher -- the people on the other end of support need to be able to compare your answer, and there needs to be some leeway especially with spoken answers and spelling variations.
Unless, of course, your answer is an entirely different password...
The lucrative in-app purchases in my metro app will involve throwing chairs.
It could be a parody of angry birds, where you throw chairs at Eric Schmidt, Larry Page and others.
The first expansion pack would be "Angry Ballmer: Developers Developers Developers".
I imagine the Pi is cheaper than the PIII after you factor in electricity costs...
I'm fairly certain these are hardware patents, but it's still just as ludicrous.
I don't think Higgs Bosons will catch the interest of the mass market.
A feral druid blog I follow had this to say about the banning:
(Full source here)
Blizzard doesn't make a point of banning Linux users. The same source claims that there was an incident a few years ago where they inadvertently banned everyone using Cedega to play WoW, but when Cedega contacted them they determined the bans were false positives and not only lifted them but credited them with 20 days of game time.
I've read that Maptools (an open-source virtual tabletop for RPGs/etc.) currently is non-functional under Java 7, presumably due to an incompatible library.
And perhaps a controller or other input device.
It's been done before...
Well, there is one particular satellite that has been well known to cause sea levels to rise quite significantly, so I think you might be on to something here...
At least some of the MCSE-related exams do as well, though they're adaptive in a different manner -- if you miss a question on one subject area, it asks more (harder) questions on that subject to determine if it was just a tiny mistake or if your knowledge on that subject is actually lacking. The drawback to the format is you can't go back and revise your answers before time is up since, if you could, you could pay close attention to the questions being asked and go "Oh, I must have picked the wrong answer to this one, let's try this other answer."
The net result is a much shorter test than when I took the NT Server 4.0 exam (70-067) way back when (a few months before they changed to the adaptive format.)
(Disclaimer: I never actually did anything with my (now defunct) certification, I just had a high-school level class (as a pilot program) that actually taught it and included a trip to take the actual test.)
http://www.gottabemobile.com/2012/03/27/android-or-condom-can-you-tell-which-is-a-phone/
Need I say more?
T-Mobile pro-rates ETFs. My wife and I are changing plans with them in a couple of weeks to save $50/mo, but it'll be costing us $50 per line in ETFs on the current plan (presumably because the new plan is unsubsidized and the existing one isn't). The reason we're waiting two weeks is because we're right on the cut from when their ETF goes from $100/line to $50/line.
I believe there was a class-action lawsuit against some other carriers (Verizon I think?) about ETFs that basically forced them to pro-rate ETFs as well, so I don't think this is exclusive to our carrier.
I tried to xerox on a cannon, but every time I fire up the machinery there's a loud bang.
The keys to the DRM, of course.
Knowing people's fanatical devotion to their model M keyboards, I think they'd rather take the bullet than let the keyboard do it :-p