They should resuscitate some Apple ][s and make all the competitors play Microsoft's Olympic Decathlon. Man that game was tough on the fingers... and probably broke more keyboards in its day than any modern-era game.
I take a small bit of exception to the author's statement:
"Although the higher rated songs are given preference, you will not definitively hear more 5-star rated songs than all other ratings. Most people follow a bell shaped curve for their ratings, with the 3-star rating being the most common."
In fact, I find that I tend to rate only the songs I *really* like and *really* dislike, and leave the average songs alone. I suspect that I am not alone here. It's akin to the trend of many online forums to attract polarized opinions; i.e., few people take the time to log into forums and post comments that are middle-of-the-road -- typically they're full of "THIS SUCKS" or "HELL YEAH" posts.
If you're looking for a collision, you'll always (100% of the time) find it on your last try. Because after finding it, you have succeeded and discontinue looking.
Apparently you have some misconceptions of how SIP works too.
The latest SIP RFC (RFC 3261) *requires* (in normative text) that all devices support both TCP and UDP as transport protocols. SIP devices MUST use TCP as a transport mechanism if the message to be sent is within 200 bytes of the MTU of the transit link.
Also, SIP has no "GET" header (like HTTP). The SIP methods defined by RFC 3261 include INVITE, REGISTER, ACK, BYE, CANCEL, and OPTIONS. Other subsequent SIP-related RFCs include other methods such as PRACK, SUBSCRIBE/NOTIFY, INFO, and UPDATE. These are all well defined and the RFCs are publicly available.
I agree with the parent poster that SIP devices should be considered servers. I'd go one step further that the RFC defines a PEER TO PEER protocol, where all SIP devices MUST act as both clients AND servers. If I call you, my request is made from the "client" aspect to your "server" aspect. Once the call is setup, if you hang up the phone, your BYE message is sent from your "client" aspect to my "server" aspect. This is the nature of SIP.
Interactive Intelligence distributes a free SIP proxy for Windows. It's easy to get up and running, but my testing has been somewhat limited. They also have a User Support forum where the ININ developers will answer your questions directly.
Just guessing here (well, I did sniff some packets with Ethereal) but I think that the negotiation is done using an open (3rd party) host -- so the call setup is not necessarily P2P. But, the RTP packets flowing between me and my callee were definitely end-to-end, P2P.
This is probably counting on the fact that most home firewalls use fully conic NATting.
I'm also guessing that the signaling and media are using the same port, unlike most (all?) other VoIP protocols. This saves the desginers from having to worry about keeping two NAT bindings alive.
Re:I can see it now... BabyBell propaganda campaig
on
New VOIP App. Profiled
·
· Score: 1
Apple uses SIP in its iChat AV software. "Kazaa" implementing this in their Skype software is mentioned in the article (in reference to a question regarding Pulver's FWD).
I agree with the parent poster -- I had a lot of noise in mp3 files imported directly into Final Cut Pro 3; when I converted them to AIFF first, then imported them the noise disappeared.
Very recently (within the past month?) ticketmaster.com has begun using gimpy-styled captchas, presumably to prevent automated ticket-buying applications.
Anyone know of any other "mainstream" sites using these tests?
I'm not exactly sure when or where N^N was introducted to this line of discussion. I was refering to N! which, although related to N^{nth power}, actually increases faster than N^{nth). Perhaps I am wrong.
Yep, I think so. It's 4:30am here, so I may be a bit fuzzy-headed... but I think N^N increases MUCH faster than N! 1! = 1, 1^1 = 1 2! = 2, 2^2 = 4 3! = 6, 3^3 = 27 4! = 24, 4^4 = 256... etc.
Slashdot Mirror
They should resuscitate some Apple ][s and make all the competitors play Microsoft's Olympic Decathlon. Man that game was tough on the fingers... and probably broke more keyboards in its day than any modern-era game.
Missing:
4. Browse at -1.
In fact, I find that I tend to rate only the songs I *really* like and *really* dislike, and leave the average songs alone. I suspect that I am not alone here. It's akin to the trend of many online forums to attract polarized opinions; i.e., few people take the time to log into forums and post comments that are middle-of-the-road -- typically they're full of "THIS SUCKS" or "HELL YEAH" posts.
Tetris just got a lot harder.
If you're looking for a collision, you'll always (100% of the time) find it on your last try. Because after finding it, you have succeeded and discontinue looking.
Apparently you have some misconceptions of how SIP works too.
The latest SIP RFC (RFC 3261) *requires* (in normative text) that all devices support both TCP and UDP as transport protocols. SIP devices MUST use TCP as a transport mechanism if the message to be sent is within 200 bytes of the MTU of the transit link.
Also, SIP has no "GET" header (like HTTP). The SIP methods defined by RFC 3261 include INVITE, REGISTER, ACK, BYE, CANCEL, and OPTIONS. Other subsequent SIP-related RFCs include other methods such as PRACK, SUBSCRIBE/NOTIFY, INFO, and UPDATE. These are all well defined and the RFCs are publicly available.
I agree with the parent poster that SIP devices should be considered servers. I'd go one step further that the RFC defines a PEER TO PEER protocol, where all SIP devices MUST act as both clients AND servers. If I call you, my request is made from the "client" aspect to your "server" aspect. Once the call is setup, if you hang up the phone, your BYE message is sent from your "client" aspect to my "server" aspect. This is the nature of SIP.
Semantics or no, Massachusetts is a one of four commonwealths. It should not be referred to as the "State of Massachusetts".
How does it feel to see one of the beautiful people?
Happy 20th Anniversary, Macintosh users. You get... a security fix.
Interactive Intelligence distributes a free SIP proxy for Windows. It's easy to get up and running, but my testing has been somewhat limited. They also have a User Support forum where the ININ developers will answer your questions directly.
http://www.inin.com/sipproxy/ will get you there.
NB: I am not affiliated with ININ.
Your dream come true?
NB: I haven't tried one of these devices myself.
Just guessing here (well, I did sniff some packets with Ethereal) but I think that the negotiation is done using an open (3rd party) host -- so the call setup is not necessarily P2P. But, the RTP packets flowing between me and my callee were definitely end-to-end, P2P.
This is probably counting on the fact that most home firewalls use fully conic NATting.
I'm also guessing that the signaling and media are using the same port, unlike most (all?) other VoIP protocols. This saves the desginers from having to worry about keeping two NAT bindings alive.
Apple uses SIP in its iChat AV software. "Kazaa" implementing this in their Skype software is mentioned in the article (in reference to a question regarding Pulver's FWD).
I agree with the parent poster -- I had a lot of noise in mp3 files imported directly into Final Cut Pro 3; when I converted them to AIFF first, then imported them the noise disappeared.
Upside down tabs... hmm...
BATS??
Very recently (within the past month?) ticketmaster.com has begun using gimpy-styled captchas, presumably to prevent automated ticket-buying applications.
Anyone know of any other "mainstream" sites using these tests?
I'm not exactly sure when or where N^N was introducted to this line of discussion. I was refering to N! which, although related to N^{nth power}, actually increases faster than N^{nth). Perhaps I am wrong.
Yep, I think so. It's 4:30am here, so I may be a bit fuzzy-headed... but I think N^N increases MUCH faster than N!
1! = 1, 1^1 = 1
2! = 2, 2^2 = 4
3! = 6, 3^3 = 27
4! = 24, 4^4 = 256... etc.
In fact, N^N >>> N!
Wow... looks as though each student can have 1.67Gb/s if they divide up the bandwidth equally.
And their connection is 1,000 times faster than my broadband? I thought my broadband was capable of 10Mb/s(?)
If you look closely at the Quicktime animation on the page describing the Server Management software, one of the frames shows that the server is running Mac OS X Server 10.1.5.