This makes no sense at all. Trade secrets are not the problem that patents were invented to solve. I don't have hard numbers, but I suspect most (as in greater than 50%) trade secrets are not patent-able.
In fact, that they gave this info to the city suggests it's not a trade secret at all.
Trade secrets are just the excuse for getting this information hidden. They could have claimed copyright. Does that mean we should abolish that too? Because reading techdirt, I see report after report of problems "caused" by companies suing over copyright.
"So in the same way I’d argue we legalize drugs, why not have a careful, legal pathway to break into a phone?"
This reads to me as: Many would argue that legalizing drugs is generally bad. Not only can illegal drugs screw you up, illegal drugs helps enriches criminals and leads to increased criminal activity, due to the vast sums of money involved. Legalizing illegal drugs, while perhaps not that palatable to many, is a good idea because it helps combat the criminal activity made possible by illegal drugs.
Replace "illegal drugs" with "encryption" and "legalizing" with "backdooring".
I don't think you were involved with "building" the net. https encrypts content, not source or destination. HTTPS works over HTTP. So how exactly is it that they won't see the source of a given packet is youtube?
Unless someone along the way is caching youtube and responding to t-mobile's requests, your comment doesn't make much sense.
They're named target. It's like being surprised to be kicked when you're hanging around the local Kick Me.
To be fair, if this was Tupac, they might have a case. Is he really dead? Really?
Sure ZK, he might be a low-level soldier. But, the issue here is not that a soldier whose only job was tweeting was killed. The issue is the published sentiment, which is that the US should be justified in killing anyone who tweets something which is considered material support for ISIS.
Do you have any proof for "They were preventing exclusively republican organizations from..." Because as far as I can see, there were very few "republican" organizations on that list. Unless you are co-opting conservative, tea party, and other groups as being "exclusively republican".
Yeah, thanks for the stats that the freaking article says can be misleading.
There aren't stats on the total number of applications so if there were only 7 progressive groups that applied for such status, then that means 100% of progressive groups were vetted.
Clearly, you did not actually look at the numbers.
Umm, no. You get to listen to them. You're paying x amount to listen to whatever songs you want (subject to being available from your streaming provider). That does not convey ownership of said songs. Furthermore, the amortized cost per "listen" is much less (as you'd expect) than the cost of ever purchasing any one song.
So, you're not wasting a ton of money on crap music you don't want. As you get to choose the music and the cost to listen to unlimited amounts of music is much less than the costs to buy even a tiny fraction of said music.
If you take a selfie running in front of a bus, you will get tired.
If you take a take selfie running behind a bus, you will get exhausted.
If you take a selfie in cathouse, you will soon find yourself in doghouse.
If you take a selfie shooting off your mouth, you may find yourself losing face.
A selfie jumping off a cliff is a leap to conclusion.
Let's be clear about what happened. Mr. Lush did not lose his account. What happened is that google changed how it does urls on youtube.
Before, his channel was available through the url youtube.com/user/lush which due to how youtube did redirecting, could also be accessed at youtube.com/lush
Note, there was never an explicit agreement that the url youtube.com/lush was tied to his channel, it just so happened to work that way and people used it. The way countless programmers turn undocumented behavior in some platform into necessary features of their app.
Anyway, youtube changed things to allow custom names/urls. Lush cosmetics got youtube.com/lush and the whole issue began.
Note, you can still access Mr. Lush's channel at the original url. He still controls his account. Just the url hack that benefited him does so no longer.
While there are certainly PR arguments to be made around to granting control of that URL officially to Mr. Lush, what actually happened and what this article (and comments) seem to imply happened are quite different.
Hmm, then why do so many people seem to think it is ok for the government to have laws that violate my constitutional right to kill everyone I don't like?
Clearly, we establish laws in part to punish behavior that we as a society feel is wrong. Just like we don't care about the hurt conscience of a psychopath serial killer, we also don't care about the hurt conscience of racists or homophobes.
That's why contracts aren't written in code
Or some other logic/math/physics based language.
It is hard to write code that defines behavior A and only allows A. Well, it's easy, but A is typically very trivial, and ensuring the only A part requires a lot of code as well.
You're better off writing it in natural or legalese and enforcing it as a legal contract, where things like what both parties understood the agreement to mean become important and not what one party later to leverage the literal words on paper to mean.
Essentially, a smart contract needs to be both code + unit tests + regression tests + acceptance tests. And it needs to have a non-code meta layer that essentially says, if it does something other than what we've agreed because the code is flawed, that action is outside the contract.
It appears right now it's just the code portion. Unit tests let you know that your building blocks do what you want and only that one thing (mostly). Regression tests let you know that if you make a slight change somewhere, everything still works *like you already validated even if it doesn't seem like the change you made should affect anything else*. Acceptance tests essentially are the "everyone understands that X means ..." part of the contract. All of these "tests" are code BTW.
Then when a contract violates this, you can easily point to the behavior that's outside the acceptance test, and thus in violation of the "contract" even though the current smart contract as written would let it happen.
What's hilarious is that there's a whole "programming by contract" field which seems to have been ignored here.