Wanting to give DVD-R's to your kids instead of 50UKP originals isn't exactly an exceptional circumstance; neither is wanting to play legally bought R1/3/4/5 DVD's/games. My experience suggests these uses are at least as common as pirate games
If I can't rip it to FLAC using standard ripping software (without insane amounts of errors) and play it back with my choice of playback application, I'm not interested. Why should I *pay* to get less access to my music than if I just pirate it?
I wish people weren't so willing to put up with low quality rips and silly copy protection; maybe iTunes would look a little more like Magnatune or allofmp3 if people were a little less easy to please.
Any system that includes an SMTP server supporting mail relaying or
delivery MUST support the reserved mailbox "postmaster" as a case-
insensitive local name. This postmaster address is not strictly
necessary if the server always returns 554 on connection opening (as
described in section 3.1). The requirement to accept mail for
postmaster implies that RCPT commands which specify a mailbox for
postmaster at any of the domains for which the SMTP server provides
mail service, as well as the special case of "RCPT TO:<Postmaster>"
(with no domain specification), MUST be supported.
The section you quoted basically means you can spam/virus filter it, and set up temporary denials in the event of attacks; nothing more.
As for the subject of the discussion; my catch-all addresses have been fine, but YMMV. If I was that worried about dictionary attacks, but still wanted the ability to give a new address out to each company, I'd do something like *-signup@mydomain or *@signup.mydomain or similar, but you might not have that level of control (in which case I'd recommend finding somewhere better to host your email, but *shrug*).
Why XHTML? Is there something wrong with HTML 4.01? Just because XHTML's newer and has an X in the name doesn't mean you should use it over 4.01 Transitional/Strict in most cases.
I certainly won't be impressed if Slash just moves to serving XHTML 1.0 + Compatability Profile as text/html; that's just taking for granted the robust HTML parsers browsers have developed:/
HTML 4.01 Strict + CSS is as valid and as clean as XHTML 1.0 Strict + CSS; moreso if they're both served as text/html. 99% of sites which use (or pretend to use) XHTML are probably better off just sticking with HTML. Can anyone give me a convincing counterargument? Please?
Fails how? If your pump or cooling fan fails, the heat goes up until, potentially, your computer shuts down (probably after sounding a nice alarm). If the waterblock comes off the CPU (unlikely with modern mounting methods), the CPU either fries, throttles down or shuts down. If it springs a leak, well, it's no worse than any other watercooling system; get something of quality and it'll be no more likely to do so than your freezer leaking coolent everywhere. If you knock it over and spill it, or crack the glass open or so, well, you should have put it somewhere safer; people seem to manage to keep real aquariums without getting water everywhere.
Liquid cooling is fun, effecient and practical, with a few managable risks. It may not be your cup of tea, but that doesn't mean it's without merit. This is especially true when you're dealing with SMP systems; even without overclocking a dual Opteron has up to 178W to disapate -- a high end dual Xeon can easily pass 200W. Watercooling's probably going to be simpler than working out an effecient, quiet air cooling system for this sort of setup.
A common figure for the estimated lifespan of a modern CPU is about 10 years. After that, ion migration and other entropic effects are likely to kill it.
Canon Powershot Pro 1 8mp Digital Camera: 669.73 UKP Canon EOS 300D 6.3mp Digital Camera +Lens: 681.48 UKP
At an event like a wedding, you're going to have a lot of indoor shots with relatively low lighting; you'll want to bump up the sensitivity to keep the shots from blurring, especially at longer range shots where a flash isn't practical. Now, the EOS does ISO 200 in it's sleep, and will happily produce ISO 400 shots which are perfectly usable; the excruciatingly dense 8MP sensor on the Pro 1 is probably noiser at ISO 50 than the EOS at 200.
In fact, let's back that statement up (using the handy crops from DPReview):
The ISO 200 shot from the Pro 1 is actually noiser than the Rebel at ISO 1600!
Are the extra couple of megapixels and the more flexible bundled lens worth that much noise, lower battery life, icky electronic viewfinder and poorer autofocus?
DVD video is still error corrected; it's largely just a UDF filesystem containing.vobs and various support files. This is good because a single bit error in a video stream, while not the end of the world, can cause nasty artifacts (like half of each frame falling to bits until the next keyframe).
I've certainly never seen a dual layer disk with more than 8.5G of data on it. Not to say you're wrong; 1.1G of ECC for 8.5G of data sounds about right (~1 bit ECC per byte of data). I just don't think anyone actually does anything like mode 2 on DVD's, which makes sense since the raw bit error rate on a denser media is probably somewhat higher than that of a CD.
I wrote a small bit of CSS which I find blocks ads quite effectively. The false positive rate can be a little high sometimes, but it's pretty good on most sites. Opera's keyboard configurability make it fairly simple* to bind to a keypress to turn it off when it gets in the way. The bundled "Hide certain sized elements" does largely the same thing, but is a little less discriminating.
I dislike both IE and Firefox UI wise; IE more because it's so feeble (something MyIE/Maxthon/friends largely resolves), Firefox more because it doesn't behave like a native application; it doesn't even bother to use my system default font, never mind made text gadgets behave like standard Windows ones.
I find Opera suits my needs far better, and I think it's a little unfair (and unwise) that most of this hype centers around moving people to Firefox rather than away from IE.
"Thing is, why do most of us need all of this power?"
Games? When you're splitting your CPU power across hundreds of entities with AI, sound, graphics, damage models etc, CPU can quickly become a major bottleneck.
Audio encoding and processing? I store my music as FLAC; before I transfer to my iPAQ, I want to encode it as low bitrate Vorbis; I'd *love* to have the CPU power to do that as fast as IO will allow (as it is I'm lucky to make 5x real time at -q-1). Equally I ReplayGain all my music so I don't need to constantly reach for the volume control; not having to wait around for a scan of an album every time I get something new would rock.
Video decoding and encoding? Very high bitrate MPEG-4, especially with some of the more exotic features of the standard, can bring a 3GHz P4 to it's knees just decoding. It takes about half an hour to transcode a DVD-8 to DVD-4; overnight isn't always enough to encode a high quality XviD, and this with a system that's probably about 70% of the way towards top end single CPU hardware.
Image processing? I don't want to have to wait whole seconds for a photo to render every time I alter the settings in a fixup filter; I want immediate feedback. And of course more power in my desktop probably means more power in my portable devices too; agressive lossless compression in my digicam without it locking up for 45s? Please!
There are a few reasons at least *some* of us "need" more computing power; I've not even mentioned the geekier ones which *I* want more for. Certainly the whole human race can benefit from having more computational power to it's name, even if only a few groups of people can really harness it.
Ditto storage (I want my entire DVD collection on my workstation; I want to keep a versioned history of every file I handle; I want to back up every bit of data I own to a single SD card; I want to grep my entire 5GB of mail in a fraction of second without special indexing software).
Ditto graphical power (I want Far Cry to look like THIS damnit!).
Ditto network bandwidth (I want to access the stupendously fast, huge mass storage devices on my server 400 miles away like it was installed in my own computer; I want to migrate large processes across machines as easily as changing CPU affinity on an SMP system).
But that's just me. I'm rambling even worse than you now, *ahem*.
Yup; data files tagged with metadata, and a database caching said metadata providing effecient searches, playlist creation, etc. Store your music on a samba share, import into foobar on the client, and you're 90% towards what you might possibly want. The other 10% can likely be achieved either by writing your own plugin or maybe using a third party one.
Failing that, well, at least most of foobar is BSD licensed; lots of code you can probably reuse:)
Er, ok, you're asking to store a big-ass file like a.wav in a BLOB; doing this is a Very Bad Idea because SQL's not really designed for such things to be effecient.
First, you've got to insert your multi-GB file into the db; this means you're going to have a single SQL statement in memory at both the client and server end which is likely going to be larger than physical memory. After sending this single huge-ass string across a socket, the db is then going to sit there writing your big-ass BLOB out while your application waits patiently; if you're doing this on an interactive system, you're not even going to be able to provide a useful progress indicator, since the update is so course-grained -- the best you can do is hook into the SQL API and track how fast your multi-GB string is being sent.
Then when it comes to retriving this data, you're probably going to be buffering a multi-GB result set in memory (and potentially moving it across the network), and again you're not even going to be able to provide much in the way of progress indication, even assuming you have the resources to actually do any of this in one go in the first place.
If you limit the size of each BLOB, all you need to do is wrap your data access layer to handle the buffering for you; it can track progess in query-sized chunks, and even fairly effeciently seek inside your "virtual BLOB". This is about as much like writing your own language as writing your own logging library.
Personally, though, I'd rather just leave my files on a real filesystem and serve them using Samba or NFS or even HTTP. Frankly as far as audio is concerned I'd keep the metadata there too, leaving the database to act as a cache for metadata searches, without turning my entire audio collection into a monstrously huge data file I can only access through SQL. That's just me though; I can't pretend to have a deep understanding of the problems you're dealing with.
Split the file across BLOBs. I'm sure things get a lot easier for the DB when you don't have to send a 4G+ INSERT statement to create a single row in your table. It's probably a lot more effecient on SELECTs too; no buffering insanely huge rows into memory before your application gets the data, and much quicker "seeking" and such.
If you don't think your comments are important enough to be worthy of a few seconds correcting typos, why should we think they're worth reading?
Put it this way; reading involves pattern matching against word shapes. If you corrupt a word shape with a typo like "caregul", it's somewhat similar to causing a pipeline stall in a CPU; my reading pace slows for a second as I deal with the error. This is distracting, and doesn't help you get your opinion across.
Of course, if you're dyslexic or so and correcting typos takes you quite a lot of effort, I'll let you off;)
They wouldn't get licensed with such features. They don't ship with them on Windows, why do you expect them to do so on Linux?
Don't worry, I'm sure someone will come up with a small layer between your DVD drive and any software which silently strips region codes, PUO's (Prohibited User Operations) and CSS.
Heh, just to confuse matters, the System Properties window on my XP box reads "Version 2002". cmd.exe still reads "Microsoft Windows XP [Version 5.1.2600]". I guess when you have 30-odd million lines of code, one version number just isn't enough;)
Heh, MSIE is version: 6.0.2800.1106.xpsp2.030422-1633. I guess the first 4 bits are the base major/minor/revision/build, then branch (one for each OS and OS SP level IE needs to be integrated into), then what could be a date (features frozen at 2003-04-22 perhaps?), followed by a build number for the branch. That's just a guess though:)
"It should be noted that the GateD code available at this website under the click-thru license was NOT covered by GPL. Hence, the code was available for use ONLY in research and educational purposes."
This doesn't at all sound like a BSD-style license. Can you elaborate? Was there an original BSD-licensed codebase which the "GateD community" commercialised, or was the "GateD community" the originator in the first place?
"Coined in the United States in the early 20th century, it has met with a blizzard of condemnation for being an improper yoking of irrespective and regardless and for the logical absurdity of combining the negative ir- prefix and -less suffix in a single term"
Um, I would have thought PNG's most useful feature next to GIF is that it supports 24bit images. Alpha transparency in IE can be achieved using some IE-specific CSS/JS, so...
Wanting to give DVD-R's to your kids instead of 50UKP originals isn't exactly an exceptional circumstance; neither is wanting to play legally bought R1/3/4/5 DVD's/games. My experience suggests these uses are at least as common as pirate games
If I can't rip it to FLAC using standard ripping software (without insane amounts of errors) and play it back with my choice of playback application, I'm not interested. Why should I *pay* to get less access to my music than if I just pirate it?
I wish people weren't so willing to put up with low quality rips and silly copy protection; maybe iTunes would look a little more like Magnatune or allofmp3 if people were a little less easy to please.
Opera has a kiosk mode built in, too.
Make sure addresses like postmaster@ and abuse@ work. They're unlikely to get spammed, but may well receive important messages.
postmaster@ is actually required by rfc2821, btw.
As for the subject of the discussion; my catch-all addresses have been fine, but YMMV. If I was that worried about dictionary attacks, but still wanted the ability to give a new address out to each company, I'd do something like *-signup@mydomain or *@signup.mydomain or similar, but you might not have that level of control (in which case I'd recommend finding somewhere better to host your email, but *shrug*).
Why XHTML? Is there something wrong with HTML 4.01? Just because XHTML's newer and has an X in the name doesn't mean you should use it over 4.01 Transitional/Strict in most cases.
:/
I certainly won't be impressed if Slash just moves to serving XHTML 1.0 + Compatability Profile as text/html; that's just taking for granted the robust HTML parsers browsers have developed
HTML 4.01 Strict + CSS is as valid and as clean as XHTML 1.0 Strict + CSS; moreso if they're both served as text/html. 99% of sites which use (or pretend to use) XHTML are probably better off just sticking with HTML. Can anyone give me a convincing counterargument? Please?
Fails how? If your pump or cooling fan fails, the heat goes up until, potentially, your computer shuts down (probably after sounding a nice alarm). If the waterblock comes off the CPU (unlikely with modern mounting methods), the CPU either fries, throttles down or shuts down. If it springs a leak, well, it's no worse than any other watercooling system; get something of quality and it'll be no more likely to do so than your freezer leaking coolent everywhere. If you knock it over and spill it, or crack the glass open or so, well, you should have put it somewhere safer; people seem to manage to keep real aquariums without getting water everywhere.
Liquid cooling is fun, effecient and practical, with a few managable risks. It may not be your cup of tea, but that doesn't mean it's without merit. This is especially true when you're dealing with SMP systems; even without overclocking a dual Opteron has up to 178W to disapate -- a high end dual Xeon can easily pass 200W. Watercooling's probably going to be simpler than working out an effecient, quiet air cooling system for this sort of setup.
A common figure for the estimated lifespan of a modern CPU is about 10 years. After that, ion migration and other entropic effects are likely to kill it.
/. comment, it must be true.
I read it in a
- EOS 300D at ISO 50.
- EOS 300D at ISO 200.
- Pro 1 at ISO 50.
- Pro 1 at ISO 200.
The ISO 200 shot from the Pro 1 is actually noiser than the Rebel at ISO 1600! Are the extra couple of megapixels and the more flexible bundled lens worth that much noise, lower battery life, icky electronic viewfinder and poorer autofocus?DVD video is still error corrected; it's largely just a UDF filesystem containing .vobs and various support files. This is good because a single bit error in a video stream, while not the end of the world, can cause nasty artifacts (like half of each frame falling to bits until the next keyframe).
I've certainly never seen a dual layer disk with more than 8.5G of data on it. Not to say you're wrong; 1.1G of ECC for 8.5G of data sounds about right (~1 bit ECC per byte of data). I just don't think anyone actually does anything like mode 2 on DVD's, which makes sense since the raw bit error rate on a denser media is probably somewhat higher than that of a CD.
I wrote a small bit of CSS which I find blocks ads quite effectively. The false positive rate can be a little high sometimes, but it's pretty good on most sites. Opera's keyboard configurability make it fairly simple* to bind to a keypress to turn it off when it gets in the way. The bundled "Hide certain sized elements" does largely the same thing, but is a little less discriminating.
.ini editing, grr!
* Involves
I dislike both IE and Firefox UI wise; IE more because it's so feeble (something MyIE/Maxthon/friends largely resolves), Firefox more because it doesn't behave like a native application; it doesn't even bother to use my system default font, never mind made text gadgets behave like standard Windows ones.
I find Opera suits my needs far better, and I think it's a little unfair (and unwise) that most of this hype centers around moving people to Firefox rather than away from IE.
It's a ranking between 1-4 or so. NetSol's "1" seems to stretch from Alexa's 1 - 15000 at least.
Games? When you're splitting your CPU power across hundreds of entities with AI, sound, graphics, damage models etc, CPU can quickly become a major bottleneck.
Audio encoding and processing? I store my music as FLAC; before I transfer to my iPAQ, I want to encode it as low bitrate Vorbis; I'd *love* to have the CPU power to do that as fast as IO will allow (as it is I'm lucky to make 5x real time at -q-1). Equally I ReplayGain all my music so I don't need to constantly reach for the volume control; not having to wait around for a scan of an album every time I get something new would rock.
Video decoding and encoding? Very high bitrate MPEG-4, especially with some of the more exotic features of the standard, can bring a 3GHz P4 to it's knees just decoding. It takes about half an hour to transcode a DVD-8 to DVD-4; overnight isn't always enough to encode a high quality XviD, and this with a system that's probably about 70% of the way towards top end single CPU hardware.
Image processing? I don't want to have to wait whole seconds for a photo to render every time I alter the settings in a fixup filter; I want immediate feedback. And of course more power in my desktop probably means more power in my portable devices too; agressive lossless compression in my digicam without it locking up for 45s? Please!
There are a few reasons at least *some* of us "need" more computing power; I've not even mentioned the geekier ones which *I* want more for. Certainly the whole human race can benefit from having more computational power to it's name, even if only a few groups of people can really harness it.
Ditto storage (I want my entire DVD collection on my workstation; I want to keep a versioned history of every file I handle; I want to back up every bit of data I own to a single SD card; I want to grep my entire 5GB of mail in a fraction of second without special indexing software).
Ditto graphical power (I want Far Cry to look like THIS damnit!).
Ditto network bandwidth (I want to access the stupendously fast, huge mass storage devices on my server 400 miles away like it was installed in my own computer; I want to migrate large processes across machines as easily as changing CPU affinity on an SMP system).
But that's just me. I'm rambling even worse than you now, *ahem*.
Opera is still identifiable: it says "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.52" by default.
:)
In terms of raw hits to newzbin this month, Opera accounts for ~6%, Gecko based browsers ~17% and MSIE ~74%.
By comparison, back in Feburary Opera was at ~3.5%, Gecko ~11% and MSIE nearly 82%. Looking good
(Registered Opera user since v5 \o/)
*glances at e:\music*
:)
*glances at his copy of foobar2000*
Yup; data files tagged with metadata, and a database caching said metadata providing effecient searches, playlist creation, etc. Store your music on a samba share, import into foobar on the client, and you're 90% towards what you might possibly want. The other 10% can likely be achieved either by writing your own plugin or maybe using a third party one.
Failing that, well, at least most of foobar is BSD licensed; lots of code you can probably reuse
Er, ok, you're asking to store a big-ass file like a .wav in a BLOB; doing this is a Very Bad Idea because SQL's not really designed for such things to be effecient.
First, you've got to insert your multi-GB file into the db; this means you're going to have a single SQL statement in memory at both the client and server end which is likely going to be larger than physical memory. After sending this single huge-ass string across a socket, the db is then going to sit there writing your big-ass BLOB out while your application waits patiently; if you're doing this on an interactive system, you're not even going to be able to provide a useful progress indicator, since the update is so course-grained -- the best you can do is hook into the SQL API and track how fast your multi-GB string is being sent.
Then when it comes to retriving this data, you're probably going to be buffering a multi-GB result set in memory (and potentially moving it across the network), and again you're not even going to be able to provide much in the way of progress indication, even assuming you have the resources to actually do any of this in one go in the first place.
If you limit the size of each BLOB, all you need to do is wrap your data access layer to handle the buffering for you; it can track progess in query-sized chunks, and even fairly effeciently seek inside your "virtual BLOB". This is about as much like writing your own language as writing your own logging library.
Personally, though, I'd rather just leave my files on a real filesystem and serve them using Samba or NFS or even HTTP. Frankly as far as audio is concerned I'd keep the metadata there too, leaving the database to act as a cache for metadata searches, without turning my entire audio collection into a monstrously huge data file I can only access through SQL. That's just me though; I can't pretend to have a deep understanding of the problems you're dealing with.
Split the file across BLOBs. I'm sure things get a lot easier for the DB when you don't have to send a 4G+ INSERT statement to create a single row in your table. It's probably a lot more effecient on SELECTs too; no buffering insanely huge rows into memory before your application gets the data, and much quicker "seeking" and such.
If you don't think your comments are important enough to be worthy of a few seconds correcting typos, why should we think they're worth reading?
;)
Put it this way; reading involves pattern matching against word shapes. If you corrupt a word shape with a typo like "caregul", it's somewhat similar to causing a pipeline stall in a CPU; my reading pace slows for a second as I deal with the error. This is distracting, and doesn't help you get your opinion across.
Of course, if you're dyslexic or so and correcting typos takes you quite a lot of effort, I'll let you off
They wouldn't get licensed with such features. They don't ship with them on Windows, why do you expect them to do so on Linux?
Don't worry, I'm sure someone will come up with a small layer between your DVD drive and any software which silently strips region codes, PUO's (Prohibited User Operations) and CSS.
Heh, just to confuse matters, the System Properties window on my XP box reads "Version 2002". cmd.exe still reads "Microsoft Windows XP [Version 5.1.2600]". I guess when you have 30-odd million lines of code, one version number just isn't enough
Heh, MSIE is version: 6.0.2800.1106.xpsp2.030422-1633. I guess the first 4 bits are the base major/minor/revision/build, then branch (one for each OS and OS SP level IE needs to be integrated into), then what could be a date (features frozen at 2003-04-22 perhaps?), followed by a build number for the branch. That's just a guess though
This doesn't at all sound like a BSD-style license. Can you elaborate? Was there an original BSD-licensed codebase which the "GateD community" commercialised, or was the "GateD community" the originator in the first place?
Um, I would have thought PNG's most useful feature next to GIF is that it supports 24bit images. Alpha transparency in IE can be achieved using some IE-specific CSS/JS, so...