This discussion would make any sense if ICQ had anything to do with Israel. ICQ has nothing to do with Israel. It is not hosted in Israel. It is an America Online service and has not had anything to do with Israel since 1996.
ICQ is not based or even hosted in Israel. It has been hosted by AOL for the past dozen years, the first two of which it was hosted in New York, not Israel. Ubique was founded in Israel and once hosted ICQ in Israel but this was 1996 and earlier. Nothing about ICQ operations now has anything to do with Israel.
ICQ hasn't been based in Israel for more than a decade. Before that, its main "data center" was an office in New York. Since then, it's been in America Online's data centers spread mostly in the US and several non-US locations, none of which are Israel. Ubique was founded in Israel. That's about all you can say about Israel and ICQ in the past dozen years or so.
And during your interview, when you mention the phrase "I've been doing this professionally for seventeen years..." the conversation shifts to how subtly and quickly you can be shown the door.
Again, as I keep saying, the "underlying protocol" is not HTTP, it's ICY. The only part of the protocol that even remotely could be called HTTP is the initial exchange of headers on the beginning of the connection. It is not HTTP. Ask any company that tried to treat Shoutcast streams as HTTP and you'll find out it's not at all like HTTP. In addition to the interleaved metadata there are control signals sent back and forth and they're completely not anything like HTTP, either.
I agree, yet by the time they bought them, Netscape was a sad shell of company that didn't know it was dead yet. Nobody was going to Netscape.com by that time, and AOL tried to integrate as much of the My Netscape product into the failed My AOL product and actually brought My AOL back from the dead on iPlanet server. Traffic kept dropping over at Netscape.com and they finally put it out of its misery and redirected people to a somewhat revitalized My AOL product with the "Netscape" brand "chrome" on it. After all this, My AOL features were blended with AOL.COM and it survived to some success over the years. Today you go to my.netscape.com and it is my.aol.com with a Netscape "skin" running on a combination of Apache and AOLserver servers, the latter being an open-source project since 1999. -another ex-AOL employee.
The letters all refer to something called the "Shoutcast Radio." This is the free, yet proprietary, directory of people using Shoutcast servers to serve audio data. I don't see anything that talks about the protocol itself, which is open and is used to serve audio to tens of millions of iPhone/iPad/iPod Touch users via apps like iheartradio, CBS Radio, and many others.
This isn't such a big deal but I sure hope the VLC people don't think it means they should remove the Shoutcast streaming protocol, which it pretty clearly does NOT refer to.
Not true. It is not even HTTP. It's its own protocol and just uses HTTP-like headers to handshake the start of the connection. Think of Shoutcast as a media container and the music file as the data. The server takes the ID3 tags and remembers them, then interleaves them with the audio data. In fact it is not just MP3: it is more common to be AAC today.
When you tune to a Shoutcast stream the name of the song appears even when in the middle of the song. You can't do that without interleaving the song data with the stream, which is not supported in MP3 nor AAC for that matter. It's the Shoutcast/ICEcast/ICY protocol. It's not HTTP. It's ICY.
I would even argue that the injunction is aimed at the use of Shoutcast Radio which is the online directory of Shoutcast streams that AOL aggregates and serves to Shoutcast Radio users. I don't believe the injunction talks about the Shoutcast protocol itself, either, which is also implemented in a free version under the name ICEcast and it's still used by lots of people including Ogg Vorbis.
Yes, the article and the C&D letters appear to be about the directory service provided by Shoutcast, called Shoutcast Radio. This is separate from Shoutcast, the protocol. The quoted sections posted over at the VLC web site specifically say "Shoutcast Radio" so it's reasonable to think they're talking about the directory service, not the streaming protocol. The protocol itself for streaming the audio is open, and AOL even tried to promote it under the name "Ultravox" and it never seemed to get anywhere. But all I see that the VLC site is talking about is Shoutcast Radio, the directory service.
It's also important to know that the protocol behind Shoutcast serves way more than half a million people. Most iPhone Apps that receive streaming audio are receiving them via the Shoutcast streaming protocol even if they're not using the Shoutcast Radio directory. In many cases the ICEcast open-source implementation of Shoutcast is what's being used. Let's see, CBS Radio (AOL and Yahoo Radio), AMFM's iheartradio, and so many others are using something very much like the Shoutcast protocol, once and no longer known as "Ultravox," for serving iPhone, iPod Touch, and iPad clients. I don't know about Android but I would suspect they're using ICEcast since it's the one supported by the Ogg Vorbis crowd, too.
Shoutcast/ICEcast ICY protocol is in so many more places than people know. It might not be purely AOL's Shoutcast by Nullsoft, but it's someting mighty close to it, serving tens of millions of people.
We don't need the Shoutcast Radio directory. That's the technology in question from what I'm reading at VLC's web site.
It's important to note the existing, efficient commercial solutions out there. The government-supplied rockets can be replaced with commercial versions.
Just like you hit the "Junk" button on email, you hit the "Junk" button when you see someone's junk on ChatRoulette. The system records the number of "Junk" hits on that user's camera per N second period, and, voila, problem solved for that session. Even better, pop up fake users to the Junksters so they stay on one camera for the rest of their session.
You're over three days late. Your unnecessary ad hominem attack, and your sarcasm betrays your obvious ignorance about the Windows Home Server platform and show all of us that you are not qualified for this debate.
Linus said repeatedly that filesystem dumps are bad for reasons he is obviously not qualified to evaluate, but people believed him, and ext3 has no real support for dumps for NO GOOD REASON.
My Windows Home Server disagrees with you completely. I only wish something similar to WHS with Volume Shadow Copy Provider could possibly exist for Linux. I'm tired of waiting. You really should open your eyes and see that what you're describing is not only outdated but dangerously untrue.
Be careful which SIP adapter you choose. I have yet to find one that can power a ringer on these old phones, let alone a high-powered, old-school headset.
Slashdot Mirror
Of course, by "Ubique" I mean Mirabilis. I got my Israeli AOL acuisitions mixed up, but of course ICQ has nothing to do with Israel since 1996.
This discussion would make any sense if ICQ had anything to do with Israel.
ICQ has nothing to do with Israel. It is not hosted in Israel. It is an America Online service and has not had anything to do with Israel since 1996.
ICQ is not based or even hosted in Israel. It has been hosted by AOL for the past dozen years, the first two of which it was hosted in New York, not Israel.
Ubique was founded in Israel and once hosted ICQ in Israel but this was 1996 and earlier. Nothing about ICQ operations now has anything to do with Israel.
ICQ hasn't been based in Israel for more than a decade.
Before that, its main "data center" was an office in New York.
Since then, it's been in America Online's data centers spread mostly in the US and several non-US locations, none of which are Israel.
Ubique was founded in Israel. That's about all you can say about Israel and ICQ in the past dozen years or so.
And during your interview, when you mention the phrase "I've been doing this professionally for seventeen years..." the conversation shifts to how subtly and quickly you can be shown the door.
It happens, and shame on those who do this to us.
Again, as I keep saying, the "underlying protocol" is not HTTP, it's ICY. The only part of the protocol that even remotely could be called HTTP is the initial exchange of headers on the beginning of the connection. It is not HTTP. Ask any company that tried to treat Shoutcast streams as HTTP and you'll find out it's not at all like HTTP. In addition to the interleaved metadata there are control signals sent back and forth and they're completely not anything like HTTP, either.
I agree, yet by the time they bought them, Netscape was a sad shell of company that didn't know it was dead yet. Nobody was going to Netscape.com by that time, and AOL tried to integrate as much of the My Netscape product into the failed My AOL product and actually brought My AOL back from the dead on iPlanet server. Traffic kept dropping over at Netscape.com and they finally put it out of its misery and redirected people to a somewhat revitalized My AOL product with the "Netscape" brand "chrome" on it. After all this, My AOL features were blended with AOL.COM and it survived to some success over the years. Today you go to my.netscape.com and it is my.aol.com with a Netscape "skin" running on a combination of Apache and AOLserver servers, the latter being an open-source project since 1999. -another ex-AOL employee.
The letters all refer to something called the "Shoutcast Radio." This is the free, yet proprietary, directory of people using Shoutcast servers to serve audio data. I don't see anything that talks about the protocol itself, which is open and is used to serve audio to tens of millions of iPhone/iPad/iPod Touch users via apps like iheartradio, CBS Radio, and many others.
This isn't such a big deal but I sure hope the VLC people don't think it means they should remove the Shoutcast streaming protocol, which it pretty clearly does NOT refer to.
Not true. It is not even HTTP. It's its own protocol and just uses HTTP-like headers to handshake the start of the connection. Think of Shoutcast as a media container and the music file as the data. The server takes the ID3 tags and remembers them, then interleaves them with the audio data. In fact it is not just MP3: it is more common to be AAC today.
When you tune to a Shoutcast stream the name of the song appears even when in the middle of the song. You can't do that without interleaving the song data with the stream, which is not supported in MP3 nor AAC for that matter. It's the Shoutcast/ICEcast/ICY protocol. It's not HTTP. It's ICY.
I would even argue that the injunction is aimed at the use of Shoutcast Radio which is the online directory of Shoutcast streams that AOL aggregates and serves to Shoutcast Radio users. I don't believe the injunction talks about the Shoutcast protocol itself, either, which is also implemented in a free version under the name ICEcast and it's still used by lots of people including Ogg Vorbis.
Here's more for you to read:
http://en.wikipedia.org/wiki/Ultravox_(software)
Yes, the article and the C&D letters appear to be about the directory service provided by Shoutcast, called Shoutcast Radio. This is separate from Shoutcast, the protocol. The quoted sections posted over at the VLC web site specifically say "Shoutcast Radio" so it's reasonable to think they're talking about the directory service, not the streaming protocol. The protocol itself for streaming the audio is open, and AOL even tried to promote it under the name "Ultravox" and it never seemed to get anywhere. But all I see that the VLC site is talking about is Shoutcast Radio, the directory service.
It's also important to know that the protocol behind Shoutcast serves way more than half a million people. Most iPhone Apps that receive streaming audio are receiving them via the Shoutcast streaming protocol even if they're not using the Shoutcast Radio directory. In many cases the ICEcast open-source implementation of Shoutcast is what's being used. Let's see, CBS Radio (AOL and Yahoo Radio), AMFM's iheartradio, and so many others are using something very much like the Shoutcast protocol, once and no longer known as "Ultravox," for serving iPhone, iPod Touch, and iPad clients. I don't know about Android but I would suspect they're using ICEcast since it's the one supported by the Ogg Vorbis crowd, too.
Shoutcast/ICEcast ICY protocol is in so many more places than people know. It might not be purely AOL's Shoutcast by Nullsoft, but it's someting mighty close to it, serving tens of millions of people.
We don't need the Shoutcast Radio directory. That's the technology in question from what I'm reading at VLC's web site.
Have we forgotten about Pegasus from Orbital?
http://www.orbital.com/SpaceLaunch/
It's important to note the existing, efficient commercial solutions out there. The government-supplied rockets can be replaced with commercial versions.
Why not just a "Junk" button?
Just like you hit the "Junk" button on email, you hit the "Junk" button when you see someone's junk on ChatRoulette. The system records the number of "Junk" hits on that user's camera per N second period, and, voila, problem solved for that session. Even better, pop up fake users to the Junksters so they stay on one camera for the rest of their session.
You're over three days late. Your unnecessary ad hominem attack, and your sarcasm betrays your obvious ignorance about the Windows Home Server platform and show all of us that you are not qualified for this debate.
Move along; you cannot be taken seriously.
I dunno, someone I know said extents mattered. *shrug*
Good luck with your project, btw.
I'm talking about extents and extended attributes and other data not available to userspace. I was not talking about just POSIX filesystem data.
I totally understand what Linus says.
The real world fails to agree with him.
Filesystem dumps are good. There is important metadata that is not preserved using cpio and, hahah, you actually said "tar." Now THAT is funny.
Linus said repeatedly that filesystem dumps are bad for reasons he is obviously not qualified to evaluate, but people believed him, and ext3 has no real support for dumps for NO GOOD REASON.
http://lwn.net/2001/0503/a/lt-dump.php3
There should be a Godwin's Law against quoting Linus in an argument.
My Windows Home Server disagrees with you completely.
I only wish something similar to WHS with Volume Shadow Copy Provider could possibly exist for Linux. I'm tired of waiting.
You really should open your eyes and see that what you're describing is not only outdated but dangerously untrue.
"You can make money without doing evil."
Really?
How's that working out for you?
http://www.google.com/intl/en/corporate/tenthings.html
Be careful which SIP adapter you choose. I have yet to find one that can power a ringer on these old phones, let alone a high-powered, old-school headset.
Also available in hands-free!! http://www.scscr.org/images/lisa.jpg
The Stenomask!! The picture needs no description. http://www.scscr.org/mediac/400_0/media/Misc$20110.jpg
I see that you did *not* get it.
Thanks for failing to let us know how smart you think you are.
Apogee code word--did you get it?
I like the Motorola GMRS radios, too.
Wait. What?