Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:Easier to block? (Score 1) 131

Well, you probably broke quite a few laws by using coersion to gain access to a customer's servers. But I for one would overlook it, given the benefits to the world at large (still it could be risky).

Fortunately, given the use of GRE tunnels, the spammer probably broke more laws, and would probably be a bit hesitant to sue.

No legal problem there. It's a contract issue.

Comment Re:Licensing nightmare? (Score 1) 378

Fonts are only protected in that they are "programs" for creating type. Once a font is used, you own the result. The shapes themselves are not protected.

With an image, if you subsequently use an image, you are making an unauthorised copy.

With a font, once you have the font and use it, then the output is entirely yours.

The different between fonts and images is that images need to be copied (infringement), but fonts only need to be used (not infringement).

Fonts may come with an EULA which tries to change this, but it is debatable whether this would be valid as you did not agree to any contract when you visited the website with an embedded font.

Comment Re:Licensing nightmare? (Score 1) 378

So you end up with a legitimate copy as you describe. Now you could move that copy to your system font directory. You could direct anyone else who needs the font to go to the same website you got yours from and move it to your system font directory in the same way.

So if any one website uses a font, everyone has access to a free font download.

Comment Re:Here's how Gogle should respond (Score 1) 92

Why are you griping about GNOME and KDE here?

The "wontfix" tag is generally taken to mean that the bug is not a problem that needs to be fixed. This might arise because the submitter has been misled by poor documentation. More often it is because the submitter wants the software to behave differently from what it does at the moment (eg. "the flight simulator in OpenOffice Spreadsheet doesn't work").

If there is a lack of expertise, usually a "help"-type tag is used, never "wontfix". If "help" is unavailable or there is a lack of resources then the bug is generally just left open.

This is standard stuff in FOSS development.

If "wontfix" is being used entirely correctly, then all the number of "wontfix" bugs will do is reflect the number of bug submitters who are submitting bugs that aren't bugs in the first place. Thus, counting "wontfix" bugs tells you nothing useful; perhaps just the numbers of submitters who aren't paying attention.

Therefore nothing can really be concluded by comparing GNOME and KDE "wontfix" bugs.

A philosophy behind GNOME is that features are not added at the cost of usability. This is based on the idea that less complex software is easier to use. This will result in more "wontfix" bugs as developers decline to add new features. You are welcome to disagree with this philosophy. However, you can't draw any other conclusion about the quality of GNOME or KDE nor the attitude of their respective developers from this.

I do think you should be modded down: because you are offtopic, you don't understand what "wontfix" means, you draw flawed conclusions because of this and because your gripe is therefore entirely unfounded.

Slashdot Top Deals

Some programming languages manage to absorb change, but withstand progress. -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

Working...