Neither of those provides any mechanism for downsampling an image before uploading it. In fact, from a same-origin security model perspective, JS code isn't even supposed to be able to access the image data before uploading it, though I think they've left some holes where devs can get around that....

For the first two, obviously, you either persuade them or you find someone else to work for / rent from. Freedom of association means that they have no obligation to hire you or rent out their property to you, regardless of the reason. Hiding information about your past which you know would be considered relevant amounts to fraud.

If your treatment by a police officer or any other representative of the government acting in an official capacity is influenced by outdated posts on social media sites, or anything else apart from your current standing under the law, you've got bigger issues. In any case, odds are that a law permitting you to delete your information from the Internet, even if it could somehow be implemented effectively, would not prevent the police from learning about your youthful indiscretions.

I would ass-u-me that this would mean that over a period of time X, a current generation chip would process Y commands consuming N units of energy.

The new chip would perform 2Y commands over X time while only consuming .8N units of energy.

Or that each command execution would take 80% of the energy of a current gen chip, but that it could complete twice as many of them in the same time period, meaning a net increase of ~60% energy consumption at sustained max load.

Tons of ways to play with the statistics on this one, and the 100% performance improvement and 20% energy efficiency improvement are not mutually exclusive. But the summary doesn't give any context or detail, so without RTFA, it should be considered nothing more than marketing speak.

-Rick

The /proc directory is a virtual filesystem; nothing in there survives rebooting. If you want the sysrq keys to remain enabled after a reboot you need to write to that file from an init script.

Actually, given a drone's capacity to record or transmit video it probably qualifies as a surveillance device, and there's plenty of case law which says using surveillance devices to circumvent what would otherwise be private is indeed illegal. I doubt new laws are necessary at all.

Most of the devs here come from COBOL/Mainframe backgrounds. So capslock is heavily abused, as is 4 letter abbreviations for every word, and excessive use of underscores.

-Rick

Depending on state and local ordinances, it may also fall under Aerial Trespass, the laws typically used to force telephone/cable/power companies to run their lines under ground or around property lines.

-Rick

Or an under barrel mounted grenade launcher. check out the M-203 :)

-Rick

There's nothing wrong with wanting it gone, perhaps, but what's wrong about enforcing that desire by law is that it amounts to trying to censor factual information about the past. You don't have to tell anyone about your more embarrassing historical moments, but it's wrong to forcibly prevent others from sharing what information they possess.

The right answer here is to simply recognize that people change, that it's normal to have some things in one's past that may be embarrassing (or even outright illegal), that everyone goes through this period of growing up, and that what one said or did as a child—or for that matter, as a younger adult—does not necessarily correlate with one's views or behavior in the present.

As another noted on the Red Site:

"We'll know everything* about you and we'll be snitching (including your BitLocker key) whenever and/or to anyone we think is in our interest to. Starting Aug 15"[1]

In particular, this is more than a little disturbing.

"But Microsoftâ(TM)s updated privacy policy is not only bad news for privacy. Your free speech rights can also be violated on an ad hoc basis as the company warns:

In particular, âoeWe will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary toâ, for example, âoeprotect their customersâ or âoeenforce the terms governing
the use of the servicesâ."

As with all things Microsoft, use at your own risk. Only now, the risks to you personally are higher than ever before.

[1]https://soylentnews.org/breakingnews/comments.pl?sid=8667&cid=215390#commentwrap

Or Am I missing something?

No one will be able to find the jewels among the ocean of crap.

So when the NSA intercepts your hardware before it's delivered?

Just look for the guy in the black suit, sunglasses, and earpiece lurking around the door of your server room with a cell phone plugged into his laptop.

I would correct that even further.

It isn't about the fittest or death risk, it's about being able to procreate and survive.

In your species example of the 4, 6, and 10 mph creature. If the live birth rate of the creature declines as their speed increases (musculature takes energy/hormones away from breeding, high speed movements cause more lost pregnancies, etc...) than the 4mph species may actually be the winner as they will out-bread the 6 and 10mph variants.

Now, throw a 5 mph predator into the mix and the picture may change. If the 4mph variant can still breed fast enough to offset the deaths to the predator and out populate the higher speed variants, then it could still be the winner.

More likely though, the 6mph critter would win out as it is able to out breed the 10mph critter and would suffer significantly less losses than the 4mph critter to 5mph predators.

It all comes down to procreation. Which is the basic of the movie Idiocracy.

-Rick

This bug is in the JIT optimizer of the 4.6 framework. For apps you are developing, it's absolutely no problem, you just go into the compiler settings and uncheck the 'optimize' setting.

The problem though, is that the 4.6 framework is an in-place replacement for the 4.5 framework, which was an in-place replacement for the 4.0 framework. And the JIT optimizer is on by default. So if you install the 4.6 framework, it could potentially introduce this bug into any application developed targeting the 4.0, 4.5, or 4.6 framework that is already distributed.

Luckily, it appears as though the issue is a combination of a nullable int that has a bug in the boxing/unboxing of it's operator when calling the .hasValue method. So the actual number of places where this will actually pop up is hopefully quite limited.

That said, MS better get this patch deployed ASAP. Or if you are in a critical hurry, the correction has already been committed to the .Net Git repo, so you can brave a build from that.

-Rick