I agree that it is not the ISP's job to investigate the validity of an infringement claim. However, they should make reasonable attempts to protect their customers from fraudulent claims, which, at a minimum, means notifying the customer and give them reasonable time to respond.
In this study, iFast giving out customer information is clearly unacceptable. I am a little curious about Yourhosting, though. The report says they did call the customer, I wonder if 'the customer' has denied the violation on the phone. If they did, then what Yourhosting did was unacceptable.
not having to climb under the car and lay there for four hours screwing with a stupid bolt
Of course. (under normal circumstances) You won't be able to remove the screws anyways.:)
Think about it: Amount of RAM stays constant. Instead of just leaving the data where they are, you waste some cpu cycles moving them to another part of the memory space...
These are two different concepts: a format that doesn't have the feature you need, and a format that is lossy.
Different formats support different number of features. Therefore, when you convert from one to the other, it's normal that you need to strip or make up some information. (for example, layers, paths, alpha channels, DPI, comments, thumbnail, etc.)
A lossy format is a different concept. It takes out information in order to reduce file size, so even the format is not changed, you still lose information.
"According to Peter Valdes, chief technology officer of SpecOps, David uses a "new approach" in simulating the Windows environment in a Linux-powered system."
If they are using wine, it wouldn't be a "new approach in simulating the Windows environment", would it?
"As of 2002, SpecOps said that the WINE project remained in the hands of developers, and out of reach of Windows users. The project also inherited the flaws inherent in the Windows system so early adopters experienced system crashes and performance problems."
They suggests that wine "inherited the flaws inherent in the Windows system", and theirs doesn't?
"According to SpecOps's technical executives, David used reverse engineering to create a "Windows Subsystem Simulation Environment" to allow Windows applications to run "natively" on the Linux operating system."
Note the "David used reverse engineering" part. So it's either: 1) they implement the system from the ground up, or 2) they try to take credit for the wine developers' work.
PNG: great format, but HUGE files in PNG-24, so it's not the best to use for photos etc... screenshots are good though.
I think this is not a fair statement.
PNG is not worse than other lossless formats in terms of file size.
JPEG is excellent in applications where cost is the priority (e.g, web: bandwidth, consumer DC: storage).
However, for applications where accuracy is more important, a lossless format should be used. An example is photo editing. If a lossy format is used, the final picture will likely have lots of artifacts.
Professional class digital cameras does use/support lossless formats.
It is definitely possible to have more than one file having the same MD5 hash, but it is practically impossible to find those files from the hash.
So, if you just change the positions of the values within the file, it's extremely unlikely that it will have same hash.
If someone managed to figure out a way to generate a file from a MD5 hash, then it will become useless. (IIRC there's a site that tries to find two files having the same hash, to test the reliability of MD5.)
If this is just an estimate of what computer people will be using, then this piece of data doesn't really have much to do with Longhorn (read "useless":) ). People using other O/S will be using similar systems.
On the other hand, if it is some requirements for Longhorn, then it's terrible.
Even though we are around the 3GHz range now, most software works for computer 1GHz or below.
I agree that it is not the ISP's job to investigate the validity of an infringement claim. However, they should make reasonable attempts to protect their customers from fraudulent claims, which, at a minimum, means notifying the customer and give them reasonable time to respond. In this study, iFast giving out customer information is clearly unacceptable. I am a little curious about Yourhosting, though. The report says they did call the customer, I wonder if 'the customer' has denied the violation on the phone. If they did, then what Yourhosting did was unacceptable.
or 'mkpasswd'.
ahhhhhhh... surgery every 90 days... that's terrible. :)
not having to climb under the car and lay there for four hours screwing with a stupid bolt Of course. (under normal circumstances) You won't be able to remove the screws anyways. :)
I think their company name change is more interesting: Borland -> Inprise -> Borland
Current Debian branches use XFree86 4.3 and it will not use XFree86 4.4 because of the license problem.
I wonder if it supports other formats like, OO, WP...
Can I have 3 gigs of RAM and still be stingy? :-)
Sometimes when I need to use some big files, especially over the network, I "cat file >/dev/null" first and watch it fill the memory. :)
The advantage of swap is that it increases the amount of memory applications can use without adding more RAM.
If you use RAM disk for swap, it'll only decrease performance because of the unnecessary moving of memory blocks.
Think about it: Amount of RAM stays constant. Instead of just leaving the data where they are, you waste some cpu cycles moving them to another part of the memory space...
Big generation gap :)
I am guessing what he meant is that, since you recall the oxygen level at that time, you must have born by then. So, how old are you? :)
Umm... This one is even more complicated. Are you casting over yourself or other people? :)
Not to pick on you but you phase like if a student doesn't tick the checkbox he/she isn't allowed to take the exam. :)
Having said that, it is possible to install SuSE via FTP. The boot disk images are available at: ftp://ftp.suse.com/pub/suse/i386/current/boot/
However, you'll probably want to find a fast mirror or download the directories first, it could be a pain to install from their main ftp. :)
Different formats support different number of features. Therefore, when you convert from one to the other, it's normal that you need to strip or make up some information. (for example, layers, paths, alpha channels, DPI, comments, thumbnail, etc.)
A lossy format is a different concept. It takes out information in order to reduce file size, so even the format is not changed , you still lose information.
It's not as obvious as you think. Here is my comments in another thread.
These guys seem shady. It feels like they want to hide the fact that their product is based on wine/CrossOver.
I think this is not a fair statement.
PNG is not worse than other lossless formats in terms of file size.
JPEG is excellent in applications where cost is the priority (e.g, web: bandwidth, consumer DC: storage).
However, for applications where accuracy is more important, a lossless format should be used. An example is photo editing. If a lossy format is used, the final picture will likely have lots of artifacts.
Professional class digital cameras does use/support lossless formats.
A better way would be whether repeated loading and saving of the same file accumulate losses?
If you take a GIF file, load it, and save it. It will not lose any color.
This is not true for JPEG.
So, if you just change the positions of the values within the file, it's extremely unlikely that it will have same hash.
If someone managed to figure out a way to generate a file from a MD5 hash, then it will become useless. (IIRC there's a site that tries to find two files having the same hash, to test the reliability of MD5.)
On the other hand, if it is some requirements for Longhorn, then it's terrible.
Even though we are around the 3GHz range now, most software works for computer 1GHz or below.