Nice try. However, next time go digging for the truth before spouting out right-wing lies (pardon me, "alternative facts").
The facts are that she didn't check any "Native American" box on any application to a University or for a job. See the Boston Globe and The Atlantic. She did indentify herself as "Native American" in a commonly-used legal directory, but that's it. She neither sought nor received a "leg up" for that.
As far as the cookbook she did, indeed, contribute to that, and identify herself as Cherokee.
Based on her public statements she does, in fact, believe that she has Cherokee heritage, based on family anecdotes. Whether those anecdotes are 100% accurate is debatable. What's not debatable is that there's no harm in her belief, since she has never made any attempt to trade on any such heritage.
You've forgotten the catch-22 where the Court requires standing to bring a lawsuit. To have standing you must be able to show that your emails have been searched. That information is locked up behind "national security" so that you can't know if your emails have been searched. Thus, no standing; thus, no lawsuit is possible.
How our USA courts can possibly go along with this is beyond me but so far, much to my surprise and dismay, they almost always have.
Insurance policies are issued to drivers based on the driver's record, age, location, and other actuarial factors. If the driver is not a factor, then I don't see an insurance company issuing a policy "to a car."
I'm not sure that's correct. My insurance policy is specific to the car. I'm not insured under my policy if I drive, say, a friend's car. Moreover, there are terms in my insurance that insure someone else driving my car as a "guest driver."
The cost of my insurance is affected by my driving record, etc., as I am listed as the "primary driver." However, the policy sure appears to be tied to the car, not me.
In fact, I could easily see an insurance company issuing a policy that sets terms on driverless operation. At first, those terms would probably be expensive, given the lack of data on driverless performance and accidents. However, I would expect that the cost of insuring driverless operation would come down fast, as I expect driverless operation to be a lot safer than human operation. Indeed, I wouldn't be surprised to eventually see policies issued that charge a premium for people who insist on driving themselves.
Traffic citations are issued to drivers based on their actions while in operation of that motor vehicle. I don't see law enforcement willing to attempt to stop and ticket a driverless car.
What makes you think it would ever be necessary to ticket a driverless car? They don't break driving laws, save temporarily to improve safety (one of those interesting things that the Google driverless car devs had to program in: without the ability to temporarily speed, tailgate, etc., driverless cars were found to be less safe when running on the road with other cars with human drivers). Indeed, the advent of the driverless car is likely to precipitate a budget problem for many cities, as their ticket revenue dries up.
In any event, if an officer did decide to ticket a driverless car, it wouldn't be hard to issue a ticket to the owner, based on the license plate.
I am assuming that this restriction revolves around liability. It makes some sense: if a *driverless* car is fulfilling a ride request from, say, Uber, and the car gets in an accident, who is liable? Currently, it's most likely *Tesla*, not the owner. After all, the owner wasn't anywhere near the car at the time.
For owners that contract with the Tesla Network, liability will likely be spelled out in the contract that the contractors sign with Tesla. However, Tesla has no control over the terms that, say, Uber makes with their contractors. Thus, the restriction to the Tesla Network.
This notion does make me wonder, though: what about liability for *anyone* riding in the car without the owner? Wouldn't the same problem apply? Perhaps Tesla is willing to shoulder the potential liability since that's a much less frequent occurrence?
I would expect that the Tesla Network would explicitly address liability for their driverless cars, probably by spelling out the terms in the contract they make with their contractors. However, Tesla has no control over the terms that non-Tesla-Network services set for their contractors, and currently that would likely throw all liability for problems onto Tesla, not the owner of the car.
If/when legislation specifically spells out how liability falls out for driverless cars I would hope that Tesla would be able to, and would proceed to, relax these restrictions. However, in the current legal framework, this is not unreasonable.
The link is perfectly clear, Mike. The KKK are "bad guys." The First Amendment permits them to say whatever they want to say, but they're still "bad guys." Lawbreakers are also "bad guys" - at least, according to the FBI - as are those who help them, like Moxie. The First Amendment allows them to say whatever they want to say, but they're still "bad guys."
Remember, a person is never a villain in his own eyes. An FBI spokesman is likely to have a rather black-and-white view of the world, with the FBI white and the FBI's suspects black. To him/her, Moxie is self-evidently wrong-headed, like a KKK member, and no reasonable person should agree with him. Engaging in a debate with him would only elevate his ideas to the public, as if they had some possible validity. Therefore, they won't.
Mind you, I certainly don't *agree* with this spokesman. He or she clearly has no perception or conception that the FBI might ever abuse their power, nor that there may be times when breaking the law might be a good thing (Rosa Parks comes instantly to mind). However, I can certainly *understand* why they would make such an (outrageous) statement.
Moreover, that's the irony of this whole mess. If T-Mobile had limited BingeOn's effects to only partners whom they had worked with to auto-adjust the quality, and left out the throttling, they could legitimately call this a customer benefit. There are still the issues of opt-in/opt-out and just how easy or difficult they make it to turn it off and on, but those are less important to most people. It's the throttling that brought on the uproar.
Since the EU-US Safe Harbor set up is under review anyway, modify it to require that any data transferred out of Europe and into American servers must be encrypted in transit and at its destination server. It would make the verification process more significant (and, thus, more expensive) but it would go a long way toward re-legitimizing the process.
The beauty of such a rule is that it would prompt many companies to simply encrypt everything in-transit and on-server, rather than trying to set up something specific to EU-US. That would be a good thing.
Let's see some ordinances passed in cities around the nation that require City Council members to pay the attorney's fees for civil cases that the Council brings which lose. I'm betting that there would be a 99% reduction in said civil cases.
The fine was 1.2 *billion*. I'm sure that this was taken into account somehow - that's pretty much the only way you get a number that high.
Yet this was a settlement. There's a natural tendency to assume that they settled for a fine lower than what they actually made. The only other alternative seems to be that they saw a slam-dunk case in the making, so they scrambled to settle before receiving a verdict that may be even worse. This case seems unlikely to be that clear-cut, at least in a courtroom.
Copyright system supporters insist that copyright is like a form of welfare: a right to earn money.
What a great phrase! Let's rewrite the debate: start calling Copyright "Authors' Welfare" or "Publishers' Welfare". The term "welfare" has negative connotations to much of the American public, so if we can reshape the debate with these terms we can perhaps shift public sentiment against these insane copyright terms.
We can state something like, "It just makes sense to reduce the time that authors and, especially, publishers are feeding at the Welfare trough of excessive Copyright at the public's expense." There, you've insulted Copyright by equating it to Welfare and made it clear that these excessive Copyright terms are stealing from the public by taking Public Domain works away from them.
If you don't accept their terms, you're out of YouTube.
Baloney. You can post whatever you want, for free. YouTube won't interfere with that. Or, you can sign up for their Subscriber program. However, the Ad-Sense program is going away, so if you only post your videos there, they'll go away when that program goes away.
Someday, years from now, one of the main developers of ME3, who by that time will no longer be working for EA or Bioware, will come out and reveal how the ending of ME3 was messed up so badly. I am impatiently waiting for the day.
My guess is sheer arrogance of the lead developer, possibly aggravated by time pressure. However, I could readily be off.
I am concerned about the massive database that the NSA (and others) are compiling, because despite the fact that "I have never done anything wrong," I understand perfectly that I am, along with almost everyone else in the US, technically a felon due to the proliferation of laws. I now, or soon, will live at the sufferance of those with access to this database.
I am more concerned because the same database can and will be used to influence and/or control our elected representatives through blackmail. If it hasn't happened yet, it will - always in the name of patriotism, of course - and I then begin to wonder why there are so few representatives who are up in arms about the deceitfulness of the NSA. I'd think that the reps would be more paranoid, and more worried about what that database might eventually contain on them ... unless they already know, and are keeping quiet as a result.
Before Snowden I'd have dismissed this notion as a laughable conspiracy theory. I'm not laughing anymore.
what they wanted initially was known as a 'pen register', and amounted to giving the NSA access to monitor who a person was contacting/possible content monitoring. However, because that data stream being monitored is encrypted, the pen register told them nothing.
That's not what I recall. As I recall, Lavabit refused to comply with the pen register order. That's when the NSA went to court to force Lavabit to comply. Things escalated from there.
Clearly, Lavabit didn't implement a "proper" PGP system, with encryption/decryption happening at the client *only*, or handing over the SSL key wouldn't have granted access to users' emails (which seems to be what's being argued). I'm not sure how Lavabit did provide its secure email services, though.