I've actually found the opposite... I have two proximity cards in my wallet, one for my office carpark and one for my office door, and they interfere with each other if I keep them together in my wallet, meaning the signal from neither one gets through.
What I've found is that if I keep a later of aluminium (that's aluminum for all you americans out there), from the cover of an old floppy disk, it seems to keep them isolated enough that I can keep them both in the same wallet and just turn it over to present the other card to the sensor.
But without that layer of metal between them, neither card works reliably.
Re:Sorry to poop on your theroy but....
on
Space Lichens
·
· Score: 1
hehe.. now now, we wouldn't want to start a wild new trend on slashdot by having people actually RTFA:)
Re:Sorry to poop on your theroy but....
on
Space Lichens
·
· Score: 1
They said they exposed it to space for 2 weeks and it survived. They didn't say that it died after being exposed for two weeks. Very different things. Potentially, it could have survived for months or even years, but they stopped the experiment too early to be able to determine that.
As I know nobody will actually read the article, I'll summarise it here:
It won't be as close as it was in 2003, but it will be more visible to more of the earth's population
This is the closest it will be until 2018
Hubble will be snapping party photos of it for posterity's sake.
As is so often the case, the slashdot headline is wrong.
From the page:
Welcome to visitors from Slashdot. Please be aware that the Slashdot story is completely wrong. There is no proposal to have advertising on Wikipedia. There are numerous errors of fact on this page. (See below if you're interested.) --Jimbo Wales 19:12, 24 October 2005 (UTC)
P.S. I originally posted this as AC so as not to be seen to be hording karma, but then I realised it wouldn't be seen if I posted it that way, so here goes again.
(Wouldn't it be nice if you could EDIT your posts on slashdot)
Ours already has one.. although it's not RFID, it's just a magnet that activates a reed switch in the lock on the cat door, so any cat in the neighbourhood with a magnet on its collar could in theory get in, but it works pretty well.
I've seen several locks that address that exact issue. The 'normal' way to get in is to use the combination / RFID / swipe cards / whatever hi-tech system, but if that fails, there's a keyhole in the lock that can be used to manually override the lock with a key.
Also, in commercial buildings, it's quite common to have multiple entrances. Usually they will put electronic locks and magclamps on the 'public' entrances, and leave yale locks on the others, so that security guards are able to get in and override from the inside if the sensor on the main door fails.
Despite what other people will no doubt say about how they won't read resumes send in word format, I'ld wager than 90% of human-resources staff don't read or post on slashdot, and if their standard-image computer with standard corporate software can't open the resume, then it doesn't get opened.
Many companies even state that it MUST be in word format.
Why does this remind of the joke about what do you call 1000 dead lawyers dead at the bottom of a cliff.
/mumbles something about damn corporates that are so quick to sue/take legal action that they can't see that people actually WANT the service they didn't provide to begin with.
Wow. I didn't think I'ld laid any flamebait, yet you seem to have found a need to flame.
Today, in Auckland, we have had heavy rain, heavier rain, wind reaching record levels, lightning, power cuts resulting from said lightning, oh, and bright sunshine. And it's only 1.15pm so far.
In order to work around the problems, I shape my torrent to 1kbps upload, and leave it going like that. After a weeks, I had downloaded about 600mb, and uploaded about 4gb, so my sharing ratio was great, but I can't sustain that because it means within 2 weeks, my 10gb limit has been reached.
Australian ISPs have similar policies, but I can't speak for them directly.
The problem with the 'you share with me and I'll share with you' concept that bittorrent is based on is that it doesn't fit well with the commercial reality of ISP plans these days.
For example, here in New Zealand, the fastest speed you can get is 2mbps ADSL, and depending on the plan you choose, when you hit 10GB of traffic (that's traffic in both directions added together), you either start paying excessive data charges designed to be so high as to force you to stop, or your bandwidth is reduced to 64kbps.
The latter option is obviously the one that the huge majority choose, and to the uninitiated, 64kbps seems like not such a bad idea. The problem is that the ISP acheives 64kbps by heavily dropping packets, and that results in much much worse performance than you would have got with a dialup modem connection.
I, for example, would be happy to leave BT running 24/7, seeding files, but I simply can't afford to do that, because at 2mbps, I can chew up 10GB in just 11 hours (actually less, because you have to include transmitted traffic too), and unless I want to have unusable internet access for the remaining 30.5 days of the month, I have to strictly control the amount of traffic I transmit and receive.
In Netscape Navigator 1.0 through 4.0, the history.db file was just a Berkeley DBM file. You could trivially bind to it from Perl, and pull out the URLs and last-access time. In Mozilla, this has been replaced with a "Mork" database for which no tools exist.
Let me make it clear that McCusker is a complete barking lunatic. This is just about the stupidest file format I've ever seen.
* Two different numerical namespaces that overlap.
* It can't decide what kind of character-quoting syntax to use: Backslash? Hex encoding with dollar-sign?
* C++ line comments are allowed sometimes, but sometimes// is just a pair of characters in a URL.
* It goes to all this serious compression effort (two different string-interning hash tables) and then writes out Unicode strings without using UTF-8: writes out the unpacked wchar_t characters!
* Worse, it hex-encodes each wchar_t with a 3-byte encoding, meaning the file size will be 3x or 6x (depending on whether whchar_t is 2 bytes or 4 bytes.)
* It masquerades as a "textual" file format when in fact it's just another binary-blob file, except that it represents all its magic numbers in ASCII. It's not human-readable, it's not hand-editable, so the only benefit there is to the fact that it uses short lines and doesn't use binary characters is that it makes the file bigger. Oh wait, my mistake, that isn't actually a benefit at all.
Cisco switches let you set ports to only be able to communicate with what you designate to be the uplink port.. it's okay if everything fits neatly into one switch, but if you have two or more switches then you need to have them blocked from seeing each other's traffic at a layer 3 level (ie, put them all on different subnets).
Slashdot Mirror
unfortunity thate wuld meen evry artycle on slachdot wuld be marced as spam :)
This is the norm with many, many corporate mail systems, so I don't see how you can point at google and say this is a bad thing.
Heh.. I read that as "it's called a Dupe attack".
I've actually found the opposite... I have two proximity cards in my wallet, one for my office carpark and one for my office door, and they interfere with each other if I keep them together in my wallet, meaning the signal from neither one gets through.
What I've found is that if I keep a later of aluminium (that's aluminum for all you americans out there), from the cover of an old floppy disk, it seems to keep them isolated enough that I can keep them both in the same wallet and just turn it over to present the other card to the sensor.
But without that layer of metal between them, neither card works reliably.
hehe.. now now, we wouldn't want to start a wild new trend on slashdot by having people actually RTFA :)
They said they exposed it to space for 2 weeks and it survived. They didn't say that it died after being exposed for two weeks. Very different things. Potentially, it could have survived for months or even years, but they stopped the experiment too early to be able to determine that.
So yeah, it sucks for me too. I was just going on what the article said.
From the page:
Welcome to visitors from Slashdot. Please be aware that the Slashdot story is completely wrong. There is no proposal to have advertising on Wikipedia. There are numerous errors of fact on this page. (See below if you're interested.) --Jimbo Wales 19:12, 24 October 2005 (UTC)
P.S. I originally posted this as AC so as not to be seen to be hording karma, but then I realised it wouldn't be seen if I posted it that way, so here goes again.
(Wouldn't it be nice if you could EDIT your posts on slashdot)
They are obviously not aware of the Navy's latest plans to use high intensity soundwaves to destroy incoming torpedos
Ours already has one.. although it's not RFID, it's just a magnet that activates a reed switch in the lock on the cat door, so any cat in the neighbourhood with a magnet on its collar could in theory get in, but it works pretty well.
Also, in commercial buildings, it's quite common to have multiple entrances. Usually they will put electronic locks and magclamps on the 'public' entrances, and leave yale locks on the others, so that security guards are able to get in and override from the inside if the sensor on the main door fails.
Um.. you do realise that this guy doesn't exist, right ? It's just a bunch of cliches run one after the other brought to you by the RIAA.
Despite what other people will no doubt say about how they won't read resumes send in word format, I'ld wager than 90% of human-resources staff don't read or post on slashdot, and if their standard-image computer with standard corporate software can't open the resume, then it doesn't get opened.
Many companies even state that it MUST be in word format.
Here endeth lesson one of 'How management thinks'.
Argh.. just missed first post too.
Yup, and thanks to Telecom's monopoly on ADSL, we have absolutely no choice about it either.
Today, in Auckland, we have had heavy rain, heavier rain, wind reaching record levels, lightning, power cuts resulting from said lightning, oh, and bright sunshine. And it's only 1.15pm so far.
In order to work around the problems, I shape my torrent to 1kbps upload, and leave it going like that. After a weeks, I had downloaded about 600mb, and uploaded about 4gb, so my sharing ratio was great, but I can't sustain that because it means within 2 weeks, my 10gb limit has been reached.
Australian ISPs have similar policies, but I can't speak for them directly.
yes, you're quite right, but the more people that applies to, the less people there are out there seeding torrents.
For example, here in New Zealand, the fastest speed you can get is 2mbps ADSL, and depending on the plan you choose, when you hit 10GB of traffic (that's traffic in both directions added together), you either start paying excessive data charges designed to be so high as to force you to stop, or your bandwidth is reduced to 64kbps.
The latter option is obviously the one that the huge majority choose, and to the uninitiated, 64kbps seems like not such a bad idea. The problem is that the ISP acheives 64kbps by heavily dropping packets, and that results in much much worse performance than you would have got with a dialup modem connection.
I, for example, would be happy to leave BT running 24/7, seeding files, but I simply can't afford to do that, because at 2mbps, I can chew up 10GB in just 11 hours (actually less, because you have to include transmitted traffic too), and unless I want to have unusable internet access for the remaining 30.5 days of the month, I have to strictly control the amount of traffic I transmit and receive.
HahahahahahahahahahaahA
hahah
ahha
ahahahahahaha
ahhahaahaha
That's right up there with the starwars kid
Now THIS is funny - from the File::Monk man page:
THE UGLY TRUTH LAID BARE ^
Extracted from mork.pl
In Netscape Navigator 1.0 through 4.0, the history.db file was just a Berkeley DBM file. You could trivially bind to it from Perl, and pull out the URLs and last-access time. In Mozilla, this has been replaced with a "Mork" database for which no tools exist.
Let me make it clear that McCusker is a complete barking lunatic. This is just about the stupidest file format I've ever seen.
http://www.mozilla.org/mailnews/arch/mork/primer.
http://jwz.livejournal.com/312657.html
http://www.jwz.org/doc/mailsum.html
http://bugzilla.mozilla.org/show_bug.cgi?id=24143
In brief, let's count its sins:
* Two different numerical namespaces that overlap.
* It can't decide what kind of character-quoting syntax to use: Backslash? Hex encoding with dollar-sign?
* C++ line comments are allowed sometimes, but sometimes
* It goes to all this serious compression effort (two different string-interning hash tables) and then writes out Unicode strings without using UTF-8: writes out the unpacked wchar_t characters!
* Worse, it hex-encodes each wchar_t with a 3-byte encoding, meaning the file size will be 3x or 6x (depending on whether whchar_t is 2 bytes or 4 bytes.)
* It masquerades as a "textual" file format when in fact it's just another binary-blob file, except that it represents all its magic numbers in ASCII. It's not human-readable, it's not hand-editable, so the only benefit there is to the fact that it uses short lines and doesn't use binary characters is that it makes the file bigger. Oh wait, my mistake, that isn't actually a benefit at all.
Pure comedy.
The 68K became very popular with appliance manufacturers. My parent's washing machine has a 68K in it for example.
Cisco switches let you set ports to only be able to communicate with what you designate to be the uplink port.. it's okay if everything fits neatly into one switch, but if you have two or more switches then you need to have them blocked from seeing each other's traffic at a layer 3 level (ie, put them all on different subnets).