Various politech readers tested yahoo mail for the problem and it appears that this problem is already fixed. So don't everybody go rushing off and start mailing yourself- you probably won't find anything.
Oh, and since NTK is slashdotted already, you might want to read the original politech message to see what we're talking about.
I don't think anyone's arguing that it's impossible for a well-off private citizen to gather the materials and know-how to launch themselves to the edge of space. While it's not bleeding-edge design, it's still difficult enough to require some serious brainpower and mathematics to make it work. And there's not exactly much margin for error, is there? It's not as though he's building a car engine, where if it blows up you shrug and head back to the shop for more refinement.
But this guy just doesn't seem smart enough to figure out the engineering details himself, and doesn't even seem interested in getting his seat-of-the-pants design verified by people with bigger brains than his. I wouldn't trust this guy to build me a go-kart. The real giveaway is that he doesn't seem interested in testing his design before he straps himself in and pushes the button. This clearly marks him as an idiot, or a kook.
Somebody will eventually come along and put together enough money, intelligence, experience, and common sense to make this happen. But I doubt it'll be this guy. He'd be entertaining to watch on Junkyard Wars (uk: Scrapheap Challenge), though.
Major labels are the ones who decided it's a good idea to start paying to get songs on the air. Now they're crying because Clear Channel owns enough stations to start raising the price?
The entire major-label-commercial-radio biz is totally corrupt. You might as well make an effort to support independent bands, stations, and labels because there ain't no way this business is going to get cleaned up any time soon.
1. "Embedded" is not a coherent market. It's an incredibly wide span from dinky 8-bit CPUs that you'd use if you were building a toaster, or maybe super-efficient CPUs for cheap cellphones, through medium-sized CPUs that run industrial machines, or maybe cheap routers or automotive engine controls, all the way up to very hefty CPUs that drive expensive routers, giant room-sized printers, or networked test equipment.
2. Yes, some embedded designs (those at the smaller end of the scale) don't use an OS or a kernel of any kind. But it's equally important to realize (as some 5-rated slashdot poster invariably doesn't) that the embedded CPU in a piece of $100,000 network equipment probably does run a hefty OS kernel, especially if it needs multitasking, networking, field debugging, or upgrading (as many pieces of $100,000 network equipment do).
3. Note that I say "OS kernel", not "OS". Most PC users tend to think of an "OS" as a giant 500MB distribution that includes everything from printer drivers to web browsers. Even heavyweight embedded systems are a lot slimmer (kernel+libraries+app, perhaps), but may still bear some resemblance to what you consider an "Operating System".
4. There's as many penny-pinching companies doing embedded designs as there are penny-pinching companies of other flavors. Some companies have big issues with the costs of VxWorks and similar products.
5. Support is really important in the embedded world, where you're always going to have to customize somebody else's code. As a corollary, survival of the company you're buying from is very important too (definitely an concern with today's crop of embedded-linux companies). Note that this and #4 are in conflict.
How to change quicktime plugin filetypes:
Open quicktime. Under edit->preferences->quicktime-preferences, flip to "Browser Plug-in". Push the "MIME settings" button, then uncheck whatever MIME types you don't want quicktime to handle. I use Quicktime 5.0.2, other versions may vary.
BTW: your "duh" comment is totally off base. This bug affects all MIME types, so a workaround for octet-stream barely scratches the surface (go read the bugzilla reports. This causes problems with.jpg.tar.gz.mp3.ps.c.sh...)
Mozilla developers all agree this is a real bug; it's just that nobody has actually written the code to fix it just yet.
Depending on the exact system setup (which changes between OS and what software is installed locally), mozilla likes to determine the One True Extension for a given mime type, then pastes that onto every file saved even if the file already has another correct extension. The 0k thing is something different.
If you go back to 0.9.9 you will find that file extensions work properly. But there so many people on bugzilla griping about this bug that I expect this gets fixed real soon now. Fingers crossed for 1.0.1.
I really, really wish someone would have fixed the obnoxious file-extension mangling bug. It's rapidly soaring toward the top of the most-frequently reported bug list, and was introduced at 1.0rc1 back in April. It's bug 120327 if anyone's interested in reading 183 (mostly repetitive) comments.
This bug is why mozilla insists on adding.exe extensions to anything delivered as application/octet-stream,.txt to text/plain, and likes to fool around with lots of other extensions depending on your exact setup (on my machine it tries to rename every mp3 file to.mpga).
I'd be thrilled if Big Media gave up on screwing up copyright law and just kept doing this.
Because this is the way copyright law is supposed to work. They're the only ones allowed to distribute copies, and if they catch you, you're in trouble.
And I don't buy this "assumed guilty" complaint. If you're distributing an MP3 file that matches the checksum of a song they own the copyright on, they are entirely justified in trying to bust you. Busting folks that are sharing major-label MP3s is a lot less harmful than fiddling with the law, making it illegal for anyone to share anything.
Maybe their efforts will reduce the amount of major-label crap on P2P networks, and legal stuff (which is what everyone claims they want P2P for) will then make up a larger percentage of P2P content. Which will demonstrate the legitimacy of P2P networks.
Further differences between the two cases mentioned:
The federal (2600/NY) case was brought under the big bad DMCA anticircumvention laws. Since these laws are pretty new, were mostly untested, and are so vague that they can arguably be applied to almost anything, this case caused a lot more concern about the stretching boundaries of copyright.
The California case is not brought under the DMCA; it was brought under state trade-secret laws. These laws aren't new, are better understood, and their limits are better defined. The other issues (jurisdiction and free-speech conflicts) are also a lot less murky than the DMCA. So while this case is still a big cause for concern, it's not about ever-expanding copyright law or the DMCA. It's more about Big Media smacking programmers with a bag of lawyers, whether or not the law backs them up.
This story is about the case that's in California, and getting batted back and forth among California state courts. No trial has happened yet; they're still arguing over preliminary injunctions and jurisdiction.
The 2600 case was in federal court in New York. They lost the trial, and were also shot down by the federal appeals court.
... just so the theme support code doesn't look like a big, fat, stupid waste of time.
I mean, come on, guys, themes have been in mozilla for a really long time now, and there's still how many included? two. (and one of them is just the old Netscape 4 look.) Oh, and if you're feeling really adventurous, you can wander out to the web, and find a whopping ten more. If you can find them; it seems as though the websites are packing up and moving once a month.
Sorry about the flame, I really like the browser. But the whole themes thing has started to look kind of silly.
3 Gs in a corner is typical for a high-performance open-wheel race car, when you're doing everything right. That's corner after corner, lap after lap, until the race is over, and that's a lot longer than a roller coaster ride.
Crashing race cars, however, routinely see over 30 Gs. That's ten times the force on your body. Real problems start around 40-50 Gs, because you can fracture your neck or the base of your skull from the deceleration alone. With the proper safety gear, even these crashes are survivable.
Still, rollercoasters are hardly in the same category, unless someone plans on building a coaster that randomly flies off the track and smashes into a wall.
That's really cool. I just called it, and they ask for your telephone number, name, and SSN. That's it, and they offer the option of opting out for 2 years or permanently. I now look forward to no more "pre-approved" credit card junkmail.
Even if this doesn't protect against all telemarketers or credit theives, I'm still glad I did it. Thanks for posting the number!
between Kazaa, the dominant file sharing network, and Verizon, a company with revenues of $67 billion...
Now that just sounds funny, in a way that tickles my anti-big-bad-corporate-america sensibilities. Basically, over here we've got Kazaa the file-sharing network, and over here we've got Verizon, who, well, we don't know exactly what they do (or we're afraid to say), but they make a hell of a lot of money doing it. And so, we must consider them big, important people with ideas.
Almost like how mafia dons are always referred to as businessmen, without specifying what business exactly they're in.
Looks to me like truetype fonts (and similar formats that have program-like logic included) are copyrightable, but typefaces in general (including the font after rendering) are not.
1. The code is ridiculously simple (perhaps a hundred lines of C) and compiles and works perfectly under Linux with a minor fix to the #includes.
2. Non-embeddable fonts will prevent you from creating a PDF file that is portable and will display correctly, if you're using Adobe software (Acrobat Distiller). This program can fix the problem. (hmm. Significant noninfringing use?)
3. There's a lot of free fonts out there that, through accident or omission, have the "don't embed" bits set. So there's a significant number of fonts where the author did not intend to limit the ability to distribute the font, yet these stupid bits (more correctly, stupid font-creation software that turns them on by default) are interfering with use of fonts as intended.
For some reason, the idea of fish in space seems really funny to me. I'm imagining a fishtank in zero-g, where some of the fish a swimming rightside-up, some are swimming upside down... better watch out when you take off the cover to feed them, though, because fish might head for the food and then pop out of the water and go sailing across the room. Of course, the water is fairly likely to go sloshing across the room as well, so presumably someone would have to design a zero-g airlock (waterlock?) for food and fish to enter and leave the tank. Or perhaps just spin the whole thing like a centrifuge to get gravity-like effects.
Slashdot Mirror
(photo of revolver up against dog's head) If You Don't Buy This Magazine, We'll Kill This Dog!
Oh, and since NTK is slashdotted already, you might want to read the original politech message to see what we're talking about.
But this guy just doesn't seem smart enough to figure out the engineering details himself, and doesn't even seem interested in getting his seat-of-the-pants design verified by people with bigger brains than his. I wouldn't trust this guy to build me a go-kart. The real giveaway is that he doesn't seem interested in testing his design before he straps himself in and pushes the button. This clearly marks him as an idiot, or a kook.
Somebody will eventually come along and put together enough money, intelligence, experience, and common sense to make this happen. But I doubt it'll be this guy. He'd be entertaining to watch on Junkyard Wars (uk: Scrapheap Challenge), though.
If you want to reduce your bandwidth a bit convert that 865KB gif to a PNG. It goes down to 550-600KB depending on the compression level chosen.
The entire major-label-commercial-radio biz is totally corrupt. You might as well make an effort to support independent bands, stations, and labels because there ain't no way this business is going to get cleaned up any time soon.
2. Yes, some embedded designs (those at the smaller end of the scale) don't use an OS or a kernel of any kind. But it's equally important to realize (as some 5-rated slashdot poster invariably doesn't) that the embedded CPU in a piece of $100,000 network equipment probably does run a hefty OS kernel, especially if it needs multitasking, networking, field debugging, or upgrading (as many pieces of $100,000 network equipment do).
3. Note that I say "OS kernel", not "OS". Most PC users tend to think of an "OS" as a giant 500MB distribution that includes everything from printer drivers to web browsers. Even heavyweight embedded systems are a lot slimmer (kernel+libraries+app, perhaps), but may still bear some resemblance to what you consider an "Operating System".
4. There's as many penny-pinching companies doing embedded designs as there are penny-pinching companies of other flavors. Some companies have big issues with the costs of VxWorks and similar products.
5. Support is really important in the embedded world, where you're always going to have to customize somebody else's code. As a corollary, survival of the company you're buying from is very important too (definitely an concern with today's crop of embedded-linux companies). Note that this and #4 are in conflict.
Oops. I meant that the EFF page referenced runs off the right side of the page. It wasn't exactly clear what page I was referring to.
Open quicktime. Under edit->preferences->quicktime-preferences, flip to "Browser Plug-in". Push the "MIME settings" button, then uncheck whatever MIME types you don't want quicktime to handle. I use Quicktime 5.0.2, other versions may vary.
BTW: your "duh" comment is totally off base. This bug affects all MIME types, so a workaround for octet-stream barely scratches the surface (go read the bugzilla reports. This causes problems with .jpg .tar.gz .mp3 .ps .c .sh ...)
Mozilla developers all agree this is a real bug; it's just that nobody has actually written the code to fix it just yet.
Gotta love the fact that the page only formats correctly under IE. Under Netscape 4.75 and Mozilla the text runs way off the right edge of the window.
Depending on the exact system setup (which changes between OS and what software is installed locally), mozilla likes to determine the One True Extension for a given mime type, then pastes that onto every file saved even if the file already has another correct extension. The 0k thing is something different.
If you go back to 0.9.9 you will find that file extensions work properly. But there so many people on bugzilla griping about this bug that I expect this gets fixed real soon now. Fingers crossed for 1.0.1.
This bug is why mozilla insists on adding .exe extensions to anything delivered as application/octet-stream, .txt to text/plain, and likes to fool around with lots of other extensions depending on your exact setup (on my machine it tries to rename every mp3 file to .mpga).
Because this is the way copyright law is supposed to work. They're the only ones allowed to distribute copies, and if they catch you, you're in trouble.
And I don't buy this "assumed guilty" complaint. If you're distributing an MP3 file that matches the checksum of a song they own the copyright on, they are entirely justified in trying to bust you. Busting folks that are sharing major-label MP3s is a lot less harmful than fiddling with the law, making it illegal for anyone to share anything.
Maybe their efforts will reduce the amount of major-label crap on P2P networks, and legal stuff (which is what everyone claims they want P2P for) will then make up a larger percentage of P2P content. Which will demonstrate the legitimacy of P2P networks.
I love it when all I need to do to stand up for what's right is just keep my money in my pocket.
The federal (2600/NY) case was brought under the big bad DMCA anticircumvention laws. Since these laws are pretty new, were mostly untested, and are so vague that they can arguably be applied to almost anything, this case caused a lot more concern about the stretching boundaries of copyright.
The California case is not brought under the DMCA; it was brought under state trade-secret laws. These laws aren't new, are better understood, and their limits are better defined. The other issues (jurisdiction and free-speech conflicts) are also a lot less murky than the DMCA. So while this case is still a big cause for concern, it's not about ever-expanding copyright law or the DMCA. It's more about Big Media smacking programmers with a bag of lawyers, whether or not the law backs them up.
The 2600 case was in federal court in New York. They lost the trial, and were also shot down by the federal appeals court.
I mean, come on, guys, themes have been in mozilla for a really long time now, and there's still how many included? two. (and one of them is just the old Netscape 4 look.) Oh, and if you're feeling really adventurous, you can wander out to the web, and find a whopping ten more. If you can find them; it seems as though the websites are packing up and moving once a month.
Sorry about the flame, I really like the browser. But the whole themes thing has started to look kind of silly.
Crashing race cars, however, routinely see over 30 Gs. That's ten times the force on your body. Real problems start around 40-50 Gs, because you can fracture your neck or the base of your skull from the deceleration alone. With the proper safety gear, even these crashes are survivable.
Still, rollercoasters are hardly in the same category, unless someone plans on building a coaster that randomly flies off the track and smashes into a wall.
Even if this doesn't protect against all telemarketers or credit theives, I'm still glad I did it. Thanks for posting the number!
Practice getting everybody to say "whop" at the same time.
Now that just sounds funny, in a way that tickles my anti-big-bad-corporate-america sensibilities. Basically, over here we've got Kazaa the file-sharing network, and over here we've got Verizon, who, well, we don't know exactly what they do (or we're afraid to say), but they make a hell of a lot of money doing it. And so, we must consider them big, important people with ideas.
Almost like how mafia dons are always referred to as businessmen, without specifying what business exactly they're in.
CNET article
comp.fonts FAQ: Are fonts copyrightable?
Looks to me like truetype fonts (and similar formats that have program-like logic included) are copyrightable, but typefaces in general (including the font after rendering) are not.
2. Non-embeddable fonts will prevent you from creating a PDF file that is portable and will display correctly, if you're using Adobe software (Acrobat Distiller). This program can fix the problem. (hmm. Significant noninfringing use?)
3. There's a lot of free fonts out there that, through accident or omission, have the "don't embed" bits set. So there's a significant number of fonts where the author did not intend to limit the ability to distribute the font, yet these stupid bits (more correctly, stupid font-creation software that turns them on by default) are interfering with use of fonts as intended.
Screw men on mars. I wanna see Fish In Space.
Now that's offtopic.