Software Customer Bill of Rights 293
Cem Kaner of Badsoftware.com has written up a Software Customer Bill of Rights. Very appropriate considering our recent stories about Microsoft viruses, Dell's BIOS-clickwrap licensing agreement, etc.
Sorry.... (Score:4, Insightful)
Re:Sorry.... (Score:2)
Re:Sorry.... (Score:2, Insightful)
Re:Sorry.... (Score:5, Funny)
"But this is America. Consumer rights are secondary to business rights..." ... and making things better is secondary to making smug, cynical statements.
You just described Microsoft's business model. Why make decent software when you can make smug, cynical statements instead? What a country! :)
Re:Sorry.... (Score:5, Insightful)
Quality and security of software is a market feature, and if the public ignores the continual security lapses of some particularly popular software, for instance, and if they accept that there will be X crashes per week, then so be it: The marketplace has spoken. We don't need anyone protecting us from ourselves, and feigning ignorance after the fact is incredibly weak.
Re:Sorry.... (Score:3, Insightful)
It is all the corporation's fault. Let me illustrate with a seemingly unrelated story.
I was flying home after a long day. In the airport. Tired. Plenty of time before my flight. Grab a bite to eat at a fast food joint. Then I need to visit a restroom. I start looking around for one. Finally, I ask a nearby employee where is t
And then later, on the news, (Score:5, Funny)
Re:And then later, on the news, (Score:5, Funny)
I was going to read it (Score:5, Funny)
Just kidding! I'd never use IE.
Live up to marketing???? (Score:5, Interesting)
When has any product ever "lived" up to the marketing claims? If I expected everything I bought to live up to their claims, I'd be dissapointed with every bar of soap, every beer, and every Big Mac.
Re:Live up to marketing???? (Score:2)
And soap is soap, damnit. I've never seen it claimed to be more than it is in advertising.
Herbal Essence (Score:5, Funny)
Re:Live up to marketing???? (Score:5, Insightful)
And that's not the way it should be. An ad shouldn't be able to tell me that a product is something when it's not. It is not my job to guess about what parts are lies.
Re:Live up to marketing???? (Score:4, Interesting)
accurate but useless (shown in clinical tests to contain the active ingredient X, i saw this one the other day, I'm not kidding, they made no claims about the effectiveness of the stuff, just claimed that clinical tests showed the stuff contained one of the ingredients)
or
subjective as all hell (any adjective incl best, fastest, biggest, or claim to surveys, used by more popular cheerleaders than any other brand of laxative)
If you can show they lied you can make big money. If they do lie then they won't have much money in the first place.
Lies by omission are a little different but even in ads there is no law that says you have to be exhaustive, just don't actively lie.
de minimis fraud (Score:2)
It's not possible to promote a product without lying a bit. This is called de minimis fraud, fraud within the scope of the law; fraud that cannot be avoided in capitalism.
Re:de minimis fraud (Score:3, Interesting)
If they claim, however something that is objective and verifiebly untrue, you should be able to sue. Say, McDonalds claiming that the big mac has x% of fat when it's not true.
Re:Live up to marketing???? (Score:5, Insightful)
I've seen several boxed applications that have claims on the box that are simply not true... And I'm not talking about a game claiming to be able run on a 500MHz system.
I can name a number of MMORPGs that had big fat claims on their boxes/websites for features that were not (yet) in the games at launch. Hell, some of these games didn't even RUN after launch... With no refunds.
The section that you refer to is probably directed at things like that.
Re:Live up to marketing???? (Score:4, Funny)
Re:Live up to marketing???? (Score:4, Insightful)
Living up to the claims means that when we go in the store, and the package actually says "Imports all microsoft office formats", and it turns out that is false... that they have to take it back, no questions asked. It's a false sale.
The reason this needs to be stated is that, although you have this protection with physical products, the license-ish nature of software has allowed some vendors to claim that you have no recourse, even though they lied.
It's not the same thing as false advertising... more like sale under false pretenses.
Re:Live up to marketing???? (Score:2)
You know, as a Student, I'd gladly take that beer off you if you don't want it!
Re:Live up to marketing???? (Score:5, Insightful)
The same should be true of software. AOL can say that their software helps protect your children from inappropriate content, but they should not be able to say that it prevents your children form viewing inappropriate content. Such subtleties are everything in a court of law.
I agree with most of it... (Score:4, Interesting)
If I could have manufacturer's adopt one part of the consumers bill of rights, it would be to advertise with honesty. Do not sell me a software product which does not live up the advertising.
The one part I disagree with is the reverse engineering. Companies have a right to sell software and to ban people from reverse engineering it.
Re:I agree with most of it... (Score:5, Insightful)
Why? If I buy a car, I can dig around under the hood to my heart's content. If I buy a book, I can study the writing style. Why should software be any different, especially given that software interacts with other programs on my computer, and other systems on the net, in ways that can be important to know but are easily hidden from the use.
Re:I agree with most of it... (Score:2)
But only their patents.
If their software is not patentable than no, they do not have the right to ban you from reverse engineering it, any more than someone could "ban" you from making a chair like the one they had made.
I suppose they could try to revoke your license, but by that point you'd already have a work alike, so. .
KFG
Re:I agree with most of it... (Score:2)
Re:I agree with most of it... (Score:2)
He then points out that if we didn't have reverse engineering that the PC as we know it today would not exist.
Re:I agree with most of it... (Score:2)
That was hard to say. I hate defending companies.
You miss the point. (Score:2)
You are free to figure out how your car works, and make your own.. the car company doesn't make you sign a no reverse engineering clause... so what's the point?
Software success should not be based on secrets. Innovative ideas can be patented. (let's pretend that patent still works for a minute here). Figuring out what the file format of a word processor document is so I can make other software that uses it is hardly "st
Re:You miss the point. (Score:2)
Re:You miss the point. (Score:2)
That's what patent law is for. Patents are a tradeoff, because it forces you to pub
Re:I agree with most of it... (Score:4, Insightful)
How do you think Ford ever got competition from the likes of GM, VW, Kia, etc.? How do you think Ford started making cars?
I think they can patent some ideas, based on non-obviousness and the rest of patent law, but when it comes down to it, Ford still buys all the newest GM models and takes them apart, just like everyone else.
US patent and copyright law was created to expand the public domain. To do this, it gives an incentive to people for inventing (patents) or creating (copyrights). If you ever stop people from learning how to invent or create, by stopping them from taking apart and investigating the products of others, then you are acting against the intent of the constitution.
Re:I agree with most of it... (Score:2)
Except that (algorithms and business models notwithstanding) you're not supposed to be able to patent an idea. You can patent a particular invention or process, but not the idea.
Re:I agree with most of it... (Score:3, Insightful)
Copyright law?
"Ideas" get exactly zero legal protection, and rightly so. Only actual code requires any protection, and that is already covered by copyright. And frankly, given that software defects cost us $60 billion a year in damages, they should be grateful we even give them that much.
From a purely practical standpoint, how exactly do no-reverse-engineering clauses help companies anywa
Interesting... (Score:5, Insightful)
Re:Interesting... (Score:4, Interesting)
It would be like if I purchased a VCR which did not work two months later, and after I went to have it fixed, the manufacturer decided to "add a feature" which sends them data about the VCR. It is BS.
It's about time.. (Score:2, Insightful)
Re:It's about time.. (Score:2)
Why? For the credit card information to be sent from my computer, I must have, at some point, put it in, and so have seen it. By consequently sending this
Re:It's about time.. (Score:3, Insightful)
4. User has right to see and approve all transfers of information from her computer
In the credit card case, you are talking about repetition of a single information transfer, which you will have seen the first time it is sent. If needs be, have an MD5SUM of each transfer so you can be sure it is the same.
There will always be a point between your saying "send it" and the data being sent where the computer could craftily do something to the inf
Re:It's about time.. (Score:2)
Look at the flip side. This would be a nice analogue to other credit-reporting laws. If you pull your credit report, you'll see a nice list of every other person who's accessed it. (Well, except the federal government, under some Patriot-act shenanigans; but that's an exception.) Having a record of
Utopia (Score:5, Insightful)
Remember, most computer users still think software crashes and glitches are part of life with a computer, that viruses and worms are the work of evil pirates and that Microsoft is the victim, not the cause, etc
In short: it'll never happen. Move along
Too much responsibility is bad for your economy (Score:5, Interesting)
I can see where this view is coming from, but seriously; the litigious culture that is developing in the USA (and therefore no doubt on this side of the pond before long) could have a grave impact on your economy.
You have to take a certain degree of responsibility for your own action. Otherwise, everybody will just be too scared to do anything, and every American will just stay in bed all day.
You NEED suppliers to be a viable business yourself; and in return those suppliers deserve a leniency from you as far as accountability goes.
In return you get leniency from your customers as far as your own liability goes.
As the owner of a small software business, I feel comfortable with the fact that whilst I cannot sue Microsoft's ass if something goes terribly wrong; neither can my customers sue my ass.
Swings and roundabout; 6 of one...
Re ligitious culture (Score:2)
Blaming amorphous "culture" or "morals" is a quick way to end a discussion and avoid reaching any substantial conclusion.
My thoughts on this subject are made quite clear.. (Score:2)
Subject: Great ideas that will never come to pass
What "Microsoft viruses?" (Score:4, Insightful)
How is it Microsoft's fault if users run the attachment? Is it Linus Torvalds' fault when there's a sendmail hole? Is that suddenly a "Linux hole?"
Just curious.
Re:What "Microsoft viruses?" (Score:3, Funny)
No, it's a GNU/Linux hole.
Re:What "Microsoft viruses?" (Score:3, Interesting)
You would think that after 10 years of this crap that Microsoft, with all their money and resources would have figured out how to provide their customers with a mail client or OS that any halfway intelligent 15 year old couldn't bring to it's knees after spending an afternoon on an IRC channel with his buddies.
The only way that I ca
Re:What "Microsoft viruses?" (Score:3)
Being able to run attachements from an external source within a mail client is such an absurdly broken feature that it boggles the mind that you are trying to place the blame for what happens on the user. Even worse is the nightmarish situation that most users are doing it with Administrator level access!!! Bill Gates SHOULD go door to door to personally apologize for shipping a
Re:What "Microsoft viruses?" (Score:3)
Granted that worms like Code Red were a problem for enterprise environments
Worms like Code Red are a problem because they propagate on ports that are normally open to provide services. SQL Slammer and MS Blaster got into many corps through users carrying it in on laptops.
The most telling argument that there is a REAL problem and it lies with MS, not the users is that SQL Slammer got into MS's own s
Re:What "Microsoft viruses?" (Score:2)
I deal with this issue by simply explaining to customers/friends/etc. that if they need or want secure, robost computing they need to _not_ use MS products. All these viruses and worms make this advice seem more obvious by the day.
I've been advocating and converting PC users since 1997. *creak*
I'm sorry, but this software can't be patented (Score:2)
Can we say "legal contradiction" boys and girls?
I knew you could.
KFG
Re:I'm sorry, but this software can't be patented (Score:2)
Can we say "legal contradiction" boys and girls?
I'd like to see what you are smoking. It must be really good stuff.
Patents, copyrights and contract law are three separate issues. Just because there is a contract it doesn't mean that copyrights or patents are excluded.
Re:I'm sorry, but this software can't be patented (Score:2)
Exactly, that's my point.
I read the article. I read it carefully. I even read some of the stuff the article linked to.
Some interesting stuff in there.
KFG
Re:I'm sorry, but this software can't be patented (Score:2)
Re:I'm sorry, but this software can't be patented (Score:2)
I thought the little game of splitting hairs that people play is that algorithms aren't patentable, because they're abstract mathematical ideas. However, once you figure out how to use a mathematical algorithm to do something useful using a computer, then that process is patentable. That would say to me that you can't patent algorithms, but you can patent software. (Not that I agree with it, but that appears to be the way it is.)
I guess they say that the idea fo
This is a DMCA violation! (Score:2, Insightful)
But the software is intended to allow the user to see what Microsoft wants them to see. Encouraging users to see all their own data is circumventing the grand Microsoft plan of Digital Domination. I demand the site is removed from all search engines.
They forgot one (Score:4, Insightful)
IMHO, there's one the omitted from the list:
11. The user shall have the right to view the source code on demand.
If I am running your software on my computer, I have the right to see what exactly it is doing. In 99% of the cases, I would not exercise this right, if I believe that the software is doing what it is supposed to do and I have no suspicions that it is doing something funny. I have a Red Hat Linux system but don't have most of the source code RPMs installed, or the full Linux kernel source installed. It's good enough for me to know that I can acquire it on demand.
And before I get flamed for sound like a clone of RMS, realize that seeing the source code is not necessarily the same as modifying and redistributing it. All Free Software is Open Source, but not all Open Source is Free Software. I would, however, object to having to sign NDAs to see source. You can tell me not to redistribute your source and I will abide by that, as that is simply following existing copyright law, but I would not accept a blanket gag order to not discuss the source at all.
Of course, this will probably never happen, but its a nice thought, anyway.
Re:They forgot one (Score:2)
Re:They forgot one (Score:2, Interesting)
I've had plenty of occasions to make small changes to applications running on my Linux box.
For example, earlier this year I installed GnomeMeeting [gnomemeeting.org], which is a Linux audio/video conferencing program that will talk to NetMeeting clients. I very quickly discovered that when GnomeMeeting starts
Great, but (Score:4, Interesting)
I wonder what would happen if 40,000 slashdotters mailed a copy of this to their respective congressferrets?
The only thing I would add is to see if there's any reasonable way something can be done about the fact the BSA has made it a criminal act to own lots of software and have less than perfect archiving of license paperwork.. I don't think there's any way that could be done in a reasonable manner within this "bill of rights" though...
Re:Great, but (Score:2)
Unless they each attach $1000 to their letter, not a damned thing.
America has the best government money can buy.
Without sounding like a 60's radical (Score:4, Insightful)
Just the 10 basic facts (Score:5, Informative)
(Note, this does not excuse you from reading the FA, there will be a test.)
Software Customer Bill of Rights
1. Let the customer see the contract before the sale.
2. Disclose known defects.
3. The product (or information service) must live up to the manufacturer's and seller's claims.
4. User has right to see and approve all transfers of information from her computer.
5. A software vendor may not block customer from accessing his own data without court approval.
6. A software vendor may not prematurely terminate a license without court approval.
7. Mass-market customers may criticize products, publish benchmark study results, and make fair use of a product.
8. The user may reverse engineer the software.
9. Mass-market software should be transferrable.
10. When software is embedded in a product, the law governing the product should govern the software.
Bonus points if you can figure out which of the above *didn't* have a detailed explanation in the original!
fggf (Score:2, Insightful)
They take all the rights, with no responsibilities (Score:5, Insightful)
While these agreements become more complex and onerous, the people creating them have taken on no responsibilities to clarify the licenses, explain the reqstrictions, etc.
If the companies are allowed to use these licenses, they should be required to have an independent citizens rights group translate/rate the license to compare it to accepted norms of how restrictive the licenses are. Rather than expecting each person to read the complete license, or have their lawyer interpret it for them; it should be analyzed by a professional and summarized in simple language. It should also carry ratings on a few key points, like how much it tries to limit product usage, resale, reverse engineering.. and, related areas like privacy protection by the company.
You know.. (Score:5, Insightful)
What I found, though, was a simple, precise set of terms that are wholly agreeable. Nothing in that document is the least bit complicated or overbroad.
Let us see the contracts before we have to agree to them. Don't take away rights we already have, like criticism and reverse engineering, and first sale. If you know about serious bugs, tell us. Don't lie about what the product does.
That's pretty straightforward, and should not be the least bit damaging to anyone selling decent software.
Awesome, but they missed a big one. (Score:5, Interesting)
But there's a big one missing, particularly important in light of Symantec's foolhardy announcement:
The software can be installed on multiple machines.
I own a notebook and a desktop home server. I use both of them basically as a unit - sometimes literally, via Terminal Services or Synergy. They achieve different purposes - the server provides infrastructure (holding data, managing requests from other users [e.g., web pages], network security, MP3s), while I run actual applications on my notebook.
With this setup, it only makes sense to have a roughly identical set of software on each. I don't want my word processing solely on my notebook, and I don't want all of my security apps solely on my server.
So it's exactly that reason why this product-activation crap is odious. If I want two functionally-identical machines, I have to buy two operating systems, two word-processing packages, two versions of TurboTax and Symantec. similarly, with DRM, I'll have to buy two licenses for every piece of media I want to play. Others will follow down this path to the seedy underworld of profit-driven software.
It only seems fair that I expect to pay only once per software package. After all, I'm one guy; I'm never typing on both machines at the same time. Now, I understand why software companies are reluctant to release software that can be installed a trillion times, because it tends to get purchased, like, eight times, and then widely distributed on IRC. But at the same time, they're smacking down guys like me.
So with that in mind, I propose: Let software be installed on multiple machines. That number can be limited, and it can be small. Ten is fine - if I install software on more than ten machines, I should probably be purchasing a site license. But one is insufficient, in this day of frequent multiple-computer ownership.
- David Stein
The other side (Score:2)
But user-based licensing tends to seriously hurt organizations that have more users than computers -- particularly universities. If you have 50,000 users and only 5,000 computers, you don't want to pay for 50,000 licenses.
Re:The other side (Score:2)
- David Stein
Re:The other side (Score:3, Insightful)
Re:The other side (Score:2)
it happens all the time.
where have you been?
it is not a problem.
ever downloaded a program that said "free for non-commercial use"?
did you die a painful death screaming in agony about how hard it was to understand what was going on?
you are looking for difficulties that do not exist.
Re:Awesome, but they missed a big one. (Score:5, Insightful)
Re:Awesome, but they missed a big one. (Score:3, Interesting)
#11 (Score:4, Interesting)
So I feel it needs another article:
11. A software vendor will provide real support for the products they sell. Or A software vendor will outline in detail what; if any, support they provide and what guidelines they use.
A shorter version (Score:4, Funny)
Ooookay.... (Score:3, Interesting)
We've got one story about robots putting people out of work and another with people claiming we should put people who do jobs robots can't do (like programming) out of busines
Apple Computer... (Score:2, Interesting)
Source code will be placed in bonded escrow (Score:4, Insightful)
Source code and documentation will be placed and maintained [updated] in bonded escrow.
If the software product or hardware product reaches end of life and the current company does not develop a follow-on product with corresponding upgrade offer to registered customers, then the source code [software and firmware and documentation in digital format] will be sent to registered software and hardware customers, and, the source code will declared open source and offered to all via internet. If the initial development company is sold, source code will be offered and sent, if requested, to registered software and hardware owners. If the initial development company ceases to exist, source code will be sent to registered software and hardware owners, and, the source code will be declared open source and offered to all via internet. If an operating system integer upgrade [v1.X -> v2.X] requires the user to purchase new operating system software or hardware, then the source code will be offered to registered customers.
Failure to make source code available when a product reaches end of life or other conditions listed above will result in the top five officers of the initial development company (and the top five of the purchasing company, if a company purchase is involved) [CEO, COO, CIO, CFO, etc] being fined no less than $1,000,000 each, not payable by insurance company or current company; and will result in their forfeiture of all of the monies the executives received from their respective companies; and, will result in their receiving three years in prison without possibility of parole.
Re:Source code will be placed in bonded escrow (Score:2)
That would pretty much ensure that there would be no more "integer upgrades". Instead software would be numbered in ten-millionths or just renamed (fer'instance "Windows XP" might become "The Great and Powerful Windows" and so on).
Otherwise I rather like the idea.
Good Idea (Score:2)
1. Let the customer see the contract before the sale.
I really don't see this as mandatory or practical, especially with machines that come with a lot of bundled software. What is critical is that users get a no-cost chance to return the product if they don't agree to the EULAs.
Another requirement should be that EULAs must be in plain language.
Finally, the EULA must be good for the life of the product. T
One more (Score:2)
Background on the proposal (Score:3, Informative)
1) My proposals are primarily in support of disclosure. For readers who prefer free market accountability to litigation, that's what disclosure rules support. To make rational decisions in an open market, the customer needs information to base the decisions on. The information rules that I advocate are not far from laws that currently govern traditional sales:
- The customer can see the contract before the sale and use that knowledge as a factor when comparison shopping (and the press can help customers comparison shop by publishing information about the contracts, such as warranty policies, support policies, etc.)
- The company is accountable for its claims. I'm not talking about claims like "our burgers are yummy." I'm talking about "statements of fact" (specific statements that can be proved true or false). Laws governing warranties, fraud, and deceptive trade practices make these claims enforceable in the traditional markets. If you can't hold the company to its claims, you can't know what you're buying.
- The company can't prevent mass-market customers (and reporters covering mass-market products) from publishing comparison studies and product criticisms.
- The company can't prevent mass-market customers from using reverse engineering to discover bugs and security holes, false claims, etc. (NOTE: Patent law protects the original ideas in a product, whether you reverse engineer them or not. Additionally, my proposal doesn't invalidate a restriction against using reverse engineering to help create a competiting product. It invalidates restrictions that bar people from doing non-competing things, like discovering problems, making this product interoperable with others, fixing bugs in products that a company no longer supports, etc.
- The company has to disclose its KNOWN defects. Note that failure to disclose significant defects in traditional goods can be prosecuted under the deceptive trade practices or unfair competition laws.
The next main theme is privacy/security related. These are ground rules, not litigation magnets. Don't transfer data from someone else's computer without permission, don't block their access to their own data (a trick that some companies use to force customers to renew licenses or agree to unfavorable new license terms) and don't cut off their rights to use software they've paid for without a court order.
This isn't about bugs. It's about misconduct.
Do we need to polish the language to make that distinction clear in the legislation? Of course. This is a set of principles, not legislation. The goal here is to present the ideas simply (while giving enough footnote-links to provide context for legally knowledgeable readers). Legislative precision comes after appropriate people accept the principles.
SO WHY BOTHER? WHAT'S THE POINT?
The software industry is increasingly vulnerable to regulation. Software publishers aren't creating masses of new jobs in the United States. They've made a lot of people angry, partially because they've been doing business in ways that would never be tolerated under traditional American sales law. The most visible representative of the industry is a monopoly that seems to be so greedy as to be willing to try to wipe out even the research / scientific / free-public-benefit community in order to preserve or trivially increase its market share.
When companies look like they're more about greed than about providing benefits to the country, they become vulnerable to regulatory proposals. If their business practices seem dishonest and their products cause widespread, well publicized social disruption, some legislators will introduce bills to regulate the industry. Every crisis is another opportunity for legislation.
Not necessarily good or wise legislation. If we want THAT, it's up to us to advise legislators. Otherwise, they'll do what they do and we'll complain about it later.
This is great... (Score:3, Funny)
Software Publishers vs. Computer Owners (Score:4, Interesting)
The Free/Libre/Open-Source Software (FLOSS) movement seems to understand this, but many mass-market proprietary software developers are still able to flout this rule. Unfortunately, most computer users have become accustomed to being subservient to their software.
My own experience with most FLOSS has been much like my experience with high-speed Internet service: I can never go back. I think once people get a good taste of what using well-behaved software is like, things will quickly change. The only things that can get in the way of this change are:
Re:Glad I live in the EU! (Score:2)
What EU country do you live in??? I'd pack tomorrow and move to it if that was remotely true.
Re:Glad I live in the EU! (Score:2)
This is of course wrt commerce, you obviously give away rights such as free speech when being in military intelligence.
but AFAIK, nothing can take away your statutory rights, and any EULA that asked you to would be meaningless.
Re:Glad I live in the EU! (Score:2)
won't somebody *PLEASE* think of the criminals...
what "individual right" is being taken away?
Re:Glad I live in the EU! (Score:2)
Your post is more of the same knee-jerk reaction you get in rags like the Daily Mail who delight in bigotry and bias; actually studying the EU might give you very different impressions.
Re:Wishful thinking (Score:5, Interesting)
Is there such a thing as a Software Consumers' Association? I couldn't find anything like that using a quick Google search.
Re:Wishful thinking (Score:5, Interesting)
Any attempt to form a "Software Consumer's Organization" will have a BSA bullseye painted on it in a heartbeat. It would be far more exciting to see the Alliance Against Fraud in Telemarketing and Electronic Commerce (AAFTEC) decide that current software licensing practices are deceptive, fraudulent and unfair to consumers.
Re:Wishful thinking (Score:5, Interesting)
When public anger with an industry rises, legislators get tempted to create laws to regulate the industry. Software publishing is particularly vulnerable because so many publishers have engaged in business practices that would be considered outrageous (and unlawful) in traditional markets AND because this is no longer a wildly expanding industry / employer in the United States.
We can lay out some principles to advise those legislators, or we can lay back, and later complain that they got it all wrong.
Re:Wishful thinking (Score:3, Funny)
Not sure about that. Years of noise on /. hasn't had an appreciable effect on the Great Satan.
Re:Wishful thinking (Score:2)
you could think software is where electrical home appliances were 50 years ago, software _is_ very new compared to other 'engineering' fields, and such guarentees that the software is safe are going to be among the few things properiaty software can live with op
Re:Wishful thinking (Score:2, Insightful)
Are you sure?
Following rule 1 is mandatory if you are including non-standard terms. GPL doesn't apply, as it is an optional component.
Following rule 2 is mandatory to a limited extent. While everyone should be aware of a defect, information on how to explo
Alternative: Consumer Protection Labeling (Score:3, Interesting)
Caution! By agreeing to use this software, the vendor may access your private files at any time.
Caution! This software is unprotected and may expose you to foriegn programs (virus and worms) that may corrupt your documents.
The be
Re:Alternative: Consumer Protection Labeling (Score:3, Interesting)
This port has installed the following files which may act as network
servers and may therefore pose a remote security risk to the system.
/usr/local/sbin/oftpd
If there are vulnerabilities in these programs there may be a security
risk to the system. FreeBSD makes no guarantee about the security of
ports included in the Ports Collection. Please type 'make deinstall'
to deinstall the port if this is a concern.
For more information, and contact details about the securit
Re:Wishful thinking (Score:2)
However, I don't see much here that impacts free software authors. The issue here is sellers. From the article: "...the Court said that the contract for sale is formed when the customer agrees to pay and the seller agrees to deliver the product..." If there is no sale, then there is no contract and there is no issue of customer's rights.
Of course, this raises the issue
Re:TEAR UP THE BILL OF RIGHTS! (Score:2)
You misspelled "terrists."
Re:What about when Linux fails? (Score:3, Insightful)
Yeah, it's fashionable to want to sue Bill, but what if some guy creates some virus that brings a Linux system down to it's knees? Who do we sue? Linus? OSDL? Or will there be a double standard? Remember, if Bill gets to be sued, be prepared for your favorite OSS house to be liable as well. Otherwise it's just sheer hypocrisy to target MS. And remember, MS is made of of coders who went to the same schools as you. Contrary to OSS opinion, Bill does not write every single line of code in the products nowada
Re:What about when Linux fails? (Score:2, Informative)
Hell - they even use it in this exact same context: "If Linux breaks, you can't call anyone. You can try getting some help from the Linux weirdos on some IRC channel, but good luck to you. Now in the unlikely event [ha!] that Micr
Re:Simple Solution... (Score:2, Insightful)
If you don't like how a software product is marketed or how the EULA works, THEN DON'T BUY THE PRODUCT. Buy from a competitor, download open source software. You do have choices people.
And how do I make that choice if the EULA is only presented after I've bought it?