It's a problem of legal liability - if you provide them a firewall, and something bad happens, then they can come back and sue you for not doing your job.
If you put the onus on them, then you are safe.
Much the same reason that it is very good to be certified by the Red Cross if you have to do CPR - it can protect you from being sued by the guy who's life you saved just because you broke his ribs doing CPR.
Point #9 - prevention of viruses and prevention of Microsoft Messanger pop-up spam.
Point #10: No, I'm not saying they have to run a virus scanner. I am saying that if they are infected, and if they refuse to correct the problem, you pull their connection.
Point #4: Physical ports - in other words, if a unit isn't signed up for access the port is dead.
Final point: I was making my points in a brief, straightforward fashion, so as to keep my message short and easily understood. OF COURSE when you present these points to the users, you tell them what's what and why it is in their own best interests to go along.
1) Don't put DSL to each unit - pull CAT-5 and run Ethernet. Your residents will have a much easier time getting hardware than with DSL, and your costs will be less. 2) Pull the wire to a common router closet. 3) One port per unit 4) Lock down the ports that aren't being used. 5) Use DHCP to assign addresses. 6) Set up your own caching server. I would recommend using Squid. 7) Force all outbound port 25 (SMTP) through your mail server. 8) Run a virus scanner on your mail server. Scan all incoming AND outgoing mail. 9) Don't route the Microsoft file sharing ports or Apple Rendezvous ports between units. 10) Insist customers keep their machines virus free. Disconnect any who don't IMMEDIATELY. 11) Write into your rental contracts that you ARE NOT RESPONSIBLE for maintaining your customer's machines or security - if they are scared let them run their own firewall. 12) Offer your own space, accessible to your users, with virus scanner updates, MS patches, and so on. Encourage them to use that to save bandwidth. 13) Routinely sniff around for WAPs. Handle them as you see fit - disconnect, or verify they are set up sanely. Don't ignore them.
Many will disagree with some of my points (esp. 7 and 9). Ask yourself this: do I enjoy being blacklisted for spamming?
I'm sorry, but I hold the copyright over my brain and the information therein, and your brain scanner is an unlawful circumvention device under the DMCA.
The fundimental problem with the floptical IMHO was that the interface was SCSI only. While that was fine by me (At the time I was running an Atari ST so SCSI was my native tongue) it meant the PC crowd (i.e. the bulk of the world) could not easily use them.
Had Insite made a floptical with a floppy interface (and special drivers to access the higher density mode) they might have been able to displace the floppy disk drives, and get enough volume to have brought the price down.
It's scary to think that I can get 5 times the storage on a USB keychain drive....
When do we start punching holes in them?
on
High Density CDs
·
· Score: 5, Funny
So, history repeats itself again - higher density on older media.
When do we start punching holes in them and flipping them over?
It used to be that advertising was about making people aware of your product/service. Ideally, you did so the the most focused manner possible - if you were a lawn care service you went to people with lawns, etc.
You also did things like list yourself in the telephone book.
That form of advertising is useful to both the advertiser and the viewer, and so will persist. That is what getting your web site listed in Google under the appropriate indexes does.
However, now-a-days advertising is about "RAM THIS DOWN HIS THROAT AND MAKE HIM WANT IT NO MATTER WHAT!" I've heard it said that, to a marketer, it is a failure if you go into a store and buy only what you went in to buy.
That sort of advertising is doomed, because it a) does not generate good, high quality leads, and b) it pisses people off. That which pisses people off gets ignored.
What you said in your first message was incorrect. I corrected you. I'm sorry if my way of correcting you offended you, but misquoting the laws as you did leads to other folks misunderstanding what is unlawful, which in turn causes folks like to be be harrassed while going about our lawful business.
she was walking all alone down the street in the alley her name was sally she never saw it when she was hit by space junk
in new york miami beach
heavy metal fell in cuba
angola saudi arabia
on xmas eve said norad
a soviet sputnik hit africa
india venezuela (in texas
kansas)
it's falling fast peru too
it keeps coming and now i'm mad about space junk i'm all burned out about space junk oooh walk & talk about space junk it smashed my baby's head and now my sally's dead
I thought it was impossible to write bugs in Java - nature's most perfect language! After all, all the Java bigo^H^H^H^Hzealot^H^H^H^H^H^Hexperts have always said that all software problems would vanish if we would just use their perfect language.
(/me removes tongue from cheek)
I just hope that the myriad and varied Java bigots out there will take this to heed: No language can prevent you from making mistakes.
(NOTE: I most emphatically do NOT assert that a language cannot make certain classes of errors more difficult to make!)
(NOTE 2: I also do not assert that all people who use Java, or promote the use of Java are bigots.)
There is no substitute for experience, careful design, and methodical testing.
The biggest problem with the idea of generic FPGA accelerators is sharing the resource in a multitasking environment.
Suppose you had a nice 10 million gate FPGA on your PCI bus. Now, if you program it to do one thing and one thing only, then there's no problem. So if that FPGA set up to be a hardware DiVX encoder and that's it, all is well.
But let's suppose that you fire up your video editor, and it wants the FPGA to be a DiVX encoder. Then you fire up SSH, and SSH wants the FPGA to be an encryption engine.
It is currently VERY hard to dynamically reprogram sections of an FPGA (some do support partial reprogramming while running, but not all). It is also very hard for the hardware compiler to merge tasks - you would have to re-generate the layout of the FPGA each time you added a function.
What we need is the equivilent of a malloc() call to allow a single large FPGA to be used by multiple applications at the same time (until you run out of gates).
Once that exists, then you will see vendors making generic FPGA accelerators.
Until then, FPGA boards will be the province of a very few people, and prices won't come down very much, I fear.
HE's not from the government-he's from MICROSOFT!
on
MIT Gnome Invasion
·
· Score: 1
Look out! He's not from the government, he's from MICROSOFT!
However, I would argue that comes about as a result of prohibiting the parties from using public property or public voting gear, but you are right, it is best to spell it out explicitly.
Of course, even spelling things out explicitly doesn't work - witness "... the right to keep and bear arms shall not be infringed."
Thank you for talking about BNTOA (Binding None Of The Above), a pet subject of mine.
You need to do one other thing, as well, IMHO: You need to recognize that the "primaries" are nothing of the sort - they are a wart on the side of the electoral process, completely outside the scope of the laws defining the system. They are purely a function of the political parties.
The best thing in the world would be to de-emphasise them, by:
1) not allowing the parties access to the voter rolls as maintained by the State - all they should be able to ask you is "Are you eligable to vote in this district?" not "What party are you registered with?" 2) not allowing the parties to use State property to conduct the primaries - let them find their own damn location to hold the polling and use their own damn equipment to tally the votes. This helps remind people of the unofficial status of the primaries, as well as (hopefully) forcing the two main parties to be at seperate locations, in order to facilitate point #3, which is: 3) If a party wishes to restrict access to its primary voting to party members, that's fine (after all, it IS a private function). However, do NOT allow the parties to prevent me from joining, just because I also joined the other party. If I wish to be BOTH a Rep and a Dem (and a Green and a Lib and a....) that is MY choice.
In the state where I live (Kansas), you are EITHER a Republican OR a Democrat OR an independant, but not more than one of the above. Thus, I cannot vote in both the Rep and Dem primaries - pick one and only one.
With my changes, I could be both a Rep and a Dem, and vote in both primaries, thus preventing the "pick the lesser of two evils" crap when the REAL election comes around - I would at least have a chance to get each party to field a reasonable candidate.
THEN, if the parties refuse to play ball, you can NOTA their sorry selves out of the running.
Thus, the parties won't run lame ass candidates (Like Bush AND Gore) because the matrix looks like this:
Both parties run poor candidates: NOTA wins, both parties have to run a second campain.
Party A runs a poor candidate, party B runs a good candidate - party B wins.
Both parties run good candidates - we ALL win!
Also, in a NOTA system the third parties are given more power - in the first election they can focus on tearing down the Rep/Dem candidtates, and NOT run their own guy.
NOTA wins.
Then the third parties blitz to adverties their guys, being on more even footing with the big boys.
Slashdot Mirror
It's a problem of legal liability - if you provide them a firewall, and something bad happens, then they can come back and sue you for not doing your job.
If you put the onus on them, then you are safe.
Much the same reason that it is very good to be certified by the Red Cross if you have to do CPR - it can protect you from being sued by the guy who's life you saved just because you broke his ribs doing CPR.
Point #9 - prevention of viruses and prevention of Microsoft Messanger pop-up spam.
Point #10: No, I'm not saying they have to run a virus scanner. I am saying that if they are infected, and if they refuse to correct the problem, you pull their connection.
Point #4: Physical ports - in other words, if a unit isn't signed up for access the port is dead.
Final point: I was making my points in a brief, straightforward fashion, so as to keep my message short and easily understood. OF COURSE when you present these points to the users, you tell them what's what and why it is in their own best interests to go along.
Here's my advice, for what it is worth:
1) Don't put DSL to each unit - pull CAT-5 and run Ethernet. Your residents will have a much easier time getting hardware than with DSL, and your costs will be less.
2) Pull the wire to a common router closet.
3) One port per unit
4) Lock down the ports that aren't being used.
5) Use DHCP to assign addresses.
6) Set up your own caching server. I would recommend using Squid.
7) Force all outbound port 25 (SMTP) through your mail server.
8) Run a virus scanner on your mail server. Scan all incoming AND outgoing mail.
9) Don't route the Microsoft file sharing ports or Apple Rendezvous ports between units.
10) Insist customers keep their machines virus free. Disconnect any who don't IMMEDIATELY.
11) Write into your rental contracts that you ARE NOT RESPONSIBLE for maintaining your customer's machines or security - if they are scared let them run their own firewall.
12) Offer your own space, accessible to your users, with virus scanner updates, MS patches, and so on. Encourage them to use that to save bandwidth.
13) Routinely sniff around for WAPs. Handle them as you see fit - disconnect, or verify they are set up sanely. Don't ignore them.
Many will disagree with some of my points (esp. 7 and 9). Ask yourself this: do I enjoy being blacklisted for spamming?
I'm sorry, but I hold the copyright over my brain and the information therein, and your brain scanner is an unlawful circumvention device under the DMCA.
My lawyers will be calling.
The only problem with ANY SCSI card was it was one more card to add to the system - which deterred many PC manufacturers from including it.
Remember them? I have some!
The fundimental problem with the floptical IMHO was that the interface was SCSI only. While that was fine by me (At the time I was running an Atari ST so SCSI was my native tongue) it meant the PC crowd (i.e. the bulk of the world) could not easily use them.
Had Insite made a floptical with a floppy interface (and special drivers to access the higher density mode) they might have been able to displace the floppy disk drives, and get enough volume to have brought the price down.
It's scary to think that I can get 5 times the storage on a USB keychain drive....
So, history repeats itself again - higher density on older media.
When do we start punching holes in them and flipping them over?
This looks like it requires Javascript to work.
Yet another reason why I normally have JS turned off, and turn it on ONLY at need.
I must point this out to my webmaster friends.
Is your site virtual hosted? If so, then you may be sharing a server with a porn site.
So, if IP address s.y.z.a serves both your site and www.pervertsinculverts.com, then you will be besmirched by them, since you share the same server.
It sucks, but then, all content filtering like this sucks.
Advertising as it is praticed today is doomed.
It used to be that advertising was about making people aware of your product/service. Ideally, you did so the the most focused manner possible - if you were a lawn care service you went to people with lawns, etc.
You also did things like list yourself in the telephone book.
That form of advertising is useful to both the advertiser and the viewer, and so will persist. That is what getting your web site listed in Google under the appropriate indexes does.
However, now-a-days advertising is about "RAM THIS DOWN HIS THROAT AND MAKE HIM WANT IT NO MATTER WHAT!" I've heard it said that, to a marketer, it is a failure if you go into a store and buy only what you went in to buy.
That sort of advertising is doomed, because it a) does not generate good, high quality leads, and b) it pisses people off. That which pisses people off gets ignored.
First answer: have you ever heard of a back up generator?
Second answer: So?
Replied to wrong story! Mod me down as offtopic....
Seriously, this could also be good if it helps people realize jail is bad! ("This 5u><0rz! I got gibbed again!")
Lastly, if you want to prevent escapes:
"This is your collar. That is the transmitter. Get too far from the transmitter, BOOM! Take hostages, BOOM! Damage transmitter, BOOM!"
Also, this might discourage people from wanting to get into prison ("DAMN! killed again! this 5U><0rz!")
What you said in your first message was incorrect. I corrected you. I'm sorry if my way of correcting you offended you, but misquoting the laws as you did leads to other folks misunderstanding what is unlawful, which in turn causes folks like to be be harrassed while going about our lawful business.
she was walking all alone
down the street in the alley
her name was sally
she never saw it
when she was hit by space junk
in new york miami beach
heavy metal fell in cuba
angola saudi arabia
on xmas eve said norad
a soviet sputnik hit africa
india venezuela (in texas
kansas)
it's falling fast peru too
it keeps coming
and now i'm mad about space junk
i'm all burned out about space junk
oooh walk & talk about space junk
it smashed my baby's head
and now my sally's dead
Devo, Space Junk.
BZZZT! WRONG. Sorry, but manufacturing and selling devices capable of intercepting cell phone conversations is exactly what we do all day.
It is not even unlawful for us to sell such a device to anybody.
It is unlawful for you to use such a device to intercept a telephone conversation without a court order, but that is YOUR responsiblilty, not ours.
Bugs in Java code? Inconceivable!
I thought it was impossible to write bugs in Java - nature's most perfect language! After all, all the Java bigo^H^H^H^Hzealot^H^H^H^H^H^Hexperts have always said that all software problems would vanish if we would just use their perfect language.
(/me removes tongue from cheek)
I just hope that the myriad and varied Java bigots out there will take this to heed: No language can prevent you from making mistakes.
(NOTE: I most emphatically do NOT assert that a language cannot make certain classes of errors more difficult to make!)
(NOTE 2: I also do not assert that all people who use Java, or promote the use of Java are bigots.)
There is no substitute for experience, careful design, and methodical testing.
Please add this number to all Do Not Call lists your company and your client maintain.
Many telemarketing companies maintain different DNCs for each customer - ask them to put you on ALL their lists at once.
The biggest problem with the idea of generic FPGA accelerators is sharing the resource in a multitasking environment.
Suppose you had a nice 10 million gate FPGA on your PCI bus. Now, if you program it to do one thing and one thing only, then there's no problem. So if that FPGA set up to be a hardware DiVX encoder and that's it, all is well.
But let's suppose that you fire up your video editor, and it wants the FPGA to be a DiVX encoder. Then you fire up SSH, and SSH wants the FPGA to be an encryption engine.
It is currently VERY hard to dynamically reprogram sections of an FPGA (some do support partial reprogramming while running, but not all). It is also very hard for the hardware compiler to merge tasks - you would have to re-generate the layout of the FPGA each time you added a function.
What we need is the equivilent of a malloc() call to allow a single large FPGA to be used by multiple applications at the same time (until you run out of gates).
Once that exists, then you will see vendors making generic FPGA accelerators.
Until then, FPGA boards will be the province of a very few people, and prices won't come down very much, I fear.
Look out! He's not from the government, he's from MICROSOFT !
.....
DON'T LOOK INTO THE LIGHT, HE'LL ERASE YOUR
<FLASH>
Yes, no tax monies used to support the primaries.
However, I would argue that comes about as a result of prohibiting the parties from using public property or public voting gear, but you are right, it is best to spell it out explicitly.
Of course, even spelling things out explicitly doesn't work - witness "... the right to keep and bear arms shall not be infringed."
Thank you for talking about BNTOA (Binding None Of The Above), a pet subject of mine.
....) that is MY choice.
You need to do one other thing, as well, IMHO: You need to recognize that the "primaries" are nothing of the sort - they are a wart on the side of the electoral process, completely outside the scope of the laws defining the system. They are purely a function of the political parties.
The best thing in the world would be to de-emphasise them, by:
1) not allowing the parties access to the voter rolls as maintained by the State - all they should be able to ask you is "Are you eligable to vote in this district?" not "What party are you registered with?"
2) not allowing the parties to use State property to conduct the primaries - let them find their own damn location to hold the polling and use their own damn equipment to tally the votes. This helps remind people of the unofficial status of the primaries, as well as (hopefully) forcing the two main parties to be at seperate locations, in order to facilitate point #3, which is:
3) If a party wishes to restrict access to its primary voting to party members, that's fine (after all, it IS a private function). However, do NOT allow the parties to prevent me from joining, just because I also joined the other party. If I wish to be BOTH a Rep and a Dem (and a Green and a Lib and a
In the state where I live (Kansas), you are EITHER a Republican OR a Democrat OR an independant, but not more than one of the above. Thus, I cannot vote in both the Rep and Dem primaries - pick one and only one.
With my changes, I could be both a Rep and a Dem, and vote in both primaries, thus preventing the "pick the lesser of two evils" crap when the REAL election comes around - I would at least have a chance to get each party to field a reasonable candidate.
THEN, if the parties refuse to play ball, you can NOTA their sorry selves out of the running.
Thus, the parties won't run lame ass candidates (Like Bush AND Gore) because the matrix looks like this:
Both parties run poor candidates: NOTA wins, both parties have to run a second campain.
Party A runs a poor candidate, party B runs a good candidate - party B wins.
Both parties run good candidates - we ALL win!
Also, in a NOTA system the third parties are given more power - in the first election they can focus on tearing down the Rep/Dem candidtates, and NOT run their own guy.
NOTA wins.
Then the third parties blitz to adverties their guys, being on more even footing with the big boys.
... or quite a bit longer...
"Damn monkeys screwed it up again. Why oh why couldn't I have been given arms to smack them with - 1x4x9 my 1x4x9 ass!"
How very Zen of her...