The internet goes back to around 1970, but TCP/IP was invented in 1983. This gave us truely scalable routing and a seperate (therefore optional) transfer layer. The internet wouldn't be able to do all the useful things it does now if it still ran NCP.
It should be "Alvin Maker", using his profession as a surname, as with "Alvin Miller" and "Alvin Smith". The fact that they got these wrong bodes poorly for the MMORPG, in my opinion.
I also suspect the universe will adapt itself poorly, as everyone will want unreasonably powerful knacks, some of which (eg torches) can't be satisfied by the game engine.
IIRC, mplayer can read realaudio format (using a free-as-in-beer binary x86/PPC/Alpha plugin) and output WAV. If you tell it to use a named FIFO as its output file, you should be able to use it as a conversion filter in front of the broadcasting software with a minor (<1sec) time lag.
For that matter, mplayer with FIFOs and a little CGI may make an adequate ad-hoc solution, though I suspect real-time MP3 encoding is a lot trickier, and a package designed for that might be a good idea.
Here's the problem. Not many people care about controlling their computer in the sense that he's blabbing on about.
They will once their computer betrays them enough.
We're just beginning to see the possibilities of malware. Even the most tech-illiterate are unhappy about programs sneaking onto their computers to spy on them, disrupt their work and forward spam. Most likely, future malware will commit credit card fraud and participate in DDOS attacks while framing the original victim. People will care.
To a limited extent, restricting your software to reputable sources can help, but not enough. Cisco once admitted to including backdoors in enterprise-targetted products (they apologized and called it an accident). Microsoft is known to manipulate compatibility against consumers best interests in order to crush their rivals. This is subtler, but it may get worse.
RMS isn't totally out of touch on this; he's just a little ahead of his time.
It is possible to modify your file dialog without recompiling everything every time. You do need to recompile everything once. Make sure you get the source for the exact same version you have, and compile it all to get the.o files.
After that, make your changes to gtk-file-selector.c and make libgtk-x11-2.whatever, then copy that file into/usr/lib or wherever your gtk lives. You should probably back up your old version first.
Check out this selector before you start implementing your own. You may find ideas or code you want to copy.
Almost the entire highlands surface is composed of plagioclase. You can extract glass and maybe aluminum from that. You might be able to create dopes silicates for electronics, but you'd probably need to bring trace elements from earth. The Mare are a little better: they're basalt. You can probably get Iron there, maybe some other metals as well. Maybe not. In general, there won't be much in the may of heavy metals, because the moon doesn't have mantle convection and volcanism to make them accessible. It certainly doesn't have hydrocarbons, which we need a lot of.
We could probably mine the moon for a few things, but most of our materials would still come from Earth.
You're right about the publicity effect, but we need to take it one step farther. We can't squeeze the big label musicians out of mindshare because the big music labels are the big news sources (more or less) and have no regret about using the latter channels to promote the former.
What we need to do is use P2P and other systems to publicize independant music. It ought to be possible to create some semi-distributed music recommendation system, preferably combined with free distribution of samples. If anyone would like to work with me on this, e-mail me.
As an ad-hoc beginning, I'm currently listening to The Horse-Tamer's Daughter by Julia Ecklar who I highly recommend.
What difference does it make whether your controller/disk interface is 150MB/s or 320MB/s when your data is going to sit on the controller waiting for the 132MB/s PCI bus anyway?
I'm serious. Is there some way around the PCI bottleneck? Is it not as bad as I think it is? Should we all be using PCI-X anyway?
One other thing that's critical is to monitor status carefully. One of the points of RAID is transparent failure recovery, but the Linux version is too transparent: you can lose a drive and not notice it at all, until a second drive goes (third if you've set up a hot-spare as described) and then you're in trouble.
Probably the best move is to have a cron job examine/proc/mdstat and e-mail you if it's troubled.
Linux uses a fair bit of code like that. So does libvorbis. I'm pretty sure I've seen it elsewhere, too.
Of course, the right way to do this is with exceptions, but implementing them in C is usually more trouble than it's worth. (Not always, go ahead and do it for a large project -- there's probably even a library for it.)
There is a significant cultural difference that will likely continue even if the masses come to GNU/Linux: availability of free software.
Most spyware comes trojaned on to little shareware and 'freeware' utilities that are downloaded to add functionality to windows. In general, these same features are available on GNU/Linux as free software, so there's no need to mess around with untrustable shareware.
Yes, there exists free software for windows, but not with the same ubiquity as GNU/Linux. And yes, an author with sufficient sheer khutzpah could probably insert spyware into free software, but they'd get caught eventually, and whoever caught them would probably DoS them with a patch to give junk data.
GNU/Linux developers just have a strong tradition of not fucking over their users. Even if unscrupulous developers come to GNU/Linux and try to water that down, the responcible developers will still produce enough (as they do now) that the unscrupulous have no opening.
Except that you don't actually lose control. They just make things a little inconvenient. The images are shown in the background, and browsers aren't used to dealing with them.
If you want to download the images, copy the URL from the address bar and enter these commands:
You may wish to rename it to something reasonable. This also doesn't help you download entire books, because the naming of pages is not obvious at all, but if you have an OCR system, you might be able to use it as part of a spider.
Google didn't call it DRM, and there is no encryption at all, so I think this post is legal in the US. IANAL; read at your own risk.
It wouldn't be secure enough to use in court, or for any other important function. It's like DRM -- it would require the camera to slip messages to the court past its owner and against its owner's will. This in turn would require the cmera to be smarter than its owner. I'll admit that many humans are stupider than their electronics, but they can get help from those who are smarter.
On a practical level, all you need to do is pull out the ROM with the camera's private key, attach it to a custom circiut-board and query it directly. That's for a well-designed system.
What law enforcement (and other investigators) may want to do is look at the low-order correlations of adjascent pixels, which are determined mostly by the camera taking the picture. If they don't match they camera, the picture was probably tampered with.
So what's wrong with JPEG 2000? It's a lossless, free compression scheme with similar file sizes to JPEG. There's already an open source implementation even if it's not quite good enough for embedded use.
For that matter, why aren't we seeing J2k everywhere? It looks like a great format.
You can probably get it by thinking about powers of ten and small multiples thereof (and then doing the last bit by hand), but even a slow computer can brute-force it in under a second using 20 lines of C code. I wonder which approach Google prefers?
I think most of us would accept a well-designed e-voting system, which had been cross-checked by multiple independant teams of qualified engineers and field-tested electing a figurehead for 2600. The current batch of voting machines have failed tests like these dismally, and have no practical chance of getting cleaned up by November. Anyone who's programmed knows that building a reliable system takes time: time to do it right and time to test it thoroughly. If the best engineers had been working nonstop since 2000, we might have been ready by now, but they weren't, so we aren't, and we won't be in November.
I personally feal that even if the engineering were right, Diebold would still be disqualified unless they handed over all operations to someone else who'd had the chance to double-check the code (and hardware), because elections should be handled by those committed to neutrality (or, at least, a team with competing sides represented), not by someoen who is "committed to helping Ohio deliver its electoral votes to the president next [sic] year.".
Han: I'm here for the money, and I'm going to get the money.
First Speaker: [looks skepticla]
Han: On second thought, I really just want to be with Leah. Bye!
First Speaker [to novice]: HE'll be a happier man, but he'll never threaten The Plan again.
Novice: Is it always that easy?
First Speaker: Yes
Seems sort of silly, doesn't it?
Really, the power of the Force is nothing compared to the power of psychohistory.
On a similar topic, is there a way to get rid of the "you don't have this plugin; do you want it?" popup? I know I don't have the plugin; I don't want it! Every page with a flash banner ad now has a popup, despite popup-blocking!
The reason these things can't really be dangerous is simple: if they were, the TSA wouldn't let us bring them at all.
If it were possible to generate RF to cripple an airplane with a device the size of a laptop powered by ordinary batteries, it would be simple to delibrately build such a device and slap an "IBM Thinkpad" sticker on it. The TSA must realize this, but all they check is to make sure there are no concealed explosives.
>I always assumed the cellphone ban was becaues that many people shouting over the static (and eachother) in an enclosed environmant would be *really* annoying.
Meta tags in wmv files are inside the file. The file is a stream of bytes to the OS, but the application knows how to pick metainformation out. This doesn't make for good searching, becasue you need a lot of applications and you can't really index.
What BeOS did was to add arbitrary metadata to the filesystem itself (I think as a list of pairs of strings) and then index on all of it, so that you could do searches at the OS level. I never used BeOS, but those who did generally say this was very useful.
I think this is where Microsoft's great innovation is copied from. If so, it's not the same as wmv tags. Of course, since it's been delayed, we may never know.
It's probably more effective than preaching to the converted
Not necessarily. Microsoft wants enourmous numbers of people to buy Longhorn (or new computers with Longhorn). Most of those people already run Windows. Microsoft needs to convince the people who are already in their camp to upgrade, much more than they need to recruit new users from Mac, Linux, or non-computer-ownership.
This is a tricky game they're playing. Microsoft was telling Win2k users that they should upgrade to an operating system with a database file system, and is now announcing that they aren't going to provide one soon. This might encourage those people to upgrade to an operating system that already has one (sort of).
I'm sure that if more people help out, we can get that driver fully featured by 2006. Then we just need IBM to pay for a series of TV adds: "Linux: the features Longhorn was supposed to have."
That's just what They want you to think! (The governments, not the terrorists -- actually, the terrorists too.)
My thought as to what we can do is we can all run logging software and see where the attacks (if any) come from; then we can all group our data and trace them to their source. If enough of us get involved, especially if we get a good geographic spread (should be possible) we should be able to nap the culprit before the CIA do. We could discorage terrorism and embariss fascism at the same time!
Recent physical attacks demonstrated that an active populace does better than any government agency (remember the shoe bomber?). This is even more true for cyber-terrorism.
Of course, this all assumes the attack is big enough for us to notice. The internet can route around damage and congestion very effectively.
I guess that'll work, though the requirement to give each command its own file whether it warrents it or not is annoying. It will also be a pain if I want to change the behavior of a command at runtime (I suppose I could remove the command and insert one with the same name -- awkward). It strains the Single Point of Truth Principle because defining commands and inserting them into the used list are seperate. Finally, it's almost twice as long as the C implementation, and C is a verbose language. Using a high level language should shorten code without harming readability. Remember that bugs are proportional to physical lines of code.
As for the Reader classes thing, I stand by my statement. I've been coding Java for three years. If the classes were intelligently designed, I'd have them memorized. The seperation of Readers, FileReaders, BufferedReaders, and all the rest of the relevent classes is a mess. I guess they're trying to imitate the Unix file-descriptor/file-handle distinction, but it's horribly clumsy and since they don't relate to the thread model that way, there's no need for it.
Slashdot Mirror
The internet goes back to around 1970, but TCP/IP was invented in 1983. This gave us truely scalable routing and a seperate (therefore optional) transfer layer. The internet wouldn't be able to do all the useful things it does now if it still ran NCP.
I also suspect the universe will adapt itself poorly, as everyone will want unreasonably powerful knacks, some of which (eg torches) can't be satisfied by the game engine.
For that matter, mplayer with FIFOs and a little CGI may make an adequate ad-hoc solution, though I suspect real-time MP3 encoding is a lot trickier, and a package designed for that might be a good idea.
They will once their computer betrays them enough.
We're just beginning to see the possibilities of malware. Even the most tech-illiterate are unhappy about programs sneaking onto their computers to spy on them, disrupt their work and forward spam. Most likely, future malware will commit credit card fraud and participate in DDOS attacks while framing the original victim. People will care.
To a limited extent, restricting your software to reputable sources can help, but not enough. Cisco once admitted to including backdoors in enterprise-targetted products (they apologized and called it an accident). Microsoft is known to manipulate compatibility against consumers best interests in order to crush their rivals. This is subtler, but it may get worse.
RMS isn't totally out of touch on this; he's just a little ahead of his time.
After that, make your changes to gtk-file-selector.c and make libgtk-x11-2.whatever, then copy that file into /usr/lib or wherever your gtk lives. You should probably back up your old version first.
Check out this selector before you start implementing your own. You may find ideas or code you want to copy.
Almost the entire highlands surface is composed of plagioclase. You can extract glass and maybe aluminum from that. You might be able to create dopes silicates for electronics, but you'd probably need to bring trace elements from earth. The Mare are a little better: they're basalt. You can probably get Iron there, maybe some other metals as well. Maybe not. In general, there won't be much in the may of heavy metals, because the moon doesn't have mantle convection and volcanism to make them accessible. It certainly doesn't have hydrocarbons, which we need a lot of.
We could probably mine the moon for a few things, but most of our materials would still come from Earth.
What we need to do is use P2P and other systems to publicize independant music. It ought to be possible to create some semi-distributed music recommendation system, preferably combined with free distribution of samples. If anyone would like to work with me on this, e-mail me.
As an ad-hoc beginning, I'm currently listening to The Horse-Tamer's Daughter by Julia Ecklar who I highly recommend.
I'm serious. Is there some way around the PCI bottleneck? Is it not as bad as I think it is? Should we all be using PCI-X anyway?
Probably the best move is to have a cron job examine /proc/mdstat and e-mail you if it's troubled.
Of course, the right way to do this is with exceptions, but implementing them in C is usually more trouble than it's worth. (Not always, go ahead and do it for a large project -- there's probably even a library for it.)
Most spyware comes trojaned on to little shareware and 'freeware' utilities that are downloaded to add functionality to windows. In general, these same features are available on GNU/Linux as free software, so there's no need to mess around with untrustable shareware.
Yes, there exists free software for windows, but not with the same ubiquity as GNU/Linux. And yes, an author with sufficient sheer khutzpah could probably insert spyware into free software, but they'd get caught eventually, and whoever caught them would probably DoS them with a patch to give junk data.
GNU/Linux developers just have a strong tradition of not fucking over their users. Even if unscrupulous developers come to GNU/Linux and try to water that down, the responcible developers will still produce enough (as they do now) that the unscrupulous have no opening.
If you want to download the images, copy the URL from the address bar and enter these commands:
URL='url from addressbar'
IMGURL=`lynx --source "$URL" | tr '<>' '\n'|grep background-image:url | sed 's/.*url..//g' | sed 's/..;background-repeat.*//g' | tail -n 1`
lynx --source "$IMGURL" > `echo $i | tr -c '[A-Za-z]' '_'`
You may wish to rename it to something reasonable. This also doesn't help you download entire books, because the naming of pages is not obvious at all, but if you have an OCR system, you might be able to use it as part of a spider.
Google didn't call it DRM, and there is no encryption at all, so I think this post is legal in the US. IANAL; read at your own risk.
On a practical level, all you need to do is pull out the ROM with the camera's private key, attach it to a custom circiut-board and query it directly. That's for a well-designed system.
What law enforcement (and other investigators) may want to do is look at the low-order correlations of adjascent pixels, which are determined mostly by the camera taking the picture. If they don't match they camera, the picture was probably tampered with.
For that matter, why aren't we seeing J2k everywhere? It looks like a great format.
You'll probably want to rename audiodump.ogg to something more descriptive.
You can probably get it by thinking about powers of ten and small multiples thereof (and then doing the last bit by hand), but even a slow computer can brute-force it in under a second using 20 lines of C code. I wonder which approach Google prefers?
I personally feal that even if the engineering were right, Diebold would still be disqualified unless they handed over all operations to someone else who'd had the chance to double-check the code (and hardware), because elections should be handled by those committed to neutrality (or, at least, a team with competing sides represented), not by someoen who is "committed to helping Ohio deliver its electoral votes to the president next [sic] year.".
Really, the power of the Force is nothing compared to the power of psychohistory.
Uninstall the "plugin downloader plugin" (you can just delete or read-protect libnullplugin.so on Linux). Thank you! That works.
On a similar topic, is there a way to get rid of the "you don't have this plugin; do you want it?" popup? I know I don't have the plugin; I don't want it! Every page with a flash banner ad now has a popup, despite popup-blocking!
If it were possible to generate RF to cripple an airplane with a device the size of a laptop powered by ordinary batteries, it would be simple to delibrately build such a device and slap an "IBM Thinkpad" sticker on it. The TSA must realize this, but all they check is to make sure there are no concealed explosives.
>I always assumed the cellphone ban was becaues that many people shouting over the static (and eachother) in an enclosed environmant would be *really* annoying.
What BeOS did was to add arbitrary metadata to the filesystem itself (I think as a list of pairs of strings) and then index on all of it, so that you could do searches at the OS level. I never used BeOS, but those who did generally say this was very useful.
I think this is where Microsoft's great innovation is copied from. If so, it's not the same as wmv tags. Of course, since it's been delayed, we may never know.
Not necessarily. Microsoft wants enourmous numbers of people to buy Longhorn (or new computers with Longhorn). Most of those people already run Windows. Microsoft needs to convince the people who are already in their camp to upgrade, much more than they need to recruit new users from Mac, Linux, or non-computer-ownership.
This is a tricky game they're playing. Microsoft was telling Win2k users that they should upgrade to an operating system with a database file system, and is now announcing that they aren't going to provide one soon. This might encourage those people to upgrade to an operating system that already has one (sort of).
I'm sure that if more people help out, we can get that driver fully featured by 2006. Then we just need IBM to pay for a series of TV adds: "Linux: the features Longhorn was supposed to have."
My thought as to what we can do is we can all run logging software and see where the attacks (if any) come from; then we can all group our data and trace them to their source. If enough of us get involved, especially if we get a good geographic spread (should be possible) we should be able to nap the culprit before the CIA do. We could discorage terrorism and embariss fascism at the same time!
Recent physical attacks demonstrated that an active populace does better than any government agency (remember the shoe bomber?). This is even more true for cyber-terrorism.
Of course, this all assumes the attack is big enough for us to notice. The internet can route around damage and congestion very effectively.
I guess that'll work, though the requirement to give each command its own file whether it warrents it or not is annoying. It will also be a pain if I want to change the behavior of a command at runtime (I suppose I could remove the command and insert one with the same name -- awkward). It strains the Single Point of Truth Principle because defining commands and inserting them into the used list are seperate. Finally, it's almost twice as long as the C implementation, and C is a verbose language. Using a high level language should shorten code without harming readability. Remember that bugs are proportional to physical lines of code.
As for the Reader classes thing, I stand by my statement. I've been coding Java for three years. If the classes were intelligently designed, I'd have them memorized. The seperation of Readers, FileReaders, BufferedReaders, and all the rest of the relevent classes is a mess. I guess they're trying to imitate the Unix file-descriptor/file-handle distinction, but it's horribly clumsy and since they don't relate to the thread model that way, there's no need for it.
And don't even get me started on Java threads....