The instant she was expelled, her student visa went POOF. She HAD to leave
But lets look at the other side, what the university alleges is multiple felonies. If they're so sure she did it, why didn't they report these serious crimes to law enforcement?
Not really. It's hard enough to sue a large entity that has an active legal department when you are a citizen of the same country. It's really really hard to do so when you are a citizen of a different country and you aren't even a resident here. Her student visa went *poof* as soon as she was formally expelled, so she had to go home already. So she is in another country, unemployed, and the proud owner of a five figure debt, Not suing doesn't really say anything about the potential merits of a suit.
A zillion years ago, we delayed falling back one year, so I went to school in the dark. I can assure you, me and the other kids quite enjoyed it. It was a great excuse to take a flashlight to school if nothing else.
These days, they'd probably enjoy how well the LEDs in their sneakers show up.
The only problem is you'd have clueless PHBs that insist that 9:00 is 9:00, so the office will not be changing it's hours when the clock goes to GMT. Anyonme who thinks they're going to lazily saunter into the office at 12:00 (just as the sun is rising) can find a new job. It's the same reason the proposal to pin the clock to an offset and let businesses have summer hours and winter hours is a non-starter.
I suspect the differing market in the EU does make a difference. Here in the U.S. you mostly have to pick the carrier that best covers the areas you expect to be in, then choose a phone they support.
If you CAN choose a thicker more durable phone, you don't need a case for it. And as long as you have a thicker phone, it might as well have a decent battery and a headphone jack.
It's probably worth Oracle considering that it's 20 years old because up until Oracle, it was somewhat open and didn't try to make you rewrite everything to please the new version.
But since they're Oracle, they'll blame someone else when the new version tanks.
It's easy to make physical presence necessary to update a phone.
As for the headphone and more battery, HAHAHAHAHAHA. They'll just make it thinner and more fragile instead of adding more battery. All so the buyer can immediately lock it away in a chunky case to restore the durability that should never have been engineered out in the first place.
If they really want to continue with sales, they're going to have to get over their idea that everybody wants X (whatever X happens to be today) and recognize that some want X and some want Y which may be mutually exclusive with X. They can either sell X, Y or one of each.
It's not a matter of physics really, other than the speed of light and the size of the components on the die preventing us from just speeding up a simple serial processor with a TB of RAM as fast as cache on die.
Modern CPUs do their best to work around those limitations through pipelining, speculative execution, and speculative memory operations. The principal being that as long as the actual resulting computation once the speculations are all retired (either incorporated into the result or discarded) is indistinguishable from a simple "virtual" CPU that simply did the computation in the natural thread order but is magically faster.
So far, so good. The problem happens when that concept is pushed to the breaking point. We can look further ahead and do even more speculative execution if the processor can make accurate guesses as to how likely a particular speculative execution is to pay off. Those guesses can become more accurate if the CPU can "learn' more about the liklihood based on previous passes through a loop. This is the point where Spectre rears it's ugly head. The liklihood depends on the data that only the process should know.
Even all of that would be OK except that the speculative execution affects what memory gets loaded into the cache. If the CPU always did the speculative execution or never did the speculative execution, the state of the cache would reveal nothing. But if it only sometimes does the speculative execution, the cache state may reveal to other processes when the CPU did or did not speculate. If that decision is based on private data, that data is revealed outside of the process. Note that if discarding a failed speculation also reverted the cache to the pre-speculation state, there would also be no leak.
Honestly, it's a fairly subtle leak, so it's little wonder so many CPUs share the flaw.
meltdown is a special case where even the permission check is done out of order during speculation. That one is Intel specific. Other architectures either do the permission check before they decide to speculate further or just don't speculate when a permission check would be needed.
Note, however, that even if all speculative execution was disabled, there still exists a possible information leak based on how long it takes to execute instructions in order without cache effects. That's why constant time crypto functions are desirable. That is functions that take the same amount of time no matter what the input data is.
If we actually reprocess the "waste", we get mostly fuel ready to use and a small amount of actual waste that needs to be contained for 200-500 years depending on how cautious you want to be.
The part that lasts 10,000 years is the same stuff found in naturally occurring rocks, but we can get rid of it by "burning" it in a reactor.
Actually, they do NOT glow in the dark. While not recommended, there are people living in the Chernobyl exclusion zone eating food they grow and hunt in the area..
The concept is fine (in some cases even mathematically provable). It doesn't become a problem until you try to push beyond what you can actually get away with or worse, knowingly cut corners and hope nobody notices.
Rowhammer is indeed a bit flipping attack. The idea here is that if you can figure out the physical page layout, you can make a better guess about what bits you might like to flip in the page table to make a R/O page R/W or to map a physical page you shouldn't see into your address space.
It's still a 'statistical' attack. It won't always work before something else flips and crashes the machine.
If you get rid of the HIV, their immune system will recover and kill the other infections. They may well have lasting effects from their time with AIDS.
Slashdot Mirror
The instant she was expelled, her student visa went POOF. She HAD to leave
But lets look at the other side, what the university alleges is multiple felonies. If they're so sure she did it, why didn't they report these serious crimes to law enforcement?
Likewise, we've seen no evidence that she did anything at all wrong.
Not really. It's hard enough to sue a large entity that has an active legal department when you are a citizen of the same country. It's really really hard to do so when you are a citizen of a different country and you aren't even a resident here. Her student visa went *poof* as soon as she was formally expelled, so she had to go home already. So she is in another country, unemployed, and the proud owner of a five figure debt, Not suing doesn't really say anything about the potential merits of a suit.
On the other hand, expanding the strike zone (for the pitcher) and shrinking it (for the batter) are currently legitimate strategies.
Plus, with non-DST at least noon happens when the sun is directly overhead, which has some real meaning.
Actually, within a standard time zone, high noon will be roughly between 11:30 and 12:30 according to the clock depending on your location.
A zillion years ago, we delayed falling back one year, so I went to school in the dark. I can assure you, me and the other kids quite enjoyed it. It was a great excuse to take a flashlight to school if nothing else.
These days, they'd probably enjoy how well the LEDs in their sneakers show up.
Which would be at least 3 hours before sunrise if my country would choose permanent DST.
As opposed to the two hours before sunrise that you already have to deal with somehow.
How hard would it be to do that somehow for an additional hour on winter mornings?Either way, you're at work before the sun comes up.
The only problem is you'd have clueless PHBs that insist that 9:00 is 9:00, so the office will not be changing it's hours when the clock goes to GMT. Anyonme who thinks they're going to lazily saunter into the office at 12:00 (just as the sun is rising) can find a new job. It's the same reason the proposal to pin the clock to an offset and let businesses have summer hours and winter hours is a non-starter.
I suspect the differing market in the EU does make a difference. Here in the U.S. you mostly have to pick the carrier that best covers the areas you expect to be in, then choose a phone they support.
If you CAN choose a thicker more durable phone, you don't need a case for it. And as long as you have a thicker phone, it might as well have a decent battery and a headphone jack.
Most people seem to prefer thin, so they would be stupid to not engineer all that out.
Given that most thin phones I see "in the wild" are encased in thick chunky protective covers, I'm not so sure about that.
People choose those because those are the ones with faster processors and brighter screens (features they ACTUALLY want).
The thick chunky phones with replacable batteries and a headphone jack tend to have otherwise older and slower tech.
It's probably worth Oracle considering that it's 20 years old because up until Oracle, it was somewhat open and didn't try to make you rewrite everything to please the new version.
But since they're Oracle, they'll blame someone else when the new version tanks.
Actually, Python 2.7 supports iterators.
The "coin" part of Bitcoin is just an analogy. It's just balances moving around, there are no serialized tokens of any kind.
It's easy to make physical presence necessary to update a phone.
As for the headphone and more battery, HAHAHAHAHAHA. They'll just make it thinner and more fragile instead of adding more battery. All so the buyer can immediately lock it away in a chunky case to restore the durability that should never have been engineered out in the first place.
If they really want to continue with sales, they're going to have to get over their idea that everybody wants X (whatever X happens to be today) and recognize that some want X and some want Y which may be mutually exclusive with X. They can either sell X, Y or one of each.
I might actually pay money to watch Zuck play "Climbing for Dollars".
It's not a matter of physics really, other than the speed of light and the size of the components on the die preventing us from just speeding up a simple serial processor with a TB of RAM as fast as cache on die.
Modern CPUs do their best to work around those limitations through pipelining, speculative execution, and speculative memory operations. The principal being that as long as the actual resulting computation once the speculations are all retired (either incorporated into the result or discarded) is indistinguishable from a simple "virtual" CPU that simply did the computation in the natural thread order but is magically faster.
So far, so good. The problem happens when that concept is pushed to the breaking point. We can look further ahead and do even more speculative execution if the processor can make accurate guesses as to how likely a particular speculative execution is to pay off. Those guesses can become more accurate if the CPU can "learn' more about the liklihood based on previous passes through a loop. This is the point where Spectre rears it's ugly head. The liklihood depends on the data that only the process should know.
Even all of that would be OK except that the speculative execution affects what memory gets loaded into the cache. If the CPU always did the speculative execution or never did the speculative execution, the state of the cache would reveal nothing. But if it only sometimes does the speculative execution, the cache state may reveal to other processes when the CPU did or did not speculate. If that decision is based on private data, that data is revealed outside of the process. Note that if discarding a failed speculation also reverted the cache to the pre-speculation state, there would also be no leak.
Honestly, it's a fairly subtle leak, so it's little wonder so many CPUs share the flaw.
meltdown is a special case where even the permission check is done out of order during speculation. That one is Intel specific. Other architectures either do the permission check before they decide to speculate further or just don't speculate when a permission check would be needed.
Note, however, that even if all speculative execution was disabled, there still exists a possible information leak based on how long it takes to execute instructions in order without cache effects. That's why constant time crypto functions are desirable. That is functions that take the same amount of time no matter what the input data is.
About that 10,000 years thing, it's FUD.
If we actually reprocess the "waste", we get mostly fuel ready to use and a small amount of actual waste that needs to be contained for 200-500 years depending on how cautious you want to be.
The part that lasts 10,000 years is the same stuff found in naturally occurring rocks, but we can get rid of it by "burning" it in a reactor.
Actually, they do NOT glow in the dark. While not recommended, there are people living in the Chernobyl exclusion zone eating food they grow and hunt in the area..
The concept is fine (in some cases even mathematically provable). It doesn't become a problem until you try to push beyond what you can actually get away with or worse, knowingly cut corners and hope nobody notices.
Possibly, but so far, Intel HAS shown more flaws, more serious flaws, and a bigger performance hit from the mitigations.
Rowhammer is indeed a bit flipping attack. The idea here is that if you can figure out the physical page layout, you can make a better guess about what bits you might like to flip in the page table to make a R/O page R/W or to map a physical page you shouldn't see into your address space.
It's still a 'statistical' attack. It won't always work before something else flips and crashes the machine.
The weakness is not in JS itself, but JS from a hostile web site is the most likely vector for code that uses the flaw to attack a desktop machine.
If you want to be a stickler, it also means "we injected this non-resistant supject with the same strain and he got AIDS". You first...
If you get rid of the HIV, their immune system will recover and kill the other infections. They may well have lasting effects from their time with AIDS.
Increased likelihood of a future symptomatic condition is a negative effect.