Whoa. I didn't realize what I said was so controversial. OK, my opinion, in short: It's better to try to maintain things as the original author intended them to be viewed, out of courtesy for the original author. If you want to provide a link to the printer friendly version, that's all well and good, but you should make your primary link be to the ad-infested article. Something like According to the story[Printer friendly] would be OK, in my opinion.
Obviously, there are some cases where the author's originally intended view conflicts with the best way to read the page. In this case, it's a judgement call of whether the courtesy of maintaining the author's intentions outweigh the difficulties caused by maintaining those intentions.
I am not saying "You have to watch the commercials, because there is an implicit social contract", or anything silly like that. I mean, does anyone think that way?
Yeah, the printable version is usually much nicer, but it's more polite (to the people who wrote the article) to link to the ad-infested version. They need to make a buck too.
I was thinking about this a week ago, how to implement, etc. But it all came down to, "I don't have the time Right Now. Maybe when I finish my current project."
Anyway, some ideas I had:
Keep everything encrypted. Only you and the other node (including relay nodes) need to see it.
Relay nodes. You set up your node to provide a minimum of two listen nodes for the stream that you're listening to, and possibly one (or more) listen node(s) for something you aren't listening to.
Multi-source listening. You download portions of the stream you're listening to from multiple nodes.
Have the original station node keep track of how many songs you have served (for originating streams only). Use this as a ploy to tell the RIAA, "see, I have been keeping records of how much I owe you, I just haven't hit $10 yet. I was going to cut you a check as soon as I did."
Have the number of songs you have served (as an originating node) be easily modifiable (or self modifying in some controlled manner) in the client program, so that it can't be taken as evidence against you in the courts. This idea needs some fleshing out.
Up play the non-copyright infringing points of the program. "Anyone can serve a popular internet radio station and not have to pay an arm and a leg for bandwidth."
Swarm/Crowds like peering, to maintain anonymity.
Have the ability to register/digitally sign station names, and have "plain English" names for the radio stations, to prove authenticity, but not reveal your identity.
Station ratings. (How?)
That's all I can remember coming up with right now. There may have been more ideas that I can't remember right now.
Perhaps we need a new version of the GPL that says "you can't have signatures of the executable be required by the hardware" or something along those lines.
That was pretty much my point. Just because some interface is new and wonderful, does not mean it's suited for every task. Eye tracking is perfect for aiming. Finger triggers for firing, (or maybe some kind of touch screen). Foot pedals for steering. Any kind of "five seconds ago" things would be for voice control, ie "chaff" or "decoy".
Obviously, a lot of thought would have to go into interface design, and I probably missed quite a few things. Probably the best way to figure out what goes where would be to have a simulator where you can define bindings, and then track what bindings the most successful people come up with, and base your work on those. Of course, factoring in bias from previous experience in piloting of any kind.
Blinking doesn't quite work. The human eye naturally blinks very frequently. Easier way to do this is just to have normal buttons. I know it's not glamorous, but it works.
My favourite/em VC++ism is when VC++ crashes, but maintains the file lock on the project file that was open at the time of the crash. Again, the only way to fix it is to use the magic button on the case.
The majority of websites run Apache. If J.Q. Public can't access the the majority of the web, he's going to complain, and possibly return his computer as being defective.
His bill would allow copyright holders to set up decoy files and use other techno-tricks like file-blocking and redirection to throw P2P pirates off the trail, but it would forbid those holders from employing tactics that would damage or destroy pirates' own computer systems.
This seems to be the core of the article. Dud files are one thing, but it seems they are also plotting things like file-blocking and redirection. File blocking seems simple enough. Search requests would route around the damaged nodes. No problem there. But redirection seems a bit more frightening. There is potential for a network DoS there. Respond to all search requests that contain "britney spears" with a resulting "britney spears-whatever the fuck her latest song is.mp3" at the IP of "riaa-sucks.org", or whatever the currently popular anti-riaa site is.
Actually, they don't allow the login name cypherpunks anymore. Nor do they allow cypherpunks1, cypherpunks2, cypherpunks99, cypherpunks742, cypherpunks999,... They do allow cypherpunks followed by four digits, but some of those may be taken.
Re:currency tracking hardly needs rfids
on
Greenbacks No More
·
· Score: 1
Actually, I find the prospect of this rather frightening. This makes hard currency much less anonymous than it is now.
This would be the case if you were using a hub, but not if you're using a switch. With a switch, each node has access to the full bandwidth of the network.
(There are some other issues at work here, but in general, this holds true.)
Real time games don't have to be executed entirely in real time. You calculate the next n clicks for your unit, and only recalculate if there are significant changes in the local environment, otherwise you have those moves already calculated, and you use some fancy queue system to manage who gets another slice of CPU next.
I could be wrong, but I always took strong and weak AI to mean that you either encode many rules yourself, and derive the AI from that, or you encode a few simple rules, then teach that system the stronger rules.
Re:That reminds me of an entry from the Jargon Fil
on
Spy v. Spy
·
· Score: 1
One of my favourite algorithms is one I found in Programming Pearls. Basically, using a bitfield to sort numbers in constant time, O(n), given that the numbers are unique. Something like:
for i=MIN to MAX
aout[ i ] = 0
for i=0 to n
aout[ ain[i] ] = 1
for i=MIN to MAX
if aout[i] == 1
Do whatever with the now sorted output
The hosts are in use for non-mmorg use, oddly enough. Inside these hosts people playing mundane card games have existence in a 3D world because the message passing paradigm is great... but they don't move in the 3D space and essentially sit in a matrix keeping track of an unpresented 3D position in the world.
I'm suddenly getting visions of people sitting, chained in a cave, watching shadows thrown against the cave wall, completely oblivious.
There is another problem with this idea. Namely, languages are easier to analyze than mathematical cryptosystems, for a number of reasons.
Languages are believed to have "deep structures", which are common to all languages. This would mean that you could figure out the nouns and verbs and such in the language with a bit of work.
Even without these deep structures, you will eventually come up with a list of words, and you can then use conventional information theory to attach meanings to those words. (ie. you notice some words occur more often just before some action.)
There are other ways to analyze a language, but IANAL (linguist), and I don't have any books readily available ATM.
Slashdot Mirror
Whoa. I didn't realize what I said was so controversial. OK, my opinion, in short: It's better to try to maintain things as the original author intended them to be viewed, out of courtesy for the original author. If you want to provide a link to the printer friendly version, that's all well and good, but you should make your primary link be to the ad-infested article. Something like According to the story [Printer friendly] would be OK, in my opinion.
Obviously, there are some cases where the author's originally intended view conflicts with the best way to read the page. In this case, it's a judgement call of whether the courtesy of maintaining the author's intentions outweigh the difficulties caused by maintaining those intentions.
I am not saying "You have to watch the commercials, because there is an implicit social contract", or anything silly like that. I mean, does anyone think that way?
(Note: I use the term author rather loosely.)
Yeah, the printable version is usually much nicer, but it's more polite (to the people who wrote the article) to link to the ad-infested version. They need to make a buck too.
He could probably join the project as an advisor, as long as he didn't write any code, and not break the "clean-roomliness" of the code.
Of course this wouldn't be as much of an issue if bnet wasn't being sued.
I was thinking about this a week ago, how to implement, etc. But it all came down to, "I don't have the time Right Now. Maybe when I finish my current project."
Anyway, some ideas I had:
That's all I can remember coming up with right now. There may have been more ideas that I can't remember right now.
Not transmitters. Cache/proxy according to the DMCA.
Perhaps we need a new version of the GPL that says "you can't have signatures of the executable be required by the hardware" or something along those lines.
That was pretty much my point. Just because some interface is new and wonderful, does not mean it's suited for every task. Eye tracking is perfect for aiming. Finger triggers for firing, (or maybe some kind of touch screen). Foot pedals for steering. Any kind of "five seconds ago" things would be for voice control, ie "chaff" or "decoy".
Obviously, a lot of thought would have to go into interface design, and I probably missed quite a few things. Probably the best way to figure out what goes where would be to have a simulator where you can define bindings, and then track what bindings the most successful people come up with, and base your work on those. Of course, factoring in bias from previous experience in piloting of any kind.
Blinking doesn't quite work. The human eye naturally blinks very frequently. Easier way to do this is just to have normal buttons. I know it's not glamorous, but it works.
My favourite/em VC++ism is when VC++ crashes, but maintains the file lock on the project file that was open at the time of the crash. Again, the only way to fix it is to use the magic button on the case.
The majority of websites run Apache. If J.Q. Public can't access the the majority of the web, he's going to complain, and possibly return his computer as being defective.
His bill would allow copyright holders to set up decoy files and use other techno-tricks like file-blocking and redirection to throw P2P pirates off the trail, but it would forbid those holders from employing tactics that would damage or destroy pirates' own computer systems.
This seems to be the core of the article. Dud files are one thing, but it seems they are also plotting things like file-blocking and redirection. File blocking seems simple enough. Search requests would route around the damaged nodes. No problem there. But redirection seems a bit more frightening. There is potential for a network DoS there. Respond to all search requests that contain "britney spears" with a resulting "britney spears-whatever the fuck her latest song is.mp3" at the IP of "riaa-sucks.org", or whatever the currently popular anti-riaa site is.
A little bit of research shows up this on how google sets works. There's a link on the bottom of that message for an introduction to faceted sets.
And now for the fun bit. Looking for set with just the keyword Porn, I got some very interesting results:
Predicted ItemsPorn
Warez Sites
pirated software
Irc Bots
Mp3
Spamming Software
Actually, they don't allow the login name cypherpunks anymore. Nor do they allow cypherpunks1, cypherpunks2, cypherpunks99, cypherpunks742, cypherpunks999, ... They do allow cypherpunks followed by four digits, but some of those may be taken.
Actually, I find the prospect of this rather frightening. This makes hard currency much less anonymous than it is now.
They already do. Publish a security hole, and they send their military grade Jack Booted Thugs (tm) to your door.
O'Reilly is considering charging paper recycling companies a royalty for every sheet of recycled paper they sell.
This would be the case if you were using a hub, but not if you're using a switch. With a switch, each node has access to the full bandwidth of the network.
(There are some other issues at work here, but in general, this holds true.)
Real time games don't have to be executed entirely in real time. You calculate the next n clicks for your unit, and only recalculate if there are significant changes in the local environment, otherwise you have those moves already calculated, and you use some fancy queue system to manage who gets another slice of CPU next.
I could be wrong, but I always took strong and weak AI to mean that you either encode many rules yourself, and derive the AI from that, or you encode a few simple rules, then teach that system the stronger rules.
for i=MIN to MAX
aout[ i ] = 0
for i=0 to n
aout[ ain[i] ] = 1
for i=MIN to MAX
if aout[i] == 1
Do whatever with the now sorted output
I'm suddenly getting visions of people sitting, chained in a cave, watching shadows thrown against the cave wall, completely oblivious.
- Languages are believed to have "deep structures", which are common to all languages. This would mean that you could figure out the nouns and verbs and such in the language with a bit of work.
- Even without these deep structures, you will eventually come up with a list of words, and you can then use conventional information theory to attach meanings to those words. (ie. you notice some words occur more often just before some action.)
There are other ways to analyze a language, but IANAL (linguist), and I don't have any books readily available ATM.Well, of course there is the old _2001_ setup. Using centrifugal force to simulate gravity. (yeah, yeah, centripetal force...)