If you have correct SPF, you will most likely get more spam. Why? Someone spams mailservers with your domainname, then it bounces because of failed SPF, and many mailservers are configured wrong, so you will get backscatter spam.
The irony of this is, that SPF says "it wasn't me" and the wrong configured mailservers then send YOU an answer saying "hey, we're not accepting your mail, because your SPF says it is not your mail".
the copies ARE worth something, because you want to play. But this just means, you cannot sell more copies than are needed for the players. If one stops playing and another one starts playing, they can trade the license.
is there ANY case, where watermarks on digital music were accepted as an proof? Just imagine... i cannot tell what amazon writes into my mp3s. Maybe its an id, which points to me as a person. maybe their software is faulty and it describes YOUR account. So when someone tells me "a mp3 with your amazon id was found", they still need to prove, that the only possiblity of this is, that i released it somewhere. And thats not the case, anyone can write anything in files.
ah, sorry... i did not consider the whole thing. The amazon case IS special:
you buy a combo pack: CD+MP3s. So you can sell one of them keeping the other part, as you may sell one CD of a collection of 6 CDs. Noone can forbid you to split your possession and selling only a part of it.
why do you need to discuss this? Its just the same as if you would have ripped the CD yourself.
And what's then the case, is not sooo easy to say. The first approach would be, that you need to delete the copy, as you're selling your license. But then you have the right to make seven private copies, and even give them to friends. So you may be able to declare your copy as one of the private copys (just think of giving it to someone (private copy law), who gives it back to you (without leaving a copy at his pc)).
No, its not. You drop the price not after a week, but after you sold 1000 copies OR after half a year. So either the people who can pay much want the book now and pay 20 eur, or they just are not there, then you sell it for cheap after half a year (which should be enough time, that no one has the patience to wait just for a few bucks, if they can affort it to the bigger price). Of course this is a tradeoff and you can try to play with the threshold of price/copys to sell before dropping the price/wait time in which noone buys the book.
its the same argument as saying "hey, books cost money, because someone had to type them". no, thats a fraction of the price. most money is for the content. So, go and add 5 cent per book and then add the ebook to the purchase. Its okay. Or stay with the current price and see the ebook as additional very cheap marketing.
The point why removing code is so hard is not, that its hard to restore. We have VCS for this. But its hard to discover, the code ever existed. Who goes to the VCS and searches for old commits, when implementing a new function? If you weren't there when the code were in use, its unlikely you find it in the VCS instead of rewriting it. So removing code is a decision about making it hard to find, that it ever existed.
One solution would be to remove and leave a comment behind "here was code, which was removed in a commit at $DATE". What other solutions are there, for this dilemma?
its called libpam-opie. There are debian packages, and googling finds some howtos. I'm not sure which to link, because some apply on freebsd, others are written in german... so search for yourself which one works for you. In the end you get prompted with a seed ((almost) constant per account) and a serial number, and can generate the corrsponding OTP (a sequence of some english words) or use a list of precomputed OTPs.
i think (good) password vs. ssh-keys is both okay from the security point of view. But ssh-keys have much more convenience, where you have them (with ssh-agent you type your password only once, agent forwarding, etc.), and passwords are a sane fallback for when you just somewhere and downloaded putty to access your server. another good option for not so trustworthy environments are one-time-passwords. There is a pam module for this, and you just carry a list of 100 OTPs.
why would you want passwords in your lan? when you need passwords sometimes, when you are on the road with your laptop or at some pc, which is not yours, okay there its useful. But in you own lan, you always can access some ssh-key. So your policy isn't very useful that way.
Slashdot Mirror
If you have correct SPF, you will most likely get more spam. Why? Someone spams mailservers with your domainname, then it bounces because of failed SPF, and many mailservers are configured wrong, so you will get backscatter spam.
The irony of this is, that SPF says "it wasn't me" and the wrong configured mailservers then send YOU an answer saying "hey, we're not accepting your mail, because your SPF says it is not your mail".
the copies ARE worth something, because you want to play.
But this just means, you cannot sell more copies than are needed for the players. If one stops playing and another one starts playing, they can trade the license.
so its the best for both: seller and buyer. So ... resell more digital goods.
a game is nothing you consume. Its like a book. you read/play it once, then you sell it to the next person for a cheaper price.
thats the problem, the article addresses.
and when i bought it? Doesn't i have a right to reinstall it to new devices, independed from the author removing it from the store (for new sales)?!
but debian testing has freezes. Will Ubuntu-Rolling have Freezes half a year before a new LTS?
you have a gui on the client. its called xterm, or if you like a better terminal urxvt.
LMDE is a rolling release, too.
but it will only be as stable as a normal release now.
but there is Debian/kBSD, isn't it? all the apt-get goodness with freebsd kernel?
like most of the html5 stuff ... nice draft, but nothing you can expect from every browser.
seems like you do not know the new html5 file-api.
is there ANY case, where watermarks on digital music were accepted as an proof? ... i cannot tell what amazon writes into my mp3s. Maybe its an id, which points to me as a person. maybe their software is faulty and it describes YOUR account. So when someone tells me "a mp3 with your amazon id was found", they still need to prove, that the only possiblity of this is, that i released it somewhere. And thats not the case, anyone can write anything in files.
Just imagine
ah, sorry ... i did not consider the whole thing. The amazon case IS special:
you buy a combo pack: CD+MP3s. So you can sell one of them keeping the other part, as you may sell one CD of a collection of 6 CDs. Noone can forbid you to split your possession and selling only a part of it.
why do you need to discuss this? Its just the same as if you would have ripped the CD yourself.
And what's then the case, is not sooo easy to say. The first approach would be, that you need to delete the copy, as you're selling your license. But then you have the right to make seven private copies, and even give them to friends. So you may be able to declare your copy as one of the private copys (just think of giving it to someone (private copy law), who gives it back to you (without leaving a copy at his pc)).
at least in europe, you are allowed to do that with a mp3 download as well. Of course, if there is DRM, it may prevent it technically.
No, its not. You drop the price not after a week, but after you sold 1000 copies OR after half a year. So either the people who can pay much want the book now and pay 20 eur, or they just are not there, then you sell it for cheap after half a year (which should be enough time, that no one has the patience to wait just for a few bucks, if they can affort it to the bigger price). Of course this is a tradeoff and you can try to play with the threshold of price/copys to sell before dropping the price/wait time in which noone buys the book.
its the same argument as saying "hey, books cost money, because someone had to type them".
no, thats a fraction of the price. most money is for the content. So, go and add 5 cent per book and then add the ebook to the purchase. Its okay. Or stay with the current price and see the ebook as additional very cheap marketing.
The point why removing code is so hard is not, that its hard to restore. We have VCS for this.
But its hard to discover, the code ever existed. Who goes to the VCS and searches for old commits, when implementing a new function? If you weren't there when the code were in use, its unlikely you find it in the VCS instead of rewriting it.
So removing code is a decision about making it hard to find, that it ever existed.
One solution would be to remove and leave a comment behind "here was code, which was removed in a commit at $DATE". What other solutions are there, for this dilemma?
use kwin and try to change the level of focus stealing prevention (maybe only with a per window rule)
Your windows will be encrypted, and only be decrypted by a valid uefi.
its called libpam-opie. There are debian packages, and googling finds some howtos. I'm not sure which to link, because some apply on freebsd, others are written in german ... so search for yourself which one works for you.
In the end you get prompted with a seed ((almost) constant per account) and a serial number, and can generate the corrsponding OTP (a sequence of some english words) or use a list of precomputed OTPs.
i think (good) password vs. ssh-keys is both okay from the security point of view. But ssh-keys have much more convenience, where you have them (with ssh-agent you type your password only once, agent forwarding, etc.), and passwords are a sane fallback for when you just somewhere and downloaded putty to access your server. another good option for not so trustworthy environments are one-time-passwords. There is a pam module for this, and you just carry a list of 100 OTPs.
why would you want passwords in your lan?
when you need passwords sometimes, when you are on the road with your laptop or at some pc, which is not yours, okay there its useful. But in you own lan, you always can access some ssh-key. So your policy isn't very useful that way.