This is coherent light.
This is coherent light.
Maximum line of sight. Inclination, curve, drainage, presence of sidewalk, distance to intersection, distance to driveway, populaton of children, proximity to school, width, apparent width.
Then setup a traffic cone at various detail points in the road and measure the distance to the cone to make cars stop. You just need a cone, adjustable speed limit indicator, and a tape measure.
Either the grocery store pays by rounding the final price down, or the customer pays when it gets rounded up. Or is it going to alternate? Even days, rounds to the customer favor, odd days it rounds against?
The site does not choose the ads based on safety. The site sets aside space that is sold to different ad brokers who use brokers who have no idea what ads are going to be run. It is dangerous by design.
Until websites stop running content provided by other (anonymous) people, there ARE no safe ads. Its broken by design.
Your claim that you never had a problem could end tonight, tomorrow, or the day after. Then what? Are you going to apologize to everyone for failing to understand the problem and telling them it was safe. Esp when professional security researchers are telling you its NOT safe?
The www is a infinite bag of untrusted/untrustworthy data that your your flawed browser sifts through. Its was already a disaster waiting to happen. The problem is, the disaster has become automated, financed, and profitable.
Can we enumerate the reasons why the the browser needs to run with the same user ID as the person that owns files?
I can think of one: access to local files for upload or download. But it seems like there could be a mechanism to hand off files to and from the browser that doesn't give it direct access. Some IPC mechanism or a filesystem-based dmz.
At this point, I really do not understand why the industry is not moving to make the browser an untrusted entity on the computer. Taking away its ability to access files, navigate the filesystem, or run programs.
They need to issue a recovery password for every account. This would be a serial number in case the account ever gets hijacked. It can only get you in to reset your password. It could be written down and stored in a safe or in a safety deposit box. And it cannot be changed. It would be displayed only one time by the website and never be visible again to anyone. So you click on the link, it says "record this" and you write it down and put it in a safe. And that link would never work again.
Yes yes, I know, you hate the idea.
If the default is "on" , what if a bug in the code resets the setting or ignores the setting. Are there any indicators that this information is going out? Can there be any indicators? What is the amount of encrypted traffic going out from the system to microsoft? Any way to look at what is being sent at any point in time? Does it ever log what was sent? Can it?
Somebody will always be annoyed about something. Are they going to ban religion or atheism boards next? If they want to protect sensitive ears, then they should set-up an opt-in flag that will hide inflammatory reddts from searches and casual browsing.
You may need a (screamin) front-end machine that splits up the work and hands it off to multiple multi-core machines. These multi-core machines may only be available at lower clock-speeds.
Dont just "look at your application". But look at what parts of your application are subject to parallelism and what parts must stay single threaded. You may need a special single-thread machine that can keep the other ones fed.
If we are rightly scared of browser-borne infections and intrusions, then why are we still running browsers on our machines? Why not designate a machine, outside the firewall / in the DMZ, that runs ALL the browsers. The user logs into that machine, and the browser display events are sent back to the client machine. The safe client machine never runs a single snippet of plugin, or gobbles a single byte of untrusted network traffic. The client machine does not even -know- how to get to the internet.
Sending receiving files can be locked down and logged. Or prevented.
The sound device would be a pain, and might require a new protocol, but this would solve many problems. I think it might make SSL better too (no proxy bs).
Perhaps a specialized (corporate) browser nexus product could be offered...with sound and optimized for the browser.
The client machine never talks to the internet. It just sees pictures of it.
What would it feel like to live there? Would you have to be careful walking? How long would it take to adapt.
g = 3.75 m/s^2 vs 9.8 m/s^2
Trains don't really wander around randomly. So its not necessary to use the GPS system. Fixed point emitters over the tracks using simple technology would exactly position the train and insure reception no matter what the conditions. Even inside a tunnel.
I understand that putting new hardware into the trains is hard, expensive and difficult to clear for safety. But putting new hardware into the operators hands is not. Put a friggin electronic helmet on his head with a siren that goes off if the train is too fast for its registered weight / vs the track he is on. Tell him he fired if the siren goes off.
Heck, put a tens unit on it.
I would suggest using hydraulics and fiberoptics. Dont bother with active circuits at all. If all you want to do is look and grab, go really old school. Dont use amplifiers when two tin cans and a string will survive the radiation.
They have it. We want it. Make up an excuse. Take it.
Asynchronous inputs are at the root of our race problems. -- D. Winker and F. Prosser