You may not have heard of their names but there's a chance you might have heard their music. Aphex Twin is Richard D. James and he uses several aliases including Polygon Window and Caustic Window which are also featured on Warp Records.
Maybe you remember these following references:
The movie 8MM, in the last scene the bad guy "Machine" plays the track "Come To Daddy" from the 1997 Aphex Twin EP by the same name.
The movie Blade, in the first scene with Tracy Lords and the unfortunate fella in the car (no not the blood shower sequence with New Order - the one before that). In this scene you hear the 1992 Polygon Window: "Surfin On Sinewaves" - can't remember the track.
The Pirelli TV commercial? You know, the one where Carl Lewis runs through Manhatten? It's from the Caustic Window: "Joyrex J9" EP and the track is called "Aphex Dub".
One of the TV spot on Discovery also features a track from one of Aphex Twins' "Selected Ambient Works" albums. It's the TV spot with the photographer taking pictures of the Aurora Borealis.
I have the 1992 Polygon Window (aka Richard D. James aka. Aphex Twin) - "Surfing On Sine Waves" album. On the back of the CD there's a nice little bit that reads:
This is the second in a series of (Artificial Intelligence) albums from Warp. If you think on the same wave length, contact/send tapes to Warp Records... [address].
Today they even employ well known sceners like Lassi Nikko (aka. Dune/Orange, BrothomStates), and even sell albums from other less known independent labels featuring other well known sceners like Jaakko Manninen (aka. Mellow-D, MD).
Ah yes, personally I wouldn't mind collecting Danegeld from SCO, you know, in exchange for not having them destroyed by my fellow coutrymen. Or would I?:-)
Perhaps it is finally time to establish the good ol' Danelaw again! It's been years since I've wielded my broadsword, anyway.
I always thought it would be cool if your car could run out of gas. That would put the gas stations to good use, and make car chases a bit more exciting.
It hurt too, as it was the newest server in the park, and almost about to pass it's 365 day uptime mark. I had been looking forward to that for a long time.:-(
Twice already! I had had a 384 Kbit/s DSL link for several years, when back in march (I think) 2003 my ISP upgraded it to 512 Kbit/s. Last month they upgraded it again, now to 1 Mbit/s. Way cool!
Just unplug your cablemodem, wait 60 seconds, and then reconnect!
Ah, that's nothing! My letter stated that "the change has taken place already". Sure enough, the syslog from the night before concurred.:-)
Then download linux-0.0.1.tar.bz2 from ftp.kernel.org. Unpack it. Look at include/errno.h. Notice the literal copying of values. This file is not an original work by Linus Torvalds. He says as much in the comment which the parent poster quoted.
Interesting, that you would compare the Linux errno.h source to the original Unix source rather than to the Minix source, after reading Mr. Torvalds' header comment?
As the comment says, I think Mr. Torvald used the error numbers (ie. the values) from Minix - regarding it as the authoritative resource in place of the Posix standard.
Which brings me to the next point. I believe these values _are_ pretty much standard, and known, with respects to their short form names and especially their values, just as most people know SIGKILL is 9, etc. I haven't read the Posix standard, but I bet this is what you will find. I bet too, that Mr. Torvalds could remember all these in his sleep.
Perhaps this is where browser sniffing could be put to good use for once? Banks could warn the user when detecting an exploitable browser - for some reasonable period of time that is, before cutting the browser off altogether, giving users time to upgrade.
I know you can change the UA string, but you were refering to the average Joe User.
Of course not all browsers change the UA string with patch upgrades, but perhaps there's some other way of fetching revision info? This is beginning to smell of JavaScript though, so beware.:-)
Do you really believe that the same stupid coding error would appear in three different implementations by three different organisations? It's not a flaw in the HTTP protocol's GET request method, it's a flaw in Microsoft's URL handler.
The last time I read about Mozilla's doctype sniffing was before "Almost Standards Mode", but fortunately I only write to the strict versions of the standards (ie. no deprecated tags).
From the page:
Almost standards mode was created after 1.0 and 1.1alpha, but before 1.0.1 and 1.1beta.
Anyway, each browser (whether it's Opera, IE or Mozilla) uses a different doctype sniffing method, and what I've presented before is the essence of doctype sniffing.
Which (in essence) is:
the Strict versions of the (X)HTML standards only allow the use of non-deprecated tags therefore strict standards compliance mode should be the primary candidate for rendering.
the Transitional and Frameset (which is just transitional + frames capability) versions allow the use of most, if not all the deprecated tags you can think of. In other words this is what we call tag soup and therefore quirks mode shoulde be the primary candidate for rendering.
Remember, the word "transitional" i meant quite literally. You should use this when you're in the transitional phase from having tag soup to the point when you're adhering to the strict standards. I know this is just theory and that in the real world things are quite different.:-)
The theory, which is pretty much bullet-proof as far as I can see, is that any designer who puts a document type declaration at the top of his page is likely to know about and obey web standards.
Either that or his page authoring tool (sadly) put the doctype there for him.:-)
If Web Standards compliance is new to someone, then by definition, their initial target should be to write content that is valid to a Transitional DTD.
Unfortunately, I've found that these people just stick to the old tag soup which is valid Transitional markup anyway. Transitional has been misinterpreted by the masses, and sadly hasn't provided a real incentive for these people to move towards Strict standards markup (by filterering out your presentational tags for example, etc.).
This page seems to render fine when served as application/xhtml+xml in IE.
My Mozilla reports this page was sent as text/html (ctrl+i).
The source has application/xhtml+xml set as a meta tag, however I believe the correct way to do this is to have your webserver put the application/xhtml+xml content type in the reponse header.
E.g. On Apache you'd put "AddType application/xhtml+xml html" in your MIME section.
This is somewhat the chicken before the egg analogy - you'd have to know the content type before you start parsing html source.
For example floats are treated much differently by IE then in Mozilla even if both are in rendering an XHTML 1.1 page (personal experience with my own site).
That's probably because IE's CSS implementation is a wee bit lacking. I've run into that float problem myself, but I got around it.
There are ways around other IE CSS lackings as well, e.g. IE 5 had problems the w3c's _recommended_ way of centering text by specifying both left and right margins as 'auto'. It's fixed in IE 6, but I believe you could put in extra (well, redundant) rules in your style sheet to satisfy IE 5. However it's a bit ugly and unfortunate that you have to do it.
If you check out W3c's pages, even they will sometimes present different style sheets depending on your browser. The CSS page itself is a good example. Try IE and Mozilla with this one.
In any case, these lackings on IE's part will hopefully be fixed in the future, which means if you follow the standard IE will ultimately have to follow you.
Slashdot Mirror
Huh? You need to have your universal translator readjusted.
zIsn't that still a nerd? I think geek is the more hardcore nerd without the social skills. :-)
zYes, of course, but he uses that alias on the Rephlex label (his own). ;-)
zThat should have read "Richard D. James". He uses several aliases including Caustic Window and Polygon Window which are also featured on Warp Records.
zYou may not have heard of their names but there's a chance you might have heard their music. Aphex Twin is Richard D. James and he uses several aliases including Polygon Window and Caustic Window which are also featured on Warp Records.
Maybe you remember these following references:
There are more.
zThey're also a very open label.
I have the 1992 Polygon Window (aka Richard D. James aka. Aphex Twin) - "Surfing On Sine Waves" album. On the back of the CD there's a nice little bit that reads:
This is the second in a series of (Artificial Intelligence) albums from Warp. If you think on the same wave length, contact/send tapes to Warp RecordsToday they even employ well known sceners like Lassi Nikko (aka. Dune/Orange, BrothomStates), and even sell albums from other less known independent labels featuring other well known sceners like Jaakko Manninen (aka. Mellow-D, MD).
zAh yes, personally I wouldn't mind collecting Danegeld from SCO, you know, in exchange for not having them destroyed by my fellow coutrymen. Or would I? :-)
Perhaps it is finally time to establish the good ol' Danelaw again! It's been years since I've wielded my broadsword, anyway.
zI always thought it would be cool if your car could run out of gas. That would put the gas stations to good use, and make car chases a bit more exciting.
zNo, that was the problem with GTA2 - it was to far from reality (the surroundings that is). The cars weren't recognizable, etc.
zYup, been there done that.
It hurt too, as it was the newest server in the park, and almost about to pass it's 365 day uptime mark. I had been looking forward to that for a long time. :-(
So people, fix your inittabs. :-)
zTwice already! I had had a 384 Kbit/s DSL link for several years, when back in march (I think) 2003 my ISP upgraded it to 512 Kbit/s. Last month they upgraded it again, now to 1 Mbit/s. Way cool!
Just unplug your cablemodem, wait 60 seconds, and then reconnect!Ah, that's nothing! My letter stated that "the change has taken place already". Sure enough, the syslog from the night before concurred. :-)
I live in Denmark by the way.
zHere's a handy little trick:
$ look blackma
blackmail
blackmailed
blackmailer
blackmailers
blackmailing
blackmails
Blackman
Or just use dictionary.com. :-)
zThis file is not an original work by Linus Torvalds. He says as much in the comment which the parent poster quoted.
Interesting, that you would compare the Linux errno.h source to the original Unix source rather than to the Minix source, after reading Mr. Torvalds' header comment?
As the comment says, I think Mr. Torvald used the error numbers (ie. the values) from Minix - regarding it as the authoritative resource in place of the Posix standard.
Which brings me to the next point. I believe these values _are_ pretty much standard, and known, with respects to their short form names and especially their values, just as most people know SIGKILL is 9, etc. I haven't read the Posix standard, but I bet this is what you will find. I bet too, that Mr. Torvalds could remember all these in his sleep.
zNot just for a while - for several years! It's been in the 5.x series, which makes it 5+ year. I think 4.x has it too, but I'm not sure.
It's because it's not just a email app - it's Groupware.
zSince it's in MS Office format, has anyone found any intering meta info in it yet? :-)
zRemember the Michael Eisner (CEO, Disney) sketch on Family Guy?
zDOOOOOON!!!
zPerhaps this is where browser sniffing could be put to good use for once? Banks could warn the user when detecting an exploitable browser - for some reasonable period of time that is, before cutting the browser off altogether, giving users time to upgrade.
I know you can change the UA string, but you were refering to the average Joe User.
Of course not all browsers change the UA string with patch upgrades, but perhaps there's some other way of fetching revision info? This is beginning to smell of JavaScript though, so beware. :-)
zDo you really believe that the same stupid coding error would appear in three different implementations by three different organisations? It's not a flaw in the HTTP protocol's GET request method, it's a flaw in Microsoft's URL handler.
zHmm, imagine the embarrasment this guy must feel, then.
Of course you'd have to have some testicular fortitude to amputate your own arm?! If that's a macho-like turn on, then fine.
zThe last time I read about Mozilla's doctype sniffing was before "Almost Standards Mode", but fortunately I only write to the strict versions of the standards (ie. no deprecated tags).
From the page:
Almost standards mode was created after 1.0 and 1.1alpha, but before 1.0.1 and 1.1beta.Anyway, each browser (whether it's Opera, IE or Mozilla) uses a different doctype sniffing method, and what I've presented before is the essence of doctype sniffing.
Which (in essence) is:
Remember, the word "transitional" i meant quite literally. You should use this when you're in the transitional phase from having tag soup to the point when you're adhering to the strict standards. I know this is just theory and that in the real world things are quite different. :-)
zEither that or his page authoring tool (sadly) put the doctype there for him. :-)
zUnfortunately, I've found that these people just stick to the old tag soup which is valid Transitional markup anyway. Transitional has been misinterpreted by the masses, and sadly hasn't provided a real incentive for these people to move towards Strict standards markup (by filterering out your presentational tags for example, etc.).
zMy Mozilla reports this page was sent as text/html (ctrl+i).
The source has application/xhtml+xml set as a meta tag, however I believe the correct way to do this is to have your webserver put the application/xhtml+xml content type in the reponse header.
E.g. On Apache you'd put "AddType application/xhtml+xml html" in your MIME section.
This is somewhat the chicken before the egg analogy - you'd have to know the content type before you start parsing html source.
zThat's probably because IE's CSS implementation is a wee bit lacking. I've run into that float problem myself, but I got around it.
There are ways around other IE CSS lackings as well, e.g. IE 5 had problems the w3c's _recommended_ way of centering text by specifying both left and right margins as 'auto'. It's fixed in IE 6, but I believe you could put in extra (well, redundant) rules in your style sheet to satisfy IE 5. However it's a bit ugly and unfortunate that you have to do it.
If you check out W3c's pages, even they will sometimes present different style sheets depending on your browser. The CSS page itself is a good example. Try IE and Mozilla with this one.
In any case, these lackings on IE's part will hopefully be fixed in the future, which means if you follow the standard IE will ultimately have to follow you.
z