If you're at work, you're supposed to be working, that's why you're being paid to be there. Most companies do allow you to access hotmail, etc as long as it's not affecting your productivity, but they don't have to and as long as you are doing it with their equipment while they are paying you, it is their business. Actually, most of you probably signed contracts stating that any information you put through the network at your place of employment may be monitored, read, deleted, and so on.
Most manufacturers aren't making much. When I worked at best buy I paid 5% above what best buy paid for them and I only got $2-$3 off of printer cartridges, so the retailers are paying a lot and not making much from them.
Yes, he can, and he has before... sort of. Coolio asked him (actually, his team that asks for permission) to not do the parody of gangsters paradise. Wierd Al's people told him that Coolio said it was fine (as far as I know, that is, wierd al thought he had full permission, otherwise what was the point in asking in the first place?). Afterwards, Coolio was pissed off, of course, but took no legal action as I'm sure he would have if there was some that could be taken.
As the owner/admin of a small web/shell hosting company, I of course have a lot of views on and experience with DoS. I haven't read everything here, but bits and pieces, so sorry if I repeat some stuff... anyway, on with my general reply to a few things here.
1. Why script kiddies do this retarded shit - at least in the shell host biz, the main reason is they are pissed off at one of your customers who has an eggie with you. They decide to take over the channel, so they DoS the hell out of the server to take the eggie down so they can take over the irc channel... retarded.
2. I see many people talking about exposing security holes and whatnot, but DoS attacks really have little to nothing to do with exposing security holes, most of them anyway(I realize many that hardly work now used tcp/ip stack flaws and the like). Anymore, most DoS attacks are just floods of some sort... trying to squeeze a 5 sq. ft. board through a 2 sq. ft. hole, more or less. This is not a server security problem, there's not much an admin can do about it except shell out the money for more bandwidth.
3. Some of you may be happy to know that I have found UUNet great to work with on stopping DoS attacks. They have been right on top of things and got ingres filters (to stop the spoofed IPs, since most DoSes use spoofed IPs) up within about 20 minutes and continued to watch the subnet the flood appeared to be coming from. If you're a target of a DoS, check with your uplink, see if they can filter for you or have them contact UUNet and work with them (UUNet can't do anthing directly unless the DoSer is directly connect to their network, but almost everything goes through them, so they may be able to track down where it's coming from so you can contact that ISP or server admin).
hm, ok, so apparently it can... guess that'll teach me to rtfm, eh? by default it doesn't though still, so by default, it still really doesn't do shit in most cases... oh well, at least it has the fucntionality to be able to work if a person feels like reading up on it, which is better than I thought.
--
I've used getright several times, it connected all to the same server. it could not know the different servers and paths to the file on those different servers without you specifying each one and I know I have never done that, just had it open, clicked on the link for the one server, and away it went making several connections to the 1 server. Perhaps I was using it wrong, but I wouldn't imagine that they would make it more complicated than doing that because the general public (most of the people who would be using it) couldn't figure out this whole specifying different servers and the paths to the files on each server, etc.
--
yes, if it was getting from multiple sites that could work, but getright makes multiple connections to the same server, which means it doesn't (or shouldn't) make any difference except in rare cases.
--
Does anyone have any info on how getright actually works, like technical info?
mathematically speaking, what getright does should make no difference (although i've used it and yes, downloads were consistantly faster). From what I can tell with getright is it contacts the ftp server, it makes 4 or 5 connections to the same server, and splits the file into 4 or 5 chunks... unless you are on a very fast connection and downloading from a very fast server with routers somewhere in between (or a limiter on the ftp) that only allows a fraction of your possible download speed per connection, this should not work.
For example, you have a 1MB file and a 56k modem, you can download 1MB at 5.6k/sec (yes yes, not realistic numbers, the speed isn't that consistant and rarely right on like that, blah blah). Anyway, you download 1MB at 56k, or you download all at the same time 4 256k files at about 1.4k/sec... either way, it comes out to the same amount of time downloading... you've only got 5.6k worth of inbound for all connections combined, unless they do something very strange, the speedup is nothing but a placebo effect in most cases.
Now, if you have a 1.5mb/sec cable connection and you are downloading from say a t1 with no traffic but you and the ftp is setup so that each connection can only get 384k/sec, then yes, this would work... instead of 1 384k connection, you'd have 4 384k connections at once downloading the file, but how often is this the case?
--
They know full well it doesn't matter technically speaking... they keep going with the mhz game anyway because in the consumer market where the consumer knows nothing but "bigger is better", mhz does matter, more mhz == more sales, that's why intel still makes a big deal out of having higher mhz processors. It's not that they haven't reached the same conclusion as the others, it's that it's more money in their pocket not to admit it.
--
So let me get ths straight... as long as I can't afford something, it's ok to steal it. I've got another solution... get a fucking job. If the job you have doesn't pay enough, then go get a better fucking job, if you are incapable of getting a better job, then get off your lazy, worthless, ass and go develop some skills so that you can get the better job. As far as not being able to get access to the software to learn it and become part of the workforce in the future, have you ever checked out a college? The one I lived in the dorms of (saying I actually attended the college is pushing the limits of the truth;) ) had classes on most of this expensive software you need and you could use it free because the college paid for it. They also sell in the college bookstores "student edition" software... it's EXACTLY the same, except far cheaper, I paid $100 for jbuilder pro 2 back when it was around $500, still pricy, but not a bad discount, and put on my college credit card provided by the college to use at their stores, it was no problem at all. If you get off your lazy ass and look around, there's legal, non-harmful, ways of getting what you need, you just have to do the same thing that the people making all this money off of the software you are stealing did and fucking work for it. Allright, I'm off to go steal my ferrari, i'll just tell the cops it's ok since even with my 2 jobs I can't afford one... and perhaps I'll stop into the server farm area here at work and take home one of the unisys systems, too... on top of being ok since I can't afford it, i'll be doing them a favor since I can now learn to use it and get a job doing that, right?
--
yes, throwing a whole lot of "good" information at them is at least as bad as just handing them what they want and not making them learn, because then not only do they not understand, but in the end they probably still can't do what they were trying, not even in the trained chimp sense. I usually point them to a step by step readme somewhere and tell them to follow the steps and ask me what any of the steps specifically mean or do if it's not blatantly obvious to them, and try to keep my explanations relevent, of course.
--
That kind of attitude is not helping anything. If someone wants to learn, I'm happy to help them... not by just handing over the answer so they don't have to think, but give them a url to a howto, point out that handy file called README, etc. I don't think the answers should just be handed out so that people know nothing about their OS like they do with windows, but I don't think we should turn down anyone who is willing to put in the effort to learn, either.
--
The problem with that is this... what happens when you need fish and can't go to the store to buy some (post nuclear war, car stranded you 200 miles from any town, whatever, just pretend;) ) and you don't know how to fish... not know how but don't like to, but truly don't know, what will you do? Now the fish example, of course, is unlikely to be a problem anyway, but computers are a different story. Computers are unstable by nature, they are too easily adversely affected by slight changes and there's not much we can do about it. What happens when a user gets an illegal operation when doing something, what happens when their child is messing around and mutes the sound, what happens when their child accidentally drags the taskbar to the side of the screen or sets it to autohide (for just a cosmetic or interface change), what will the user do?... probably call me for help because they don't know how to use their computer.
To go along with your car example, I don't ask that users be mechanics (coders and network engineers, etc), I ask that they be able to change their tire if they get a flat 30 miles from home or add oil and preferably be able to change their oil... but most users aren't even 100% sure of themselves as to which pedal to push to stop or go.
--
That's completely accurate. I just a few minutes ago posted a reply that said the same thing, but I think you worded it much better than I did. Now the question is "how do we make them want to learn to use and not be (as I called them) trained chimps?" When we try to show them how to learn and use, they think we are being assholes, if we show them in a way that they think we are helpful, they don't learn anything. What I pesonally try to remember to do to remedy this is tell the person beforehand that I may come off sounding like an asshole at times, but it's not because i'm being a dick, it's because I'm trying to help them learn to truly use and not just memorize a couple meaningless steps. Most people I have dealt with have accepted this and were gratreful for it... a few come back without reading the README next time and thinking for themselves anyway, but most are good about it. What I have found also helps is telling them not to be afraid of screwing things up by doing something wrong, to trust in their judgement and interperetation (I've found that's the problem with many, they read it, they understand it, but they don't trust their understanding so they ask anyway), but to PAY ATTENTION (another big problem I have with the users here at work, they don't understand what the computer is doing, so they don't pay attention to it) to what they are doing, and even to write down the before and after of any changes they made, that way if they did happen to make a mess, they can go back and fix it with little or no worries.
--
umm... maybe you didn't notice, but they don't port to each linux variant. The source is the same and works on all, just download the source tarball and away you go... now some people make an RPM of the precompiled source, etc, for rh and a slackpack for slackware, etc, but that's someone just making it easier for the lazy asses who can't handle "./configure; make; make install;" which is what you want anyway, right?
--
Ok, here's the problem with trying to help people with linux, this is how 90% of my conversations with linux newbies go...
newbie: hey, how do I do X?
me: Did you read the documentation that comes with it, like README ?
newbie: yes, but I still can't figure it out
me: what did it say to do first?
newbie: type 'cp myfile.conf/etc/myfile.conf'
me: well, did you do that?
newbie: no, should I?
me: well... the instructions say to don't they?
and so the conversation continues. This is either laziness or stupidity, which one depends on the person. Either way, the person is not going to learn anything by you telling them the steps to do.... teach them to read and understand the documentation, not the step by step of doing 1 specific task that they don't understand what those steps are or how they affect anything, anyway. Just handing something over on a silver platter doesn't help people to learn to "use" it... if they are somewhat paying attention it may help them to do the same task again, like a trained chimp, but for most (not all), it is not going to help in the long run, in truly learning to use their computer, to know how it works so that they can figure things out for themselves. Some of you apparently see this as making things more difficult than they need to be, but I think they need to be like this for users to learn, otherwise we'll have the same problem with linux as we all bitch about with windows... it's so simple to do things that no one knows wtf they are doing or how to use their computer, and as your average windows userhas shown us, they do not wish to learn and are not going to learn if they do not absolutely have to to get the job done. As one of the best teachers I have ever had said, "I am a Learning Facilitator, not a teacher. I do not teach people how to do specific tasks, I help them learn to teach themselves." Those of us making it "too difficult" by saying RTFM, etc, are not making it difficult at all, they just have to read a step by step README, what's the difference, speaking of difficulty, in typing "./Configure" after seeing me type it in and irc chan and when they read it in the README? As far as difficulty goes, there's no difference, it's still "read line then copy letter for letter what line of instruction says", but by doing it from the README, they have done it themselves and often are more likely to remember it, plus the readme will commonly give some other, very important information, that I am not going to give the user. By making them read that, we are showing them how to teach themselves so that they may do it on their own next time instead of waiting for someone else to come along and do it for them.
--
wow, prices on the isdn aren't too bad there, comparitively. I looked into getting isdn at my apartment in the US, ISP was $30/month for unlimited 128k, not bad... phone company wanted about $300/month for unlimited 128k... very bad.
--
you might look into broadslate sdsl although it's expensive, as it's technically for businesses only... i'm paying $230/month for 400Kb sdsl and I believe it tops out at like $650/month for 2.3Mbit, but it's very stable, the support people actually know what they're talking about. You can run your own mail, dns (including reverse dns on your IPs), http, ftp, whatever you want. Plus at the prices they charge for the lower speed stuff, I doubt they're going under anytime soon.
--
I've actually seen this in action on a video
on
Battlefield Lasers
·
· Score: 1
In my phsyics class in highschool my teacher showed some video that showed these lasers in action. This technology apparently has actually been around since at least the 70's, although apparently not in use. In the video we were shown they had a large laser cannon, almost like a mortar, but with laser, and blew up a military jeep with it. My guess is it was a far less efficient version of the technology that they weren't going to use in actual battle situations, because it was unheard of by anyone I know of, including military people, but if they were wanting to keep it secret, it obviously would not have been in a highschool physics video.
--
Everyone that paid $50 for everquest, ultima online, etc and continues to pay $10/month to play them. Of course that's slightly different, you can't just hop on irc and play them for free.
--
I'm sure they can forfeit your right to listen to it as logn as you agree to their terms of service.... now can they phsycially do it, that's another question. The only way I see of possibly doing this is proprietary players/file formats that contact a server with your username/password... and even that, of course, could be relatively easily cracked. Between costing money and having limited music when you can get on the web, irc, etc and get basically any song at no charge, I don't think these services will last very long, anyway.
--
yes, but how were they to know? and anyway, a lot DID use macs, at least in iowa, almost every school district had a contract with apple and so used apples and macs and only had 1 or 2 winodws computers in each school.
--
ahh yes, BBS doors... LORD, Usurper, Planets TEOS... perhaps I'll setup a telnet BBS with these games so we can all play them again (I did a couple years ago on @home and then got busted and had to take it down). hmmmm... perhaps someone should code web based versions of LORD and Usurper... not I, I blow at coding and haven't touched any languages that would work well for that, like asp and whatnot.
--
Slashdot Mirror
If you're at work, you're supposed to be working, that's why you're being paid to be there. Most companies do allow you to access hotmail, etc as long as it's not affecting your productivity, but they don't have to and as long as you are doing it with their equipment while they are paying you, it is their business. Actually, most of you probably signed contracts stating that any information you put through the network at your place of employment may be monitored, read, deleted, and so on.
Most manufacturers aren't making much. When I worked at best buy I paid 5% above what best buy paid for them and I only got $2-$3 off of printer cartridges, so the retailers are paying a lot and not making much from them.
The growing scum in your sink is smaller? How'd you manage that?
Are you sure you don't remember playing Wolfenstein 3d on that computer?
Yes, he can, and he has before... sort of. Coolio asked him (actually, his team that asks for permission) to not do the parody of gangsters paradise. Wierd Al's people told him that Coolio said it was fine (as far as I know, that is, wierd al thought he had full permission, otherwise what was the point in asking in the first place?). Afterwards, Coolio was pissed off, of course, but took no legal action as I'm sure he would have if there was some that could be taken.
As the owner/admin of a small web/shell hosting company, I of course have a lot of views on and experience with DoS. I haven't read everything here, but bits and pieces, so sorry if I repeat some stuff... anyway, on with my general reply to a few things here.
1. Why script kiddies do this retarded shit - at least in the shell host biz, the main reason is they are pissed off at one of your customers who has an eggie with you. They decide to take over the channel, so they DoS the hell out of the server to take the eggie down so they can take over the irc channel... retarded.
2. I see many people talking about exposing security holes and whatnot, but DoS attacks really have little to nothing to do with exposing security holes, most of them anyway(I realize many that hardly work now used tcp/ip stack flaws and the like). Anymore, most DoS attacks are just floods of some sort... trying to squeeze a 5 sq. ft. board through a 2 sq. ft. hole, more or less. This is not a server security problem, there's not much an admin can do about it except shell out the money for more bandwidth.
3. Some of you may be happy to know that I have found UUNet great to work with on stopping DoS attacks. They have been right on top of things and got ingres filters (to stop the spoofed IPs, since most DoSes use spoofed IPs) up within about 20 minutes and continued to watch the subnet the flood appeared to be coming from. If you're a target of a DoS, check with your uplink, see if they can filter for you or have them contact UUNet and work with them (UUNet can't do anthing directly unless the DoSer is directly connect to their network, but almost everything goes through them, so they may be able to track down where it's coming from so you can contact that ISP or server admin).
hm, ok, so apparently it can... guess that'll teach me to rtfm, eh? by default it doesn't though still, so by default, it still really doesn't do shit in most cases... oh well, at least it has the fucntionality to be able to work if a person feels like reading up on it, which is better than I thought.
--
I've used getright several times, it connected all to the same server. it could not know the different servers and paths to the file on those different servers without you specifying each one and I know I have never done that, just had it open, clicked on the link for the one server, and away it went making several connections to the 1 server. Perhaps I was using it wrong, but I wouldn't imagine that they would make it more complicated than doing that because the general public (most of the people who would be using it) couldn't figure out this whole specifying different servers and the paths to the files on each server, etc.
--
yes, if it was getting from multiple sites that could work, but getright makes multiple connections to the same server, which means it doesn't (or shouldn't) make any difference except in rare cases.
--
Does anyone have any info on how getright actually works, like technical info?
mathematically speaking, what getright does should make no difference (although i've used it and yes, downloads were consistantly faster). From what I can tell with getright is it contacts the ftp server, it makes 4 or 5 connections to the same server, and splits the file into 4 or 5 chunks... unless you are on a very fast connection and downloading from a very fast server with routers somewhere in between (or a limiter on the ftp) that only allows a fraction of your possible download speed per connection, this should not work.
For example, you have a 1MB file and a 56k modem, you can download 1MB at 5.6k/sec (yes yes, not realistic numbers, the speed isn't that consistant and rarely right on like that, blah blah). Anyway, you download 1MB at 56k, or you download all at the same time 4 256k files at about 1.4k/sec... either way, it comes out to the same amount of time downloading... you've only got 5.6k worth of inbound for all connections combined, unless they do something very strange, the speedup is nothing but a placebo effect in most cases.
Now, if you have a 1.5mb/sec cable connection and you are downloading from say a t1 with no traffic but you and the ftp is setup so that each connection can only get 384k/sec, then yes, this would work... instead of 1 384k connection, you'd have 4 384k connections at once downloading the file, but how often is this the case?
--
They know full well it doesn't matter technically speaking... they keep going with the mhz game anyway because in the consumer market where the consumer knows nothing but "bigger is better", mhz does matter, more mhz == more sales, that's why intel still makes a big deal out of having higher mhz processors. It's not that they haven't reached the same conclusion as the others, it's that it's more money in their pocket not to admit it.
--
So let me get ths straight... as long as I can't afford something, it's ok to steal it. I've got another solution... get a fucking job. If the job you have doesn't pay enough, then go get a better fucking job, if you are incapable of getting a better job, then get off your lazy, worthless, ass and go develop some skills so that you can get the better job. As far as not being able to get access to the software to learn it and become part of the workforce in the future, have you ever checked out a college? The one I lived in the dorms of (saying I actually attended the college is pushing the limits of the truth ;) ) had classes on most of this expensive software you need and you could use it free because the college paid for it. They also sell in the college bookstores "student edition" software... it's EXACTLY the same, except far cheaper, I paid $100 for jbuilder pro 2 back when it was around $500, still pricy, but not a bad discount, and put on my college credit card provided by the college to use at their stores, it was no problem at all. If you get off your lazy ass and look around, there's legal, non-harmful, ways of getting what you need, you just have to do the same thing that the people making all this money off of the software you are stealing did and fucking work for it. Allright, I'm off to go steal my ferrari, i'll just tell the cops it's ok since even with my 2 jobs I can't afford one... and perhaps I'll stop into the server farm area here at work and take home one of the unisys systems, too... on top of being ok since I can't afford it, i'll be doing them a favor since I can now learn to use it and get a job doing that, right?
--
yes, throwing a whole lot of "good" information at them is at least as bad as just handing them what they want and not making them learn, because then not only do they not understand, but in the end they probably still can't do what they were trying, not even in the trained chimp sense. I usually point them to a step by step readme somewhere and tell them to follow the steps and ask me what any of the steps specifically mean or do if it's not blatantly obvious to them, and try to keep my explanations relevent, of course.
--
That kind of attitude is not helping anything. If someone wants to learn, I'm happy to help them... not by just handing over the answer so they don't have to think, but give them a url to a howto, point out that handy file called README, etc. I don't think the answers should just be handed out so that people know nothing about their OS like they do with windows, but I don't think we should turn down anyone who is willing to put in the effort to learn, either.
--
The problem with that is this... what happens when you need fish and can't go to the store to buy some (post nuclear war, car stranded you 200 miles from any town, whatever, just pretend ;) ) and you don't know how to fish... not know how but don't like to, but truly don't know, what will you do? Now the fish example, of course, is unlikely to be a problem anyway, but computers are a different story. Computers are unstable by nature, they are too easily adversely affected by slight changes and there's not much we can do about it. What happens when a user gets an illegal operation when doing something, what happens when their child is messing around and mutes the sound, what happens when their child accidentally drags the taskbar to the side of the screen or sets it to autohide (for just a cosmetic or interface change), what will the user do? ... probably call me for help because they don't know how to use their computer.
To go along with your car example, I don't ask that users be mechanics (coders and network engineers, etc), I ask that they be able to change their tire if they get a flat 30 miles from home or add oil and preferably be able to change their oil... but most users aren't even 100% sure of themselves as to which pedal to push to stop or go.
--
That's completely accurate. I just a few minutes ago posted a reply that said the same thing, but I think you worded it much better than I did. Now the question is "how do we make them want to learn to use and not be (as I called them) trained chimps?" When we try to show them how to learn and use, they think we are being assholes, if we show them in a way that they think we are helpful, they don't learn anything. What I pesonally try to remember to do to remedy this is tell the person beforehand that I may come off sounding like an asshole at times, but it's not because i'm being a dick, it's because I'm trying to help them learn to truly use and not just memorize a couple meaningless steps. Most people I have dealt with have accepted this and were gratreful for it... a few come back without reading the README next time and thinking for themselves anyway, but most are good about it. What I have found also helps is telling them not to be afraid of screwing things up by doing something wrong, to trust in their judgement and interperetation (I've found that's the problem with many, they read it, they understand it, but they don't trust their understanding so they ask anyway), but to PAY ATTENTION (another big problem I have with the users here at work, they don't understand what the computer is doing, so they don't pay attention to it) to what they are doing, and even to write down the before and after of any changes they made, that way if they did happen to make a mess, they can go back and fix it with little or no worries.
--
umm... maybe you didn't notice, but they don't port to each linux variant. The source is the same and works on all, just download the source tarball and away you go... now some people make an RPM of the precompiled source, etc, for rh and a slackpack for slackware, etc, but that's someone just making it easier for the lazy asses who can't handle "./configure; make; make install;" which is what you want anyway, right?
--
Ok, here's the problem with trying to help people with linux, this is how 90% of my conversations with linux newbies go...
/etc/myfile.conf'
newbie: hey, how do I do X?
me: Did you read the documentation that comes with it, like README ?
newbie: yes, but I still can't figure it out
me: what did it say to do first?
newbie: type 'cp myfile.conf
me: well, did you do that?
newbie: no, should I?
me: well... the instructions say to don't they?
and so the conversation continues. This is either laziness or stupidity, which one depends on the person. Either way, the person is not going to learn anything by you telling them the steps to do.... teach them to read and understand the documentation, not the step by step of doing 1 specific task that they don't understand what those steps are or how they affect anything, anyway. Just handing something over on a silver platter doesn't help people to learn to "use" it... if they are somewhat paying attention it may help them to do the same task again, like a trained chimp, but for most (not all), it is not going to help in the long run, in truly learning to use their computer, to know how it works so that they can figure things out for themselves. Some of you apparently see this as making things more difficult than they need to be, but I think they need to be like this for users to learn, otherwise we'll have the same problem with linux as we all bitch about with windows... it's so simple to do things that no one knows wtf they are doing or how to use their computer, and as your average windows userhas shown us, they do not wish to learn and are not going to learn if they do not absolutely have to to get the job done. As one of the best teachers I have ever had said, "I am a Learning Facilitator, not a teacher. I do not teach people how to do specific tasks, I help them learn to teach themselves." Those of us making it "too difficult" by saying RTFM, etc, are not making it difficult at all, they just have to read a step by step README, what's the difference, speaking of difficulty, in typing "./Configure" after seeing me type it in and irc chan and when they read it in the README? As far as difficulty goes, there's no difference, it's still "read line then copy letter for letter what line of instruction says", but by doing it from the README, they have done it themselves and often are more likely to remember it, plus the readme will commonly give some other, very important information, that I am not going to give the user. By making them read that, we are showing them how to teach themselves so that they may do it on their own next time instead of waiting for someone else to come along and do it for them.
--
wow, prices on the isdn aren't too bad there, comparitively. I looked into getting isdn at my apartment in the US, ISP was $30/month for unlimited 128k, not bad... phone company wanted about $300/month for unlimited 128k... very bad.
--
you might look into broadslate sdsl although it's expensive, as it's technically for businesses only... i'm paying $230/month for 400Kb sdsl and I believe it tops out at like $650/month for 2.3Mbit, but it's very stable, the support people actually know what they're talking about. You can run your own mail, dns (including reverse dns on your IPs), http, ftp, whatever you want. Plus at the prices they charge for the lower speed stuff, I doubt they're going under anytime soon.
--
In my phsyics class in highschool my teacher showed some video that showed these lasers in action. This technology apparently has actually been around since at least the 70's, although apparently not in use. In the video we were shown they had a large laser cannon, almost like a mortar, but with laser, and blew up a military jeep with it. My guess is it was a far less efficient version of the technology that they weren't going to use in actual battle situations, because it was unheard of by anyone I know of, including military people, but if they were wanting to keep it secret, it obviously would not have been in a highschool physics video.
--
Everyone that paid $50 for everquest, ultima online, etc and continues to pay $10/month to play them. Of course that's slightly different, you can't just hop on irc and play them for free.
--
I'm sure they can forfeit your right to listen to it as logn as you agree to their terms of service.... now can they phsycially do it, that's another question. The only way I see of possibly doing this is proprietary players/file formats that contact a server with your username/password... and even that, of course, could be relatively easily cracked. Between costing money and having limited music when you can get on the web, irc, etc and get basically any song at no charge, I don't think these services will last very long, anyway.
--
yes, but how were they to know? and anyway, a lot DID use macs, at least in iowa, almost every school district had a contract with apple and so used apples and macs and only had 1 or 2 winodws computers in each school.
--
ahh yes, BBS doors... LORD, Usurper, Planets TEOS... perhaps I'll setup a telnet BBS with these games so we can all play them again (I did a couple years ago on @home and then got busted and had to take it down). hmmmm... perhaps someone should code web based versions of LORD and Usurper... not I, I blow at coding and haven't touched any languages that would work well for that, like asp and whatnot.
--