This would put the EFF (or whoever) in a very sticky legal situation. The press would portray it as "helping hackers to steal Megasoft's intellectual property" - they would not see the distinction between this and a warez site.
Unless everyone who works on the infringing project is careful about attaching copyright notices to every CVS commit, attributing ownership of the work to the FSF, they will simply sue the individual whom they judge to have crossed the line between a non-infringing work and an infringing work. They have never denied that individuals can be sued.:(
I'm afraid Perl looks like randomly-generated ASCII to me, so I can't check out your source code, but I'd be interested to know whether you attach any extra data (like tempo and mood) to each song, or just keep track of each individual track and how often it is skipped, after which tracks, etc?
Sorry, I didn't express that very well, but I have Skinny Puppy playing in my ears at the moment.;)
I run Gnome, compiled from tarballs, on a Red Hat 5.2 box. It works fine. Just make sure you use up-to-date versions of glib, gtk and GIMP, removing the Red Hat RPMs of those packages before you start compiling them.
Resizing is the window manager's responsibility - ie, it's an E bug, not a Gnome one. It might only occur under Gnome, but that doesn't make it Gnome's fault.:)
I think the comparison to analogue synthesis stemmed from the use of combinations of simple algorithms, rather than tables of coordinates, to produce a complex texture.
An analogue synth has oscillators which produce simple tones such sine, triangle and square waves. By combining them using simple circuits such as ring modulators, envelope generators and resonant filters, it produces complex sounds. You only need a tiny amount of information to describe all the settings on an analogue synth (a "patch").
Early digital synths used wavetables (or samples) to produce complex sounds. This makes it easier to reproduce the sound of a real instrument (you just sample it and then play it back), but the patches are much larger.
(To complicate matters, many digital synths now emulate analogue synths using software models.)
Polygon-based graphics are similar to wavetable synthesis - you use a table of points to reconstruct a surface by drawing straight lines (or curves, if you have the processing power to spare) between each point and the next. 3D worlds created in this way require a lot of memory to store, or a lot of bandwidth to transmit.
Speculative part:
Psi seems to use combinations of simple waveforms to generate 3D worlds. I imagine this would generate random rolling terrain very nicely, but it would be hard to design a landscape "to order". I suppose you would design it using conventional 3D software, and then use Fourier analysis to extract the fundamental waveforms from the complex surfaces. Then you just send (or store) those waveforms, and the rendering engine has the much easier job of just recombining them.
I wonder if this technology could be used to create a new generation of samplers which would sample a sound, take it apart using Fourier analysis or whatever, and work out how to reconstruct it using simple waveforms? That would be very useful for increasing the capacity of samplers (and audio CDs, portable digital music players etc.).
But if you want to play, say, Quake III you might need all the CPU time you can get. You don't want an MP3 decoder eating into it (which is why I'm content to switch CDs every hour rather than encoding my whole music collection onto one CD).
The more insane the US patent office gets, the sooner its insanity will be recognised. I don't think the people of the world are going to be very happy when they work out that a US company owns all the patents from the Human Genome Project, and therefore has intellectual property rights over the DNA of every person on earth.
I want everyone to check the code out, find the bugs, try to crack it. Once it stands up to all that, I'll use it. I can't just trust Intel to do my homework for me.
But you can trust every cracker out there who can get a copy of the source code, right? Don't forget, not everyone who can read code wants to fix the bugs they find. Some people want to exploit them, and making the code available makes it that much easier.
I think open source/free software is a fine and noble idea, but it isn't a panacea.
Sounds like a good idea - hardware vendors are slowly starting to see the sense of open standards, but a kick up the backside wouldn't slow them down. Moderate up!
Re:Gov't must accept the death of wiretapping.
on
CALEA update
·
· Score: 2
What's more is that a single communications may not even flow through the same cable. It can be packetized and take 1000 routes and reassemble at the other end
At the moment I believe the FBI are restricted to tapping lines belonging to specific suspicious individuals. Could this property of packet comms be used as justification for tapping *all* lines?
90% of people have Microsoft OSs on their desktop machines. IBM and Sun are competing for the server market, where there is a more even split between NT and Unices.
Slashdot Mirror
"We might be able to nuke them...."
;)
...from orbit, it's the only way to be sure.
Q: Why don't sharks eat lawyers?
A: Professional courtesy.
Q: What do you call 10,000 lawyers at the bottom of the ocean?
A: A good start.
This would put the EFF (or whoever) in a very sticky legal situation. The press would portray it as "helping hackers to steal Megasoft's intellectual property" - they would not see the distinction between this and a warez site.
Unless everyone who works on the infringing project is careful about attaching copyright notices to every CVS commit, attributing ownership of the work to the FSF, they will simply sue the individual whom they judge to have crossed the line between a non-infringing work and an infringing work. They have never denied that individuals can be sued. :(
I'm afraid Perl looks like randomly-generated ASCII to me, so I can't check out your source code, but I'd be interested to know whether you attach any extra data (like tempo and mood) to each song, or just keep track of each individual track and how often it is skipped, after which tracks, etc?
;)
Sorry, I didn't express that very well, but I have Skinny Puppy playing in my ears at the moment.
Another 70 Gb drive. Otherwise you're going to be changing DATs all night...
Why does this remind me of a chain letter?
I run Gnome, compiled from tarballs, on a Red Hat 5.2 box. It works fine. Just make sure you use up-to-date versions of glib, gtk and GIMP, removing the Red Hat RPMs of those packages before you start compiling them.
Looks like they don't have power supply or control electonics onboard. :(
:p
And they have eight legs => not insects.
Resizing is the window manager's responsibility - ie, it's an E bug, not a Gnome one. It might only occur under Gnome, but that doesn't make it Gnome's fault. :)
I think the comparison to analogue synthesis stemmed from the use of combinations of simple algorithms, rather than tables of coordinates, to produce a complex texture.
An analogue synth has oscillators which produce simple tones such sine, triangle and square waves. By combining them using simple circuits such as ring modulators, envelope generators and resonant filters, it produces complex sounds. You only need a tiny amount of information to describe all the settings on an analogue synth (a "patch").
Early digital synths used wavetables (or samples) to produce complex sounds. This makes it easier to reproduce the sound of a real instrument (you just sample it and then play it back), but the patches are much larger.
(To complicate matters, many digital synths now emulate analogue synths using software models.)
Polygon-based graphics are similar to wavetable synthesis - you use a table of points to reconstruct a surface by drawing straight lines (or curves, if you have the processing power to spare) between each point and the next. 3D worlds created in this way require a lot of memory to store, or a lot of bandwidth to transmit.
Speculative part:
Psi seems to use combinations of simple waveforms to generate 3D worlds. I imagine this would generate random rolling terrain very nicely, but it would be hard to design a landscape "to order". I suppose you would design it using conventional 3D software, and then use Fourier analysis to extract the fundamental waveforms from the complex surfaces. Then you just send (or store) those waveforms, and the rendering engine has the much easier job of just recombining them.
I wonder if this technology could be used to create a new generation of samplers which would sample a sound, take it apart using Fourier analysis or whatever, and work out how to reconstruct it using simple waveforms? That would be very useful for increasing the capacity of samplers (and audio CDs, portable digital music players etc.).
Lets face it, in porn quality doesn't really matter, as long as your not asking your self the question "Is that a nipple or an anus?"
;)
And to some of us, even that doesn't matter
Knowledgible people. Heh.
It now supports HTML 3.2 and JavaScript.
But if you want to play, say, Quake III you might need all the CPU time you can get. You don't want an MP3 decoder eating into it (which is why I'm content to switch CDs every hour rather than encoding my whole music collection onto one CD).
The more insane the US patent office gets, the sooner its insanity will be recognised. I don't think the people of the world are going to be very happy when they work out that a US company owns all the patents from the Human Genome Project, and therefore has intellectual property rights over the DNA of every person on earth.
I want everyone to check the code out, find the bugs, try to crack it. Once it stands up to all that, I'll use it. I can't just trust Intel to do my homework for me.
But you can trust every cracker out there who can get a copy of the source code, right? Don't forget, not everyone who can read code wants to fix the bugs they find. Some people want to exploit them, and making the code available makes it that much easier.
I think open source/free software is a fine and noble idea, but it isn't a panacea.
Sounds like a good idea - hardware vendors are slowly starting to see the sense of open standards, but a kick up the backside wouldn't slow them down. Moderate up!
What's more is that a single communications may not even flow through the same cable. It can be packetized and take 1000 routes and reassemble at the other end
At the moment I believe the FBI are restricted to tapping lines belonging to specific suspicious individuals. Could this property of packet comms be used as justification for tapping *all* lines?
It is not much slower either.
If the computer hangs, it's a kernel issue. ;)
Small plugin modules are going to take their power from the Visor.
See the recent /. article on wearable computers. They now have a VDU that looks like a pair of wraparound sunglasses.
They put jazz music in their commercials. Much hipper than their previous jingle, a recording of a daisywheel printer typing "We are the future" IIRC.
90% of people have Microsoft OSs on their desktop machines. IBM and Sun are competing for the server market, where there is a more even split between NT and Unices.