Have a weekly piece of work, fast and short, handed in that checks whether people understood the previous week's lectures. Release lecture notes, podcasts, or anything else only to those who were in the lectures immediately after the lecture, and then to everybody after the weekly work is handed in. A simple worksheet, which doesn't even need to count towards the degree but should get a stern word if ignored and possible discipline if repeatedly ignored, is not a huge workload on the students.
On the other hand, your students will always be able to share the information with absent friends. Any restriction you try and place can be worked round. You may as well leave no restrictions and put the lecture material online publicly, for anyone anywhere to benefit from.
It still leaves the issue of those who kill in the heat of the moment, who didn't go out and plan to do it, who would have found it harder to do if they didn't already legally own a firearm.
But then, guns aren't the only way to kill someone.
What you've said, in essence, is "turning off sound turns off the sound". Of course it does. But that's not a solution in the slightest. There is absolutely no reason why we should not be able to disable a sound like that.
Although if it's the POST beep equivalent, that's another matter, I suppose...
Actually, everybody I know refers to it in such situations as lego. In a collective singular form. "This lego" refers to the whole lot, as does "this coal".
Relatively simple to answer. What they have created, in essence, is just an extension for IE. And an IE extension has a much larger likely userbase than an FF one.
The one problem I have with that gun law argument is that if guns cannot be obtained legally, there could be less accidents and less spontaneous use of them. Naturally, I have no idea what the extent of that would be. (I also am unsure where I stand on that issue for various reasons...)
Either way, except in the case of accidents, the responsibility is still with the person pulling the trigger. And that applies to most things.
Alcohol may be part of the cause of various problems, but it's not an excuse - you CHOSE to drink in the first place; if you cannot control yourself when you drink, then don't drink. Same with anything else.
I can see major problems with that deletion behaviour. If you've accidentally deleted something, and you're trying to restore it, deleting the other copy really isn't productive.
If it's already prohibited, why do we need DRM? It's plain to see that DRM does not stop people bypassing it if they wish, and making bypassing such DRM illegal makes no difference whatsoever if the original intent was illegal.
Apple's DRM prevents me from doing various things that I wish to do, including playing music on MY choice of media player (software or hardware, either applies). As does all other DRM. That itself is sufficient reason for me to dislike it regardless of any other issues.
In that case, you'll have to use non-GPLv3 software. That, or contact all authors of the relevant software (including patches) and ask for special permission.
You do have the freedom to decide what you do with your code - but someone else has the freedom to impose conditions on their own code, including forcing any derivatives of THEIR code to be licensed in a certain way. If you don't like the restrictions that gives you, don't use their code.
Exactly as you say people should be able to do - THEY CAN!
Slashdot Mirror
One possible way to do it:
Have a weekly piece of work, fast and short, handed in that checks whether people understood the previous week's lectures. Release lecture notes, podcasts, or anything else only to those who were in the lectures immediately after the lecture, and then to everybody after the weekly work is handed in. A simple worksheet, which doesn't even need to count towards the degree but should get a stern word if ignored and possible discipline if repeatedly ignored, is not a huge workload on the students.
On the other hand, your students will always be able to share the information with absent friends. Any restriction you try and place can be worked round. You may as well leave no restrictions and put the lecture material online publicly, for anyone anywhere to benefit from.
Ah, that makes sense.
These days you don't need a lot for good-quality homemade recordings.
Demons don't have reflections.
You're installing an unfinished, unsupported OS on your security systems?
This doesn't sound like an amazing idea to me.
Hmmm. Hadn't thought of it that way.
That's a fair point.
It still leaves the issue of those who kill in the heat of the moment, who didn't go out and plan to do it, who would have found it harder to do if they didn't already legally own a firearm.
But then, guns aren't the only way to kill someone.
What you've said, in essence, is "turning off sound turns off the sound". Of course it does. But that's not a solution in the slightest. There is absolutely no reason why we should not be able to disable a sound like that.
Although if it's the POST beep equivalent, that's another matter, I suppose...
The close button at the end is great for closing lots at once - the individual ones are, to me, easier for closing the individual tabs.
Actually, everybody I know refers to it in such situations as lego. In a collective singular form. "This lego" refers to the whole lot, as does "this coal".
And they still suck. I know this first hand; I've finally convinced the parental being to change his connection provider away from them.
Yeah, probably; I thought of that while I was writing that post.
Relatively simple to answer. What they have created, in essence, is just an extension for IE. And an IE extension has a much larger likely userbase than an FF one.
Unfortunately.
The one problem I have with that gun law argument is that if guns cannot be obtained legally, there could be less accidents and less spontaneous use of them. Naturally, I have no idea what the extent of that would be. (I also am unsure where I stand on that issue for various reasons...)
Either way, except in the case of accidents, the responsibility is still with the person pulling the trigger. And that applies to most things.
Alcohol may be part of the cause of various problems, but it's not an excuse - you CHOSE to drink in the first place; if you cannot control yourself when you drink, then don't drink. Same with anything else.
In IE. This apparently uses IE to do all its work, simply removing caches and logs and stuff.
It still wasn't free.
In this country, local rate (0845) calls are not free.
I can see major problems with that deletion behaviour. If you've accidentally deleted something, and you're trying to restore it, deleting the other copy really isn't productive.
Except that most printers then proceed to clean the heads every time you turn it on, print a page, change the ink, and so on.
It wouldn't help much.
Exactly.
So why should we, the consumers, accept it?
If it's already prohibited, why do we need DRM? It's plain to see that DRM does not stop people bypassing it if they wish, and making bypassing such DRM illegal makes no difference whatsoever if the original intent was illegal.
Apple's DRM prevents me from doing various things that I wish to do, including playing music on MY choice of media player (software or hardware, either applies). As does all other DRM. That itself is sufficient reason for me to dislike it regardless of any other issues.
In that case, you'll have to use non-GPLv3 software. That, or contact all authors of the relevant software (including patches) and ask for special permission.
My father's car gets over 50mpg on a good day.
Well, it did til he rolled it through a stone wall.
I don't know if anybody's ever asked Tivo that. Maybe someone should?
As far as I know, you're right. The linux kernel is stuck as, and will likely ALWAYS be stuck as, GPLv2.
You do have the freedom to decide what you do with your code - but someone else has the freedom to impose conditions on their own code, including forcing any derivatives of THEIR code to be licensed in a certain way. If you don't like the restrictions that gives you, don't use their code.
Exactly as you say people should be able to do - THEY CAN!