What about Runescape? Back when I played, Paul and Andrew Gower were very responsive to this sort of serious question, even if the answer was "no, that's not allowed". I don't know how things have changed since it turned from a hobby into a company, though.
Could this gun be used to shoot stuff into orbit? Or, to hit stuff in orbit?
The lowest commonly-used orbits are in the 200-300 mile range, so this couldn't hit them. Even something in a 100-mile transfer orbit is iffy. However, with good enough targeting, it could hit a ballistic missile during boost or re-entry, and could probably hit any aircraft.
Ok, so range - 250 miles? What happens if they miss the target... some random object/person gets blasted 250 miles down the road? Yeah, that sounds like a great idea...
The 250 mile range is the ballistic range: a miss means something near the target gets pulped. The direct-fire range, where a miss could hit something well past the target, is probably only around 30 miles.
The djbdns security guarantee I offer $500 to the first person to publicly report a verifiable security hole in the latest version of djbdns.
Examples of problems that do not qualify:
* Denial-of-service attacks. (BIND 9's fragility makes denial of service completely trivial; but an attacker can easily take down the Domain Name System without using any of BIND's bugs. The DNS architecture needs to be decentralized.)
Says it right there. It's a DoS attack that, by means of a series of specially-selected queries, forces worst-case behavior out of the caching algorithm.
A recent Slashdot article (or maybe it was one of the comments attached to the article) pointed out an easy cache-poisoning DoS attack on djbdns. Are you still sure you want to use it?
Gee, maybe they could make the results of any unresolved queries forward users to a handy search page, instead of returning an appropriate 'not found' response!
No, this is the fun sort of DNS abuse -- things like using a DNS server as a covert communication channel, with a data rate of a few bits per minute.
My solution was to use a Hayes-compatible ISA modem. Of course, since my computer didn't have an ISA slot, this meant that I needed an older computer to run the modem, and a cable to network the two computers together.
and, on another note - has anyone seen a project to do SMP between the C64 6502 and the 1541 (the 5" drives) 6502?
The problem with doing SMP is that, IIRC, the cable between the C64 and the 1541 had a data rate of 300bps -- even for a pair of 1MHz processors, you need a faster connection than that. A Beowulf cluster, now, that's a different matter -- if you can find something where you can fit program+data into 2kb of RAM, plus however much virtual memory you want to pull off a floppy disk.
Actually Classic and Carbon are pretty much one and the same. Carbon is Classic with some of the less-used and less-functional API removed, plus some of the newer Mac OS X-related stuff added in.
It's the new MacOS X stuff that makes Carbon so much easier than Classic, particularly with respect to user-interface handling.
As for ease of use, Carbon and Classic seemed pretty intuitive to me. Certainly no harder to use than the Win32 API and, IMHO, probably easier.
You haven't tried to do any serious filesystem manipulation in Classic or Carbon, have you? Royal pain in the arse, between the need to juggle FSSpecs, FSRefs, file paths, and other ways of referring to files, and the very weak concept of a directory hierarchy that MacOS has.
They might be better now, but when I was using it a few years back, wxDateTime and related classes were essentially undocumented, particularly with respect to the handling of time zones. I also remember a number of sections of documentation that basically said "To be completed".
I've used wxWindows (now wxWidgets). For the parts that aren't buggy, it's slightly better than Win32 in ease of use, and somewhere worse than any of the others in terms of documentation.
The problem is that Microsoft broke it once for.NET, a second time for Longhorn, and is making no guarentees they won't break it again.
Apple, on the other hand, only broke the API once, with the transition from Classic to Cocoa (the MacOSX API), and even then, they did their best to maintain compatibility, with Carbon.
Slashdot Mirror
I think it's a real government tax.
The difference between music CDRs and data CDRs is that the music ones are taxed by the RIAA. That's it.
What about Runescape? Back when I played, Paul and Andrew Gower were very responsive to this sort of serious question, even if the answer was "no, that's not allowed". I don't know how things have changed since it turned from a hobby into a company, though.
Safari with default settings has a status bar which displays links on mouseover.
Out of the box, my version of Safari didn't have a status bar.
In other words...
This IS TFM
I thought that was the Kama Sutra.
Could this gun be used to shoot stuff into orbit? Or, to hit stuff in orbit?
The lowest commonly-used orbits are in the 200-300 mile range, so this couldn't hit them. Even something in a 100-mile transfer orbit is iffy. However, with good enough targeting, it could hit a ballistic missile during boost or re-entry, and could probably hit any aircraft.
What browser are you using that doesn't allow you to see the URL before you click on it?
Safari. Which is why I use Mozilla as much as possible.
Ok, so range - 250 miles? What happens if they miss the target... some random object/person gets blasted 250 miles down the road? Yeah, that sounds like a great idea...
The 250 mile range is the ballistic range: a miss means something near the target gets pulped. The direct-fire range, where a miss could hit something well past the target, is probably only around 30 miles.
Who's going to start the first escrow service for gamers..
GamingOpenMarket was.
http://cr.yp.to/djbdns/guarantee.html
The djbdns security guarantee
I offer $500 to the first person to publicly report a verifiable security hole in the latest version of djbdns.
Examples of problems that do not qualify:
* Denial-of-service attacks. (BIND 9's fragility makes denial of service completely trivial; but an attacker can easily take down the Domain Name System without using any of BIND's bugs. The DNS architecture needs to be decentralized.)
Says it right there. It's a DoS attack that, by means of a series of specially-selected queries, forces worst-case behavior out of the caching algorithm.
It's not a troll. Right now, I have access to exactly zero programs that can view a PowerPoint presentation.
Use djbdns for a little while.
A recent Slashdot article (or maybe it was one of the comments attached to the article) pointed out an easy cache-poisoning DoS attack on djbdns. Are you still sure you want to use it?
Gee, maybe they could make the results of any unresolved queries forward users to a handy search page, instead of returning an appropriate 'not found' response!
No, this is the fun sort of DNS abuse -- things like using a DNS server as a covert communication channel, with a data rate of a few bits per minute.
I'd discuss the paper, but it's in a format I can't view.
Thanks for mentioning the books. I might check them out.
I try to avoid anyone offering me "Truth" with a capital "T". It usually means they're offering a very biased pack of lies.
My solution was to use a Hayes-compatible ISA modem. Of course, since my computer didn't have an ISA slot, this meant that I needed an older computer to run the modem, and a cable to network the two computers together.
So, when's the iPod, 1994 Honda Civic campaign coming?
I have a 2004 Civic and no iPod, you insensitive clod!
and, on another note - has anyone seen a project to do SMP between the C64 6502 and the 1541 (the 5" drives) 6502?
The problem with doing SMP is that, IIRC, the cable between the C64 and the 1541 had a data rate of 300bps -- even for a pair of 1MHz processors, you need a faster connection than that. A Beowulf cluster, now, that's a different matter -- if you can find something where you can fit program+data into 2kb of RAM, plus however much virtual memory you want to pull off a floppy disk.
My experience with the F/OSS model is that it can produce incredible improvements in code over a few years, but documentation tends to lag far behind.
I'll check it out anyway.
Acronymfinder.com is much more appropriate than Google in this case.
Actually Classic and Carbon are pretty much one and the same. Carbon is Classic with some of the less-used and less-functional API removed, plus some of the newer Mac OS X-related stuff added in.
It's the new MacOS X stuff that makes Carbon so much easier than Classic, particularly with respect to user-interface handling.
As for ease of use, Carbon and Classic seemed pretty intuitive to me. Certainly no harder to use than the Win32 API and, IMHO, probably easier.
You haven't tried to do any serious filesystem manipulation in Classic or Carbon, have you? Royal pain in the arse, between the need to juggle FSSpecs, FSRefs, file paths, and other ways of referring to files, and the very weak concept of a directory hierarchy that MacOS has.
They might be better now, but when I was using it a few years back, wxDateTime and related classes were essentially undocumented, particularly with respect to the handling of time zones. I also remember a number of sections of documentation that basically said "To be completed".
I've used wxWindows (now wxWidgets). For the parts that aren't buggy, it's slightly better than Win32 in ease of use, and somewhere worse than any of the others in terms of documentation.
The problem is that Microsoft broke it once for .NET, a second time for Longhorn, and is making no guarentees they won't break it again.
Apple, on the other hand, only broke the API once, with the transition from Classic to Cocoa (the MacOSX API), and even then, they did their best to maintain compatibility, with Carbon.