I've never understood why passwords can't be sentences, like "I'm going to take my dog, Spot, to the park today."
They can be, but it would be incredibly stupid to use something like that. A dictionary attack would crack that password in seconds.
Fission only at places where you can cool them, and preferable the road infrastructure is good to get fuel to them and waste away.
It's cute that you think waste has to be hauled away and stored, instead of reprocessed into more fuel.
Missing option: The planet of another star
Oh, I hate blue LEDs. When they first came out I thought they were so awesome, then I mistakenly bought an alarmclock that had a blue display. Two layers of automotive window tint later and I still couldn't stand it, had to switch back to red. The blue one now lives out in the tool shed so that its radio can be used while doing yard work.
I have an access point in the bedroom with some obnoxiously bright blue LEDs. They're bright enough that you can almost read by the light it throws off. To make things even more obnoxious, the WiFi indicator blinks constantly once it's fully up and running.
Fortunately, all of that is fixed with a strip of electrician's tape. It doesn't even look too out-of-place. Tape wouldn't work too well for a clock (my Moto X is my alarm clock), but it'll tame blue LEDs in most other devices.
WRT54G is well known for its stability and reliability.
I keep hearing that, but I've owned four of them and I kept having overheating problems or similar. I'd have to power cycle them once a week or more. The last one would shit itself when my lady fired up her Fujitsu T900 for no known reason.
What firmware were you using? I've been using a WRT54GL for somewhere around 10 years. I had OpenWRT on it for the first few years, and it mostly worked...had to power-cycle it every once in a while. I think it only started acting consistently weird when I started hammering it with BitTorrent traffic. I switched over to Tomato because I wanted easier-to-configure QoS, and it's been pretty smooth sailing ever since. It's currently using a Shibby build. The last time it was rebooted was when I was troubleshooting what turned out to be an outage in Cox's network.
All that said, I suspect my 25/5 connection might be approaching the limit of what it can handle. I've augmented my network with a D-Link DAP-1522 to add 802.11a/n, but that's all it does. One box that could replace both and have enough processing grunt to keep up with a faster connection would be nice, and I'm inclined to stick with something that runs Tomato. I'm leaning toward the Asus RT-N66U, as that's gotten favorable comments here and elsewhere, but I've not yet pulled the trigger on one.
When arguing solar vs. nuclear, what you are really arguing about is where to put the reactor, and whether it's going to be a fusion reactor now, or a fission reactor now, with a fusion reactor replacing it later.
I'm disappointed that codes for new construction haven't started mandating the installation of solar.
So are the companies selling solar. Meanwhile, Chevron is disappointed about codes for new construction not mandating the installation of furnaces requiring heating oil.
As customization reaches lower and lower levels, it becomes increasingly difficult to meaningfully compromise it. Probably the only way to meaningfully compromise an FPGA is to autodetect an internet connectin, and stream out to it everything you receive, possibly only on receiving a particular activation signal.
The "FP" in "FPGA" stands for "Field Programmable"; it's possible to compromise in the field, in a rather meaningful way.
IIRC, AOL didn't offer actual internet access until pretty late in the game.
Today's date is Tue Sep 7644 07:32:08 PDT 1993
That's easy!
Start with a computer that doesn't need tweaks/updates from time to time, and then add video conferencing software that allows you to not upgrade it in order to support new platforms because the basic protocol never changes, but is already ubiquitous on every platform someone might want to use, and get it all from a vendor who has no monetary interest in forced updates!
An elephant is a mouse with constantly changing government regulation.
The primary reason for traffic slowdowns on these highways was rear-end collisions blocking traffic.
You've apparently never driven on U.S. 101 in the SF Bay Area; the primary reasons for traffic slowdowns are:
(1) Auuuuuuuugh! There's a huge ball of light up in the sky! We fears it, my precious!
(2) Look! An accident! Is there blood? Hey, Bill, can you see any blood?!?!
(3) I must get in the fast lane because it is the "fast" lane, even though I'm coming up on my exit!
(4) I must get from the fast lane all the way over to the exit lane, but it's OK if this takes forever, I was in the fast lane for 50 feet, dammit!
(5) Yes, I know it's after 3 PM and before 7PM! What do you mean, the lane to the left of mine is "The Car Pool Lane"? I'm driving slow in the middle lane; if you want to pass, you should get into the car pool lane and pass, then get back into this lane; you probably won't get a ticket anyway...
(6) Let me race up in this lane that I need to be out of before too long, rather than getting over now, even though I see barricades ahead, because I know some dumbass will let me in, right? Right? Hey, dumbass, I'm talking to you!
(7) I want to get on one of the bridges, but I don't want to wait behind all the people who also want to get on one of these bridges, so I'm going to block the next lane over until someone lets me in just to punish everyone else... if I have to wait, then everybody else damn well has to wait, too.
That probably should have been a countdown; fast lane discipline while car pool hours are in effect is probably the number one cause of traffic slowdowns, followed by "I'm too stupid to get over ahead of time", with "Auuuugh! Ball of fire!" in third place...
but this is the perfect example of american greed the most pure and wasteful greed i have ever seen.
If you'd taken ten seconds to click over to TFA, you would've learned it's in this Georgia, not this Georgia, you America-bashing twat.
The obvious solution? Just make a rule: "No Blasters."
As a general comment... it's pretty funny that this wouldn't be an issue, since they complied with the GPL as they were required to do, and published their sources.
Only the politics of Open Source is such that the projects that they published the changes for were not updated to include the changes, because they felt that it was not their responsibility to update their projects to include someone else's changes to their projects. They felt, instead, that it was the responsibility of the people making the changes to join their projects, and then make the changes with the editorial oversight of the community.
This is somewhat ironic, since they wouldn't have published the sources in the first place, if it hadn't been for the license.
So it's interesting to me that you can more or less not comply with the license by complying with it, and that the license is only effective for however long your product and company are around, and, if not picked up by the community to be carried forward, get lost after a short period of time, even if the company continues to exist.
I guess I wonder if it's legal to sell remaindered product (or used product) without offering the sources, per the terms of the license, or if, after that period of time, the products become illegal to transfer the binary licenses, since the originators are no longer around, and you cant appeal to them in order to get around your personal obligation, as the seller/reseller, to make the sources available any more (but you, as the middleman, failed to take advantage of the offer while it was possible to do so).
Probably, projects need to be a little less pissy about integrating third party changes, fixes, and extensions back into their main line.
I've noticed several design suggestions in your code.
