This file Cysaja.asx was in the/www directory - it's probably accessable as 192.168.1.1/Cysaja.html. It looks like info you could get other places (except maybe for firmware compile time and that mysterious wl_packet_get at the end) - I wonder what it's purpose is and if this file is password-protected. This file wasn't in our non-radio linksys router.
Thanks for the tech details. Google's machine is, of course similar -- probing port 80 looking for served web pages, but it sounds like Jesse's is more aggressive - rather than crawling, I suspect it just brute-forced the IP range. Technically, both searches are equally invasive - they only get public information. Just because google webcrawls rather than scans doesn't mean that a non-connected page won't get scanned - if someone visits the "off-grid" page and then an on-grid page that happens to log its referrer-url, the log will get crawled by google. But, I see how it would be hard to convice a non-technical jury of that...
p.s. unless you use the telephone number strategy - just because I don't give out my home phone number doesn't mean that I won't get telemarketing calls...
Yeah, every third release is the way to go. My company uses 6.1, 7.1, and 8.0; my friend's company uses 6.0, 7.0, and 7.3. Every third release is the way to go:)
Ok, maybe not. You've got to look at the versions and see what the general consensus is (which is what I think umich probably did). Running an older version with updates is probably a good idea, unless you need the improved GUI of 8 & 9. I can't adopt 9.0 until WINE works with it again (we've got a legacy app we're too lazy to port!)
My thought exactly. How is this different than the university buying a google appliance and setting it up? (other than if a student does it, it's free and he learns something) The university of florida, NYU, Seattle U., and U. of Michigan have these.
John gilmore is suing for the right to travel anonymously(sp).
From the website: He does so "because he believes persons have a right to travel by air without the government requiring that they relinquish their anonymity. No security threat is as important as the threat to American society caused by erosion of the right to travel, the right to be free from unreasonable searches, and the right to exercise First Amendment rights anonymously."
Check out the FAQ's, which are well written and explain the other reasons - including being subject to secret laws - he is opposing this.
I'm not sure you can make such a strong statement about anything as messy as lunar orbits. In any case, even if you can, the result is a stable semimajor axis with constantly changing eccentricity, and sooner or later the eccentricity will rise far enough to bring the perilune into the surface. Time-reversing that orbit will get you back to the original and then off into another set of wanderings ending in a "thump". Lunar orbits intersect the surface at both ends, so to speak.
Dude, and I'm a space-guy, too! *Blush* I was thinking geosync around the earth because people aren't usualy at that altitude, but then thought that the moon would be more appealing.
Link whoring
on
Chicken Run
·
· Score: 2, Informative
Ok, try it. I'm guessing the least like place for a robbery would be about 6 miles under the ocean (near the Mariana Trench, but about 3/4 of a mile from the bottom). Now, remember, you can only rob people -- stealing stuff from buildings and vaults is called burglary. My next least-likely place would be in geostationary orbit around the moon. I'll pay your bail if you get caught.
Congrats. I too went on a mostly-water drink diet (carbonated - the seltzer water I drink has more CO2 than flavor!). I now treat soda like candy, which it is.
Just some interesting numbers: 10 mountain dews (non-diet) = 1650 calories = a good chunk of your 2500 recommended daily calories. That's about 3 pints of plain vanila ice cream, or 1 1/3 pints of chunky monkey!
Hmm... Eric vs. a sewing grandma. Their images are similar... hat, long curly black hair. But if you look carefully, there's a subtle difference in the shirts...
Ok, I'll just follow this piracy-calculation-argument through with physical property.
Q: Suppose you own a 13" Sony television set. While you're out, a thief breaks into your home and steals it. You file a police report, and the next week buy an identicle new TV. How much money has sony lost?
A: They have lost one television set that the theif would have bought from them if he hadn't stolen it.
Q: Suppose the exact same situation, but you also happen to have a massive plasma screen in the family room that was too bulky to fit in the thief's car, so it was not stolen. How much has sony lost?
A: They are out the price of the flat screen. It's what the thief really wanted, after all!
You're right about the patent thing. Ipix aparently has a patent that they are using on Quicktime QTVR and panotools. more info warning - these links seem a bit old; I wonder what the progress has been. These are pretty simple algorithms (not trivial to implement, though) and are exactly the type of patents I hate... argh...
I'll just second that "DC is dev friendly" comment. I was developing for the DC's VMU (a memory card with a screen, buttons, and 8-bit processor), and the head of developer sw support in the US contacted me (and others) to offer support. They set up a mailing list and got us answers (and sega demonstration code) quickly! They were working on getting us the full-blown dev kit, but said they were encumbered by 3rd-party IP it contained -- still, we got everything we needed to develop with, and some people came out with better games than the professionals.
I missed part of the article - the 10-digit part (ok, major part!). Still, cities are only going to get denser & you'll have to survey individual houses and apartments to get zip codes accurate to a square meter. And, unless you start with the 10-digit version (which means every address is surveyed), the length of your zip code will change as your area gets denser.
According to the article, each zip code will cover about 1 square km. This is almost useless in the world's densest cities. 30,000 - 80,000 people/km^2 is quite common - New york's lower east side had 170k/km^2 in 1905; Cairo peak at 109k/km^2, and Hong Kong had almost 2 million people per square kilometer*!!
Hopefully, the system will be divisional based on local population density -- like zip codes are now . But if it is, then it will be neither simple (no GPS/zip translation), or it will be of variable length, and/or it will change over time as areas get denser and need redivision (like phone area codes)
* ok, that was a special case of 50k people living in a 0.03km^2 walled city.
Actually, zip codes are still kinda new. They started when your dad was 20: July 1st, 1963, and not mandatory for 2nd & 3rd class mailers until 4 years later. So, it's been in use for only 40 of the post office's 228 years of existence.
Not to nitpick, but how could someone know something for "many a lifetime"? It's a cool idea, and I'd love to be able to implement it!
Imagine if all the major computer makers had come up with different kinds of floppy disk in the early 90's, all incompatible with each other? Sounds pretty idiotic in retrospect, right? As an owner of a EZ-Drive 135, a SyJet, and a 2.5" floppy drive, I can tell you that the early 90's did have lots of different incompatible floppies. Bernolulis, 2.8MB floppies, SuperDrives, Jaz, Zip, and PocketZip drives have all pretty much dried up. We just have to wait for the next shakeout in solid state media.
I can't agree on your points for FAT; it's terrible for small removable media! * It's simple, so there is no easy way to tell if the media has been corrupted when rudely removed. It has no journaling capability & little redundancy. It'll be unreliable until chkdsk'ed & I doubt any portable devices are going to implement chkdsk. * It's not appropriate for FLASH-based systems because it doesn't use a wear-evening algorithm. If you save lots of tiny files on it, you'll wear out the part of memory that holds the FAT and/or main directory, rendering the device useless. * Long file name support is a kludge. It works ok, but it's tricky to get right. Insert it in a non-long-filename aware OS and the long names can get zapped. (I helped a friend implement a FAT filesystem, so I've seen a bit of this)
I agree with two assertions - it's universal (partly because MS refused to support other file systems), and it's reasonably efficient... but there are better alternatives like JFFS... I just wish they were more widely adopted.
Pretty soon, the'll take the detector one step further -- rather than being hand-held, it will be integrated into the hand
Microsoft has taken this to the next level with ActiveDeath Technology.
Thanks for the tech details. Google's machine is, of course similar -- probing port 80 looking for served web pages, but it sounds like Jesse's is more aggressive - rather than crawling, I suspect it just brute-forced the IP range. Technically, both searches are equally invasive - they only get public information. Just because google webcrawls rather than scans doesn't mean that a non-connected page won't get scanned - if someone visits the "off-grid" page and then an on-grid page that happens to log its referrer-url, the log will get crawled by google. But, I see how it would be hard to convice a non-technical jury of that...
p.s. unless you use the telephone number strategy - just because I don't give out my home phone number doesn't mean that I won't get telemarketing calls...
Yeah, every third release is the way to go. My company uses 6.1, 7.1, and 8.0; my friend's company uses 6.0, 7.0, and 7.3. Every third release is the way to go :)
Ok, maybe not. You've got to look at the versions and see what the general consensus is (which is what I think umich probably did). Running an older version with updates is probably a good idea, unless you need the improved GUI of 8 & 9. I can't adopt 9.0 until WINE works with it again (we've got a legacy app we're too lazy to port!)
My thought exactly. How is this different than the university buying a google appliance and setting it up? (other than if a student does it, it's free and he learns something) The university of florida, NYU, Seattle U., and U. of Michigan have these.
John gilmore is suing for the right to travel anonymously(sp).
From the website:
He does so "because he believes persons have a right to travel by air without the government requiring that they relinquish their anonymity. No security threat is as important as the threat to American society caused by erosion of the right to travel, the right to be free from unreasonable searches, and the right to exercise First Amendment rights anonymously."
Check out the FAQ's, which are well written and explain the other reasons - including being subject to secret laws - he is opposing this.
Cool, thanks. I found this neat paragraph:
I'm not sure you can make such a strong statement about anything as messy as lunar orbits. In any case, even if you can, the result is a stable semimajor axis with constantly changing eccentricity, and sooner or later the eccentricity will rise far enough to bring the perilune into the surface. Time-reversing that orbit will get you back to the original and then off into another set of wanderings ending in a "thump". Lunar orbits intersect the surface at both ends, so to speak.
Dude, and I'm a space-guy, too! *Blush* I was thinking geosync around the earth because people aren't usualy at that altitude, but then thought that the moon would be more appealing.
mfg website (uses frames - scroll top frame down for selections)
bigger picture
specifications page
my sig:
Ok, try it. I'm guessing the least like place for a robbery would be about 6 miles under the ocean (near the Mariana Trench, but about 3/4 of a mile from the bottom). Now, remember, you can only rob people -- stealing stuff from buildings and vaults is called burglary. My next least-likely place would be in geostationary orbit around the moon. I'll pay your bail if you get caught.
Congrats. I too went on a mostly-water drink diet (carbonated - the seltzer water I drink has more CO2 than flavor!). I now treat soda like candy, which it is.
Just some interesting numbers: 10 mountain dews (non-diet) = 1650 calories = a good chunk of your 2500 recommended daily calories. That's about 3 pints of plain vanila ice cream, or 1 1/3 pints of chunky monkey!
They're talking about kinetic energy, not potential energy.
The failure rate of these drives isn't significantly higher in Tampa by any chance? They may be worth more broken than fixed!
Hmm... Eric vs. a sewing grandma. Their images are similar... hat, long curly black hair. But if you look carefully, there's a subtle difference in the shirts...
Ok, I'll just follow this piracy-calculation-argument through with physical property.
Q: Suppose you own a 13" Sony television set. While you're out, a thief breaks into your home and steals it. You file a police report, and the next week buy an identicle new TV. How much money has sony lost?
A: They have lost one television set that the theif would have bought from them if he hadn't stolen it.
Q: Suppose the exact same situation, but you also happen to have a massive plasma screen in the family room that was too bulky to fit in the thief's car, so it was not stolen. How much has sony lost?
A: They are out the price of the flat screen. It's what the thief really wanted, after all!
That's one way, but I think that instead of blocking the signal, you should ensure that it always has a strong signal.
You're right about the patent thing. Ipix aparently has a patent that they are using on Quicktime QTVR and panotools. more info warning - these links seem a bit old; I wonder what the progress has been. These are pretty simple algorithms (not trivial to implement, though) and are exactly the type of patents I hate... argh...
whoops - sorry, I misinterpreted your post. I was thinking "these processors" were the 970's, not the overclocked G4's... Thanks.
whoops - forgot to mention that I wasn't in any of their dev programs - I was just a hacker with a webpage that caught their eye.
good news: "The PowerPC 970 implements an Elastic I/O processor interface bus, which operates at a speed of up to 900 MHz and can keep the multiple execution units fed by up 6.4 GBps of data." That matches the latest QDR200 3GHz P4 for thouroughput - if latency is better, then it'll outperform the P4 in usable bus bandwidth.
I'll just second that "DC is dev friendly" comment. I was developing for the DC's VMU (a memory card with a screen, buttons, and 8-bit processor), and the head of developer sw support in the US contacted me (and others) to offer support. They set up a mailing list and got us answers (and sega demonstration code) quickly! They were working on getting us the full-blown dev kit, but said they were encumbered by 3rd-party IP it contained -- still, we got everything we needed to develop with, and some people came out with better games than the professionals.
I missed part of the article - the 10-digit part (ok, major part!). Still, cities are only going to get denser & you'll have to survey individual houses and apartments to get zip codes accurate to a square meter. And, unless you start with the 10-digit version (which means every address is surveyed), the length of your zip code will change as your area gets denser.
According to the article, each zip code will cover about 1 square km. This is almost useless
in the world's densest cities. 30,000 - 80,000 people/km^2 is quite common - New york's lower east side had 170k/km^2 in 1905; Cairo peak at 109k/km^2, and Hong Kong had almost 2 million people per square kilometer*!!
Hopefully, the system will be divisional based on local population density -- like zip codes are now . But if it is, then it will be neither simple (no GPS/zip translation), or it will be of variable length, and/or it will change over time as areas get denser and need redivision (like phone area codes)
* ok, that was a special case of 50k people living in a 0.03km^2 walled city.
Actually, zip codes are still kinda new. They started when your dad was 20: July 1st, 1963, and not mandatory for 2nd & 3rd class mailers until 4 years later. So, it's been in use for only 40 of the post office's 228 years of existence.
Not to nitpick, but how could someone know something for "many a lifetime"? It's a cool idea, and I'd love to be able to implement it!
I'll respond to both your posts:
Imagine if all the major computer makers had come up with different kinds of floppy disk in the early 90's, all incompatible with each other? Sounds pretty idiotic in retrospect, right?
As an owner of a EZ-Drive 135, a SyJet, and a 2.5" floppy drive, I can tell you that the early 90's did have lots of different incompatible floppies. Bernolulis, 2.8MB floppies, SuperDrives, Jaz, Zip, and PocketZip drives have all pretty much dried up. We just have to wait for the next shakeout in solid state media.
I can't agree on your points for FAT; it's terrible for small removable media!
* It's simple, so there is no easy way to tell if the media has been corrupted when rudely removed. It has no journaling capability & little redundancy. It'll be unreliable until chkdsk'ed & I doubt any portable devices are going to implement chkdsk.
* It's not appropriate for FLASH-based systems because it doesn't use a wear-evening algorithm. If you save lots of tiny files on it, you'll wear out the part of memory that holds the FAT and/or main directory, rendering the device useless.
* Long file name support is a kludge. It works ok, but it's tricky to get right. Insert it in a non-long-filename aware OS and the long names can get zapped. (I helped a friend implement a FAT filesystem, so I've seen a bit of this)
I agree with two assertions - it's universal (partly because MS refused to support other file systems), and it's reasonably efficient... but there are better alternatives like JFFS... I just wish they were more widely adopted.