Forgot your password?

Comment: Re:Connect with a VPN (Score 1) 388

by InvalidError (#47485005) Attached to: Verizon's Accidental Mea Culpa

And the reason why using VPNs or other work-arounds works is because they cause traffic to pass through one of Verizon's under-used routes instead of the overloaded routes between Verizon and Netflix preferred by Netflix's CDNs and transit providers.

If the Netflix traffic distribution was more evenly spread both geographically and across available peers, Verizon would have much fewer reasons to object to upgrades.

Comment: Re:"overwrites all files" How Many Times? (Score 1) 91

The overlap region between ideal track centers is still somewhat of a gap; albeit not a dead/silent one.

There will still be some residual information in there due to head deviations from the ideal path and when solving complex puzzles like reconstructing overwritten PRML blocks, every little extra hint counts.

I have little doubt it is possible to recover at least some data from PRML drives that have been erased once, maybe twice. But the process would probably require the precision and sensitivity of something like an atomic force microscope, which would be a "little" too much time and effort for the casual identity thief or creep.

Comment: Re:Sounds like radar to me. (Score 1) 42

If you want to use sonar to map the ocean, you measure multi-path delays, phase shift, attenuation, etc. using a receiver array too.

Radar does much of the same as well: you need the delay to calculate the distance, phase/doppler shift to calculate the speed and heading, signal strength to estimate the cross-section, etc.

You can go way beyond just measuring drift from nominal values. With a distributed receiver array, they could probably use multi-path delays, reflection, attenuation, etc. from thermals, air currents, moisture, etc. to calculate temperature and other parameters almost anywhere within the network's airspace.

Comment: Re:"overwrites all files" How Many Times? (Score 1) 91

There is still a gap between tracks in today's drives; just nowhere near as much so whatever signal might be available on the fringes will be much weaker.

The real killer for PRML-based drives is that to cope with the amount of noise the head receives from nearby tracks, the coding itself relies on statistical analysis to reconstruct the data. Whatever signal might be on the fringe will be some blend of the old data under the current track, the new data, data on the tracks to either side, the previous data on the tracks to either side, etc. There may not be enough signal left in-between tracks after a full PRNG erase or two to recover anything useful.

Comment: Re:I can really see the difference... not. (Score 2) 129

That's what magnifiers and optical microscopes are for.

Even if you cannot individually identify pixels, you can still notice the marginally sharper text/line-art edges, smoother gradients, reduced stair-casing along polygon edges in 3D applications, etc.

But beyond 300dpi at typical tablet/smartphone reading/playing distances, I doubt that many people would really care about difference between 300-350dpi and 400-450+dpi.

Comment: Re:What's the point? (Score 1) 129

There isn't much of a point in pushing display densities much beyond 300dpi for hand-held applications since most people can barely tell the difference but Apple was the first one to make a big deal out of it. Announcing higher resolutions sold many of the previous models and will sell future ones too - with the progress stagnation that has hit smartphones and tablets for much of the past two years, higher resolutions and the IGP power to drive them are almost the only two things that have improved by a fair amount.

Personally, I would be far more interested in seeing 1920x1200. 2GB RAM and 32GB SSD become the norm below 10"/$300. Right now, the N7-2013 is still practically the only tablet below $300 with those specs and price point. Most other devices below $300 launched in 2013-2014 have specs closer to the more ancient N7-2012 or sometimes even worse, which is sad, a shame and ridiculous. If analysts and manufacturers are surprised to see tablet sales dropped, they have not been paying attention to the crap the market has been flooded with for most of the past two years; no surprise sales are dropping when there is nothing worth upgrading to on the market.

Comment: Sounds like radar to me. (Score 1) 42

The only differences being that with cell towers, the receivers and transmitters are controlled by two independent parties and the signal itself was not intended for that particular purpose.

You know exactly where the tower is, you can easily reconstruct the RF signal as-transmitted by receiving the bitstream yourself and calculating the original signal as-sent. All that is left to do is compute the correlation between measured signals across your receiver network and weather along the receiver-transmitter path and their immediate surroundings.

This is a bit like a radar version of passive sonar.

Comment: Re: Failsafe? (Score 1) 468

Cameras can fail, the communication links between the camera and whatever serves video stream can fail, the displays themselves can fail, power to the displays can fail, etc.

If you do a simple HUD overlaid on top of the conventional glass window, at least you are not completely screwed even if there is a compounded instrumentation failure as long as you can still get visual cues somewhere such as the moon, stars, city lights, runway and slope guidance beacons when landing, etc.

As long as you still have some degree of flight control left, line-of-sight, skills and luck, you can land a plane even with extensive instrumentation failures - there have been many seemingly impossible yet successful landings.

Having cockpit displays/HUDs to aggregate, complement and supplement existing instruments is fine but for completely replacing direct line-of-sight as a backup? I don't think so.

Comment: Re:Will local rights holders sue? (Score 2) 153

by InvalidError (#47399323) Attached to: New Zealand ISP's Anti-Geoblocking Service Makes Waves

Geoblocking and all the unnecessary middlemen that try to use it to secure their artificial geographic monopolies need to die if they refuse to compete globally.

To be fair to local online vendors though, there would need to be an international standard for sales taxes such as one harmonized rate per country so international vendors would at least not need to deal with the countless regional variants within countries when charging foreign taxes. Another possibility would be to let financial institutions charge domestic taxes on the taxable part of electronic purchases since they are well-versed in the tax codes of whatever regions they do business in so vendors would not need to worry about managing international taxes at all.

Comment: Android development guidelines recommend Java (Score 1) 69

by InvalidError (#47373315) Attached to: ARM Launches Juno Reference Platform For 64-bit Android Developers

If developers do not want to worry about the underlying hardware, all they need to do is stick to Google's developer guidelines and use Java. Let the JRE and native recompiler abstract all the hardware-dependent stuff. Not quite as compute/power-efficient (at least in theory) but from what I have seen, there seems to be tons of developers who waste tons of cycles regardless of portable vs native anyway.

Comment: Re:It's too late (Score 1) 681

I'm using Classic Shell too and I agree it does fix nearly everything that annoyed me in Win 8.x

Many people on the other hand are still upset (exaggeratedly so IMO) with needing third-party applications to restore classic start menu functionality or are adamantly opposed to any sort of such work-around.

Comment: Re:Here's the problem. (Score 1) 205

If your "secure" applications run on Linux, Windows or any other major modern OS, that's hundreds of million lines of code that even experienced developers have little to no insight into and many of the security exploits that pop up, Heartbleed being the latest high-profile case, are tied to baked code and libraries that get reused by thousands of developers with implicit trust since almost nobody can afford to re-audit that code for themselves even when they have the expertise to do so.

Even if your application's own code is technically flawlessly secure, there are countless ways the OS, other applications running on the same machine and hardware may be used to undermine your otherwise perfect security.

The problems extend far beyond self-taught programming... and self-taught programmers are not intrinsically bad either.

Comment: Re:Here's the problem. (Score 1) 205

Systems these days are so hopelessly complex due to running full-blown OSes (mainly Linux derivatives like Android these days) for convenience that guaranteeing security is practically impossible most of the time since nobody ever knows the system inside-out so everyone is relying on everyone else making their own part of the source tree work properly without unforeseen unexpected interactions between software components and also with the hardware.

Most developers and companies do not have the time and resources to go over and get intimately acquainted with every minute detail of their development environment, libraries, OS, etc. to understand the millions of ways things can possibly go wrong assuming they even have access to the source code in the first place. If they had to do that before getting to work on their actual project, most of them would die from old age before doing anything so demanding that degree of understanding is simply not realistic.

The threat of severe legal penalties for things that are often nearly impossible to foresee would make tons of would-be developers give up on the idea - it simply makes no sense.

"Who cares if it doesn't do anything? It was made with our new Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..."