Strange that it took so long... 5222 is the standard jabber c2s port. And jabber responds if you telnet in and type anything at all, followed by enter.
What if I read off the byte-level contents of a jpeg of lesbians munching pussy, or publish them in a book? The former must fit your stringent definition of "speech", though perhaps the latter does not.
Unlike with spam, where something like.01% of people is enough to make huge profits, a significant percentage of people buy and enjoy the music industry's crap. The problem is that people in general *do* like it.
But they are. If they weren't willing to pay as much as they pay, they wouldn't be doing it. Do you think the money that recording artists are paid appears from nowhere? No, somebody is willing to pay them that much!
Except that as far as I know those things measure axles, of which cars have two, and tractor-trailers usually have 5. In addition, tractor-trailers cause more wear and tear on the roads due to their disproportionately higher weight.
Of course, I agree with you that the statistics are more likely to be measuring percentage of files that are movies since that's more useful. If it were an ISP or such, it might be expected that they would measure amount of data transferred instead.
But I don't think this indicates much of a shift in P2P user habits... I'd guess that it's more about a shift from mp3 to ogg/vorbis, which is more interesting to me, and probably the rest of the slashdot crowd.
But that problem exists anyway. I work 11am to 7pm, but some of my friends work 9 am to 5 pm, others work 7am to 6 pm... Guess what, we manage to coordinate our schedules to be able to hang out together.
And as to people in other time zones, if a meeting is set up there's still a question of which timezone they mean, and daylight "savings" just adds to the confusion, especially since some places change at times different from others.
It seems like dropping timezones would have the effect you mention as being positive. "Meet me at 10:00" is unambiguous, you just have to decide "what do I do at that time?" instead of "do you mean my time or yours? Is DST in effect there? What's the offset there in that case? Is DST in effect here? What's the offset here in that case? So the time here is x:xx. What do I do at that time?" Sounds a lot easier to me. And "what time is it there" is just a currently necessary short-circuit for calculating the difference between places so you can ask "can we meet/call/whatever at x:xx your time"... no one ever schedules meetings by asking "what time do you start work" or "what time do you wake up"!... "what time is it there" says little to nothing about when someone works, wakes up, or is available to meet/talk.
Hell, for people in what is currently the same time zone it would make exactly *zero* difference in arranging meetings.
And it would make anything involving multiple timezones much much easier. Plane tickets, bus/train schedules, meeting arrangements, etc. And all we'd "lose" by dropping time zones is something we don't have anyway: everyone working exactly the same hours.
Hmm, around here (and I suspect in most offices, where graphics work is relatively rare) "Adobe" most often refers to Acrobat. Or Acrobat Reader.
And "Microsoft" often refers to Windows instead of Office. Or some specific component of Office. Or MSIE. Or any program at all, actually, including Linux.
I'm not trying to push any rules on anyone. On the contrary, it seems that in English the only rule is that there are no rules.
I'm just saying, if you can accept ox->oxen, child->children, brother->brethren, then box->boxen has a precedent, and bitching about people using it is stupid.
"the general rule is you take your age plus the percent of your body that got burned, and if it's over 100, you won't live"
So the general rule is that people over 100 years of age are dead?
Also, more seriously... the "far enough below 100 to not be at all concerned" doesn't make sense since I doubt that it scales at all linearly....if it adds up to 99, that doesn't mean 99% probability of death, if it adds up to 25, that doesn't mean a 25% possibility of death. It sounds to me mostly like "older people have a higher risk of death due to burns than younger people"
So it's better to just go ahead and crash the production servers?
What if you have 2 "crashy" patches in a row, and while the test servers are being rebuilt from the first crashy patch you decide to skip the testing process. Bam, now your servers that are so mission critical are down, as well as your testing servers.
Oh... that's kinda tough, then. Though, if you use a VPN for the work stuff, and ssl (e.g. https: websites) you should be OK to not use the WAP's encryption.
Slashdot Mirror
Strange that it took so long ... 5222 is the standard jabber c2s port. And jabber responds if you telnet in and type anything at all, followed by enter.
What if I read off the byte-level contents of a jpeg of lesbians munching pussy, or publish them in a book? The former must fit your stringent definition of "speech", though perhaps the latter does not.
Yeah, it really sucks up here in Wisconsin where every night in winter I have to replace the battery in my car.
Whoops, forgot I'm in reality. Never mind.
Unlike with spam, where something like .01% of people is enough to make huge profits, a significant percentage of people buy and enjoy the music industry's crap. The problem is that people in general *do* like it.
But they are. If they weren't willing to pay as much as they pay, they wouldn't be doing it. Do you think the money that recording artists are paid appears from nowhere? No, somebody is willing to pay them that much!
Me too, though their music is definitely not for all tastes. I've purchased a couple of albums from them.
Except that as far as I know those things measure axles, of which cars have two, and tractor-trailers usually have 5. In addition, tractor-trailers cause more wear and tear on the roads due to their disproportionately higher weight.
... I'd guess that it's more about a shift from mp3 to ogg/vorbis, which is more interesting to me, and probably the rest of the slashdot crowd.
Of course, I agree with you that the statistics are more likely to be measuring percentage of files that are movies since that's more useful. If it were an ISP or such, it might be expected that they would measure amount of data transferred instead.
But I don't think this indicates much of a shift in P2P user habits
Yes
"it is definately not worth the millions of dollars that they receive." ...apparently it is, or people would not be willing to pay that much for it.
If by "pay" you mean "download for free". http://magnatune.com/info/openmusic
You can't have that everywhere without smaller time zones. Other than that, I agree.
But that problem exists anyway. I work 11am to 7pm, but some of my friends work 9 am to 5 pm, others work 7am to 6 pm ... Guess what, we manage to coordinate our schedules to be able to hang out together.
... no one ever schedules meetings by asking "what time do you start work" or "what time do you wake up"! ... "what time is it there" says little to nothing about when someone works, wakes up, or is available to meet/talk.
And as to people in other time zones, if a meeting is set up there's still a question of which timezone they mean, and daylight "savings" just adds to the confusion, especially since some places change at times different from others.
It seems like dropping timezones would have the effect you mention as being positive. "Meet me at 10:00" is unambiguous, you just have to decide "what do I do at that time?" instead of "do you mean my time or yours? Is DST in effect there? What's the offset there in that case? Is DST in effect here? What's the offset here in that case? So the time here is x:xx. What do I do at that time?" Sounds a lot easier to me. And "what time is it there" is just a currently necessary short-circuit for calculating the difference between places so you can ask "can we meet/call/whatever at x:xx your time"
Hell, for people in what is currently the same time zone it would make exactly *zero* difference in arranging meetings.
And it would make anything involving multiple timezones much much easier. Plane tickets, bus/train schedules, meeting arrangements, etc. And all we'd "lose" by dropping time zones is something we don't have anyway: everyone working exactly the same hours.
Hmm, around here (and I suspect in most offices, where graphics work is relatively rare) "Adobe" most often refers to Acrobat. Or Acrobat Reader.
And "Microsoft" often refers to Windows instead of Office. Or some specific component of Office. Or MSIE. Or any program at all, actually, including Linux.
...or one could just [drum roll please] have the lights on when it's dark, and not when it's light. What a brilliant idea!!
Hey, what about heart?
The problem is with the horrible angles that the main keyboard uses. Not good for a keypad. Other than that I agree.
"There are no hard and fast rules in English."
Exactly. So why are you arguing that others shouldn't use "boxen"?
Oh, and thanks for the personal attacks. It is well-deserving of its (current) "flamebait" moderation.
Huh? "hard-and-fast"?
I'm not trying to push any rules on anyone. On the contrary, it seems that in English the only rule is that there are no rules.
I'm just saying, if you can accept ox->oxen, child->children, brother->brethren, then box->boxen has a precedent, and bitching about people using it is stupid.
re: point 3, why not?
ox -> oxen, why not box-> boxen?
It's not like the "rules" of English are any more consistent elsewhere.
Though I think that boci would be equally appropriate (latin, "vox" -> "voci").
"the general rule is you take your age plus the percent of your body that got burned, and if it's over 100, you won't live"
... the "far enough below 100 to not be at all concerned" doesn't make sense since I doubt that it scales at all linearly....if it adds up to 99, that doesn't mean 99% probability of death, if it adds up to 25, that doesn't mean a 25% possibility of death. It sounds to me mostly like "older people have a higher risk of death due to burns than younger people"
So the general rule is that people over 100 years of age are dead?
Also, more seriously
Do you have a source for this "general rule"?
So it's better to just go ahead and crash the production servers?
What if you have 2 "crashy" patches in a row, and while the test servers are being rebuilt from the first crashy patch you decide to skip the testing process. Bam, now your servers that are so mission critical are down, as well as your testing servers.
Seems like a poor strategy to me.
Oh ... that's kinda tough, then. Though, if you use a VPN for the work stuff, and ssl (e.g. https: websites) you should be OK to not use the WAP's encryption.
Huh? Where did they claim that keeping the coffee hotter "saved a few cents"?
Use SSL or ipsec for the transmissions you wish to keep secure. It's more secure than WPA too.
I certainly hope not, since that's not a valid IP address.