The attack vector is a bit vague, and I'm not sure how to bring this news to some of my clients.
Is the exploit only for when running services on/to the internet (IIS, Exchange webmail, etc - ) , or is visiting an https (TLS) website on and end-user enough to make the exploit happen (even in Firefox/Chrome and behind a tradional proxy server).
Sadly Microsoft does not explain the exact parameters that make this exploit tick - this makes risk assessment hard.
OK, so, there's microwaves producing forces on either end of the cavity, and one end is bigger and…
wouldn't the forces be proportional to the area normal to either direction? i.e. one end may be smaller, it may even be a point (making the cavity a cone), but microwaves bounce off of the tapered neck of the cavity too.
If this works, and if it's scale able, it would be something like the impulse drive. A normal spacedrive for speeds far below C and without space-warp.
This should be banned. Really. I don't want this on the same road as my loved ones. When you are driving, you are driving. Not reading/tweeting.
Even more, mounting "something" to the front window is illegal in a lot of places in the world [1]. At least Netherlands and U.S. In The Netherlands operating a phone while driving (voice operated carkit exempt) gives you a ~$250 fine.
Furthermore, obstructing part of your window is dangerous. You could miss something. And it's distracting (our eyes focus on motion).
>In The Netherlands operating a phone while driving (voice operated carkit exempt) gives you a ~$250 fine.
Sadly you're wrong. Holding a phone is illegal, operating it while in a car kit is officially nog prohibited.
>Artikel 61a
Het is degene die een motorvoertuig, bromfiets, snorfiets of gehandicaptenvoertuig dat is uitgerust met een motor bestuurt verboden tijdens het rijden een mobiele telefoon vast te houden.
Actually, it's not only legal in California, the state recently banned devices that get stuck to the windshield and mandates that such devices need to be placed and secured on the dashboard.
Obviously, the law doesn't say anything about HUDs, and it will probably take a few years for legislation to catch up with technology in that area.
Those stats determine where most of the resources have been focused on. Each coins have their own agenda, goal, and different group of community backing it.
i think its a bit different b/c ethereum is supposedly useful as the 'fuel that allows apps to utilize the concept of a blockchain' in apps.
i suppose the idea is that it 'burns' ethereum to run an app on top of it, so I can see a scenario where ethereum becomes too expensive and businesses that use decide to move to a different fork that is less expensive.
I guess the oil analogy works then -- it gets too expensive and alternatives are found. However, its just a matter of forking the codebase and starting another one...kind of like stellar did with ripple.
Many clones were made of bitcoin, but it has a large first mover advantage which keeps it on top. coinmarketcap.com has some interesting stats on the "altcoins"
The solution to this kind of problems is: Make Read-only "disaster recovery" backups - zip it and burn it to a DVD set or Bluray, and put it off-site. Make incrementals or differentials of those discs every few months and a full data set each 3 months.
Takes a few hours, I like to burn all my data to Bluray (50GB per disk) while watching a movie.
Store the bluray data sets at a friend's house and never worry again.
Really? If the pool only has 51% of the mining power but gets 100% of the block rewards, pool members would get coins at double the normal rate. I don't see a lot of people leaving in that event.
Is the exploit only for when running services on/to the internet (IIS, Exchange webmail, etc - ) , or is visiting an https (TLS) website on and end-user enough to make the exploit happen (even in Firefox/Chrome and behind a tradional proxy server).
Sadly Microsoft does not explain the exact parameters that make this exploit tick - this makes risk assessment hard.