See, that's a hell of a lot more trouble then I wish to go to.
Why?
If a site is going to bombard me with popup ads, or God Forbid audio, then I leave. I haven't found a site yet that is worth the hassle. You won't let me download your stuff unless I use popups? Fine. I will do neither.
Sites can spam me all they want with ads and flashing banners and sound and spyware. I simply won't visit the site again.
More like fuel. Hydrogen and Oxygen. Guess what the shuttle engines run off of?
If we discovered water in any signifigant quantity on the moon, it would (someday) make getting there and back much cheaper and easier. Instead of packing the gas with us, we can stop at the ol' lunar gas station. It is so hellaciously expensive to put things in orbit, every pound saved is a penny earned.
It could also make construction of spacecraft on the moon or in orbit a possibility. Again, the less we have to bring up with us, the better.
It's really useful for things like Frame Relay WANs, where you can get mixed and matched speeds all over the place.
For example, I have the equivilent of a T1 (1.544mb CIR Frame) going to Qwest. From Qwest, I have a 256k CIR Frame link going to a remote office.
When the office sends data to me, it's fine. When I send back, there are massive amounts of Red Frames. Dropped packets means re-transmits which means delay. Delay is bad when you are running an interactive application over these links.
Think of a garden hose connected to a fire hydrant. The garden hose could dump water into the fire hydrant fine (assuming the water for the hydrant is turned off elsewhere...). When the fire hydrant turns on, however...
Now I have QoS maps based off of the DLCI for each office, so it throttles back our link to Qwest to match the remote connection, so everyone talks happily, instead of blasting the little link into oblivion. Now, Red Frames aren't seen very often, unless the Qwest circuit is saturated, and we get chopped back to our base CIR.
It makes a difference. Not a huge one, but a noticeable difference.
Traffic Shaping is your friend. It's all about making the mose efficient use of what you have.
(Or making sure that you still have bandwidth when your roommate is leeching gigs of pr0n...)
M
At CTF at Defcon the Ghettohackers had the teams attacking each other, instead of a central server. They were given an custom distro of linux that was specifically engineered to be horribly insecure. In addition, in order to score points, they had to keep some of these insecure services running. So they couldn't just boot off their CD Image of OpenBSD, and sit there and chuckle. They had to keep things like Finger, and Telnet working and functional in order to get points.
This meant that the "action" starts off hard and heavy. We saw people rooting and getting rooted right away.
To make things a little more interesting, we designed the scoreboard after the NASDAQ Big Board, and projected it on two walls. The teams' scores were displayed as stock prices. The scoreboard was also played over the Alexis Park television system. We had news updates on the status of the teams every so often.
Of course, we didn't broadcast the action as a cute little 'gibson' visualization. Nor were their live DJs (We used pre-set playlists). However, people still seemed to get a kick out of it. You could see the whole room go quiet and stare when a news update would come on...
Next year is going to be even better (Yes, this is a bit of shameless promotion).
I used to be a port agent in Alaska for the cruise ships, and the main way we communicated with them, was via email. Much much nicer than telex or fax. I can actually use vowels now:) Even with the cargo ships I dealt with, we would just use a service called 'stratosmobile'. We'd email the 'telex' to (theshipstelexnumber)@stratosmobile.net and they would take care of it all. Its still not cheap, however. A voicelink to a ship, via INMARSAT, *starts* at about 20 bucks. Thats usually just if you want to say hi. Any more, and it really gets expensive. So sat-based internet isn't cheap.
However, almost all the ports of call (in the Northwest, anyway) have internet cafe's. Just ask any crewmember. They all flock to the cafe's. Not to mention, they are in and out of these ports regularly, so they know all the spots. One of the first questions I would always get from new crew, is "Where is internet cafe?".
On a side note, the telecommunications infrastructure of the non-brand-spanking-new ships, is not exactly robust. Running ethernet to every cabin is not exactly an easy thing to do. The on-board network is usually a core AS/400 server, with a Windows NT client network.
This was a year ago, things might have been upgraded, but I doubt it.
Slashdot Mirror
Why?
If a site is going to bombard me with popup ads, or God Forbid audio, then I leave. I haven't found a site yet that is worth the hassle. You won't let me download your stuff unless I use popups? Fine. I will do neither.
Sites can spam me all they want with ads and flashing banners and sound and spyware. I simply won't visit the site again.
More like fuel. Hydrogen and Oxygen. Guess what the shuttle engines run off of?
If we discovered water in any signifigant quantity on the moon, it would (someday) make getting there and back much cheaper and easier. Instead of packing the gas with us, we can stop at the ol' lunar gas station. It is so hellaciously expensive to put things in orbit, every pound saved is a penny earned.
It could also make construction of spacecraft on the moon or in orbit a possibility. Again, the less we have to bring up with us, the better.
Regards,
Meri
For example, I have the equivilent of a T1 (1.544mb CIR Frame) going to Qwest. From Qwest, I have a 256k CIR Frame link going to a remote office.
When the office sends data to me, it's fine. When I send back, there are massive amounts of Red Frames. Dropped packets means re-transmits which means delay. Delay is bad when you are running an interactive application over these links. Think of a garden hose connected to a fire hydrant. The garden hose could dump water into the fire hydrant fine (assuming the water for the hydrant is turned off elsewhere...). When the fire hydrant turns on, however...
Now I have QoS maps based off of the DLCI for each office, so it throttles back our link to Qwest to match the remote connection, so everyone talks happily, instead of blasting the little link into oblivion. Now, Red Frames aren't seen very often, unless the Qwest circuit is saturated, and we get chopped back to our base CIR. It makes a difference. Not a huge one, but a noticeable difference.
Traffic Shaping is your friend. It's all about making the mose efficient use of what you have. (Or making sure that you still have bandwidth when your roommate is leeching gigs of pr0n...) M
This meant that the "action" starts off hard and heavy. We saw people rooting and getting rooted right away.
To make things a little more interesting, we designed the scoreboard after the NASDAQ Big Board, and projected it on two walls. The teams' scores were displayed as stock prices. The scoreboard was also played over the Alexis Park television system. We had news updates on the status of the teams every so often.
Of course, we didn't broadcast the action as a cute little 'gibson' visualization. Nor were their live DJs (We used pre-set playlists). However, people still seemed to get a kick out of it. You could see the whole room go quiet and stare when a news update would come on...
Next year is going to be even better (Yes, this is a bit of shameless promotion).
R
....but they are all wired.
:)
I used to be a port agent in Alaska for the cruise ships, and the main way we communicated with them, was via email. Much much nicer than telex or fax. I can actually use vowels now
Even with the cargo ships I dealt with, we would just use a service called 'stratosmobile'. We'd email the 'telex' to (theshipstelexnumber)@stratosmobile.net and they would take care of it all.
Its still not cheap, however. A voicelink to a ship, via INMARSAT, *starts* at about 20 bucks. Thats usually just if you want to say hi. Any more, and it really gets expensive. So sat-based internet isn't cheap.
However, almost all the ports of call (in the Northwest, anyway) have internet cafe's. Just ask any crewmember. They all flock to the cafe's. Not to mention, they are in and out of these ports regularly, so they know all the spots. One of the first questions I would always get from new crew, is "Where is internet cafe?".
On a side note, the telecommunications infrastructure of the non-brand-spanking-new ships, is not exactly robust. Running ethernet to every cabin is not exactly an easy thing to do.
The on-board network is usually a core AS/400 server, with a Windows NT client network.
This was a year ago, things might have been upgraded, but I doubt it.