The major point that should be taken away by this lawsuit and others recently, is that the judges and lawyers have almost no technical knowledge to even understand if a crime has been commited.
How can a judge who can barely use his wordprocessor undertstand complex technical protocols?
I wrote about this 5 years ago when Napster was on the hotseat.
Napster: History Repeats Itself http://www.idrop.com/Notes/HistoryRepeats.asp
I could see this technolgy taking off when we see Wi-Fi taking off in smaller devices.
* Let's say your skiing and these b/w symbols are on the signs and "current" trail, weather, hazard information pops up. It's not cost effective to have the signs electronic (not to mention theft), but a Wi-Fi Goggles with real-time info would be helpful.
Or with GPS...
* Let's say you're skiing and you've lost your kid who is equipped with a GPS unit, and these b/w symbols are on the signs and pop up 3D arrows to the kid's location.
The symbols are just static tags in this case, providing cheap location markers and a content index for the expensive unit on your head.
In reading the other posts it is the INCOMING Port 25 that these other ISPs are blocking.
With AOL they are blocking the OUTGOING Port 25. So if you dial into AOL and try to connect to a SMTP server on Port 25 you will fail.
Following Lisa's posting about "@Home blocking PORT 25" I would like to add that AOL does the same thing.
Our traveling reps use AOL to connect to the net when they are away from the company LAN. We were having issues with email constantly getting rejected. A quick telnet diag revealed that AOL has a Proxy on port 25 that grabs users requests.
Numerous calls the AOL Joke Support didn't get us anywhere. Just explaining the issue is grueling because the Script Reading techs just spout off canned answers like "We only support AOL mail and not Outlook, etc". I tell them "If AOL is suppose to be a true ISP they shouldn't hinder people trying to use Port 25." When you try to ask for a Senior Tech they keep on with their canned drivel.
We've had to setup another mailserver at the company that listens on Port 2525 in order for our users to send mail. AOL won't acknowledge the issue at all.
Every other port works fine, just Port 25 they capture for some reason.
Slashdot Mirror
The major point that should be taken away by this lawsuit and others recently, is that the judges and lawyers have almost no technical knowledge to even understand if a crime has been commited. How can a judge who can barely use his wordprocessor undertstand complex technical protocols? I wrote about this 5 years ago when Napster was on the hotseat. Napster: History Repeats Itself
http://www.idrop.com/Notes/HistoryRepeats.asp
I could see this technolgy taking off when
we see Wi-Fi taking off in smaller devices.
* Let's say your skiing and these b/w
symbols are on the signs and "current" trail,
weather, hazard information pops up. It's not
cost effective to have the signs electronic
(not to mention theft), but a Wi-Fi Goggles
with real-time info would be helpful.
Or with GPS...
* Let's say you're skiing and you've lost your
kid who is equipped with a GPS unit, and these
b/w symbols are on the signs and pop up 3D
arrows to the kid's location.
The symbols are just static tags in this case,
providing cheap location markers and a content
index for the expensive unit on your head.
Markus Diersbock
In reading the other posts it is the INCOMING Port 25 that these other ISPs are blocking. With AOL they are blocking the OUTGOING Port 25. So if you dial into AOL and try to connect to a SMTP server on Port 25 you will fail.
Following Lisa's posting about "@Home blocking PORT 25" I would like to add that AOL does the same thing.
Our traveling reps use AOL to connect to the net when they are away from the company LAN. We were having issues with email constantly getting rejected. A quick telnet diag revealed that AOL has a Proxy on port 25 that grabs users requests.
Numerous calls the AOL Joke Support didn't get us anywhere. Just explaining the issue is grueling because the Script Reading techs just spout off canned answers like "We only support AOL mail and not Outlook, etc". I tell them "If AOL is suppose to be a true ISP they shouldn't hinder people trying to use Port 25." When you try to ask for a Senior Tech they keep on with their canned drivel.
We've had to setup another mailserver at the company that listens on Port 2525 in order for our users to send mail. AOL won't acknowledge the issue at all.
Every other port works fine, just Port 25 they capture for some reason.