I'm for it.
Maybe this will get webmasters to finally give some thought to bandwidth instead of cramming all kinds of junk into their layouts.
348 publicly visible posts • joined 17 Apr 2009
It seems to me the key issue is whether the protest was calibrated to actually disable the web site in question, or merely be noticed. Much like a real sit-in could either try to blockade a building or just attract attention.
On the other hand if he's calling it civil disobedience, he shouldn't exactly be surprised if it turns out to be illegal. That's kind of the point, isn't it?
If I'm not mistaken, it's a different meaning of "obscene". The old obscene publication law applied to content that "tends to deprave and corrupt", the new law directs that "obscene" should be assigned the ordinary dictionary meaning, "highly offensive".
Clearly the latter is a much lower standard, considering it's doubtful that the former even exists.
Atrocities aside, I'm curious about Wikileaks' statement they "obtained and decrypted" the video. Are they claiming they can break military encryption?
That seems unlikely, though we learned here: http://www.theregister.co.uk/2009/12/17/us_drones_hacked/ that sometimes they don't even bother with encryption. But assuming they received this from a whistleblower why was it even encrypted, and how did they decrypt it? Unless they were simply given the key, but in that case it would be rather pointless to even mention.
And I think it may be counter-productive. They made the law too big a hassle to comply with so companies chose to bar children under 13 entirely. But predictably a great many of them sign up anyway, either with or without their parents' knowledge. And Facebook et al have neither the motivation nor the ability to actually enforce the rule.
So instead of having an open situation where younger children could have extra protection or supervision if needed, they have to hide and nobody really knows how many there are.
If their employee failed to verify the code as the result of some kind of clerical error, or even simply forgetting to do so, that would be ordinary negligence. But if he decided he just couldn't be arsed to check the code, even though he must have known it could result in the account being stolen, that as I understand it would be an example gross negligence.
But the girl's mother is of the opinion (which I happen to agree with) that it wasn't wrong at all. Maybe no wise, given that there creeps like Mr. Skum and his successor out there, but not wrong. A key part of the argument for this restraining order what that she had been deprived of the right to raise her children as she sees fit.
No, because the reasoning in this case was more complicated. And dealt with the fact the "education" program would have required the girls to write an essay about "why what they did was wrong", which is compelled speech. And the fact that the prosecutor threatened to retaliate if the exercised their constitution right not to speak by procecuting them for child pornography. And the fact that the prosecutor could not show probably cause(!) for the prosecution, leaving relation as the only explanation.
But yes, I think in due time it will be recognized that the law as it stands is an unacceptable restriction on young people's freedom of speach.
Except no, the way you described it is still a logical impossibility. You have to be sexual in order to sexualize something, and you have to be nonsexual to be sexualized, hence a person cannot do it to his or her self (short of timer travel).
Okay, yes. Education. But for the kind of harm you describe, two conditions are necessary.
1. The existence of naked pictures.
2. The belief that said pictures are a horrible shameful thing.
We could attempt to "educate away" either condition.
Since teens exploring their sexuality has been a constant throughout history, and cultural attitudes about nudity come and go, perhaps you're going after the wrong one.
It sounds like this relies on an assumption by Google that PDF docs won't change, or won't change frequently, like HTML pages do. If so that's a good trick, but I've sometimes wondered what's to stop somebody from simply serving a different file when Google asks for it than what rest of us get.
Freedom on the internet. It was nice while it lasted. Alright I know they're not going to be imposing global censorship any time soon, but I can't help feeling like this could be the beginning of the end.
Mostly because I am absolutely amazed the Internet has thus far been nearly free of large-scale meddling by either corporations of government. It's not perfect, but why mess with a good thing?
But the solution you describe isn't even on the table. It isn't an "everybody wins" result by any means either. What about all the owners of existing porn sites? Do they get kicked out of their old domains, or what? Sure they could go register the same name under .xxx but what about hotsex.com and hotsex.net, would they be forced to share or what? What about britishpornclips.co.uk? What right does ICANN have to tell an (ostensibly) sovereign nation what it can and can't put under its tld? Then there's situation of sites that are not primarily pornographic, but on occasion feature some mature content. Would it sounds like they would be forced to either move their whole site to xxx land, or else split it in two. Neither option sounds very attractive (or fair) to me.
Geez, hasn't this browser kerfuffle been going on for over a decade now? I don't understand how, of all the many anticompetitive, anti-consumer acts perpetrated by Microsoft and other tech companies every day, something as trivial as browser choice was selected as the important thing to focus on.
You'll get nothing but sympathy from me. No one should be subjected to that. I'm curious though, did Max Hardcore secretly replace your Bambi DVD with one of his his movies, or actually chain you to a chair and force you to watch that filth? But in either case, I think it's just reprehensible, and I hope he gets what's coming to him.
The whole system seem anachronistic to me. I guess it made sense to publish contact details in the early days when only governments, universities and large companies had domains, but that hasn't been true for well over a decade. Now that small businesses and private individuals regularly have one, it doesn't seem reasonable to require everybody to put their name address and phone number out there.
He's clearly behind a fence. Presumably it's tall enough that passer's-by can't normally see in. Google's streetview camera is mounted much higher than eye-level (I checked the view of my own neighborhood to confirm this). I admit I'm no expert on Finnish law either, but in the US the general rule is that you have an expectation of privacy if you can't be seen by a person on the sidewalk.
That would be COPPA, it doesn't actually prohibit sites like Twitter from allowing children under 13, but it imposes fairly onerous requirements for getting parental permission before collecting any personal information from them, including an email address. So many web sites decided it was easier to just ban preteens entirely.
I think it's perfectly logical to consider "negative trust" in this case. Zero trust merely means that when a anyone attempts to persuade you with official statistics, it has no effect. If you had negative trust, then you would be inclined to believe the opposite of whatever the statistics were purported to show.
I worked on a project that counters this quite effectively too. Basically it was a rod composed of blended aluminium phyllosilicates and graphite used to encode passwords on a cellulose substrate. This allowed a user to easily retain multiple login credentials for future reference, thereby enabling the use of unique passwords for each site.
The whole thing is stupid. Amazon is only proving that they too are a monopoly. What makes them think they have a right to decide how much publishers get paid? If the publishers ask too much they just don't get sales. That's how it's always worked. And if anything, with ebooks it should be less of a problem, due to quicker feedback.
Yes, it's Apple's fault. Why? Because they voluntarily took on the responsibility of policing what software people point on their iPhones. If I install malware on my computer, it's my own damn fault for not checking it out first. If I install software on my (jailed) iPhone than it must be software that Apple reviewed and found acceptable, so if it turns out to contain malware anyway, yes it's their fault.