I hope the operator of the drone is charged and convicted, trespass and peeking tom laws seem to fit. Hell if that underage girl was topless get them for kiddie porn.
That aside, just don't screw with things. You mention caps lock, which I don't use, but any change is likely to just screw with muscle memory and not have any practical benefit except as some symbolic gesture against caps lock. For example, see second gen X1 carbon which replaced caps lock with home and end keys.
There is also the troubling by the way mention of the right mouse button. For the love of god do not advocate screwing with the right mouse button. You don't often need it, but when you do, all the schemes that try to de-emphasize it's footprint really screw with you and again *nothing of value is gained*.
The problem being they didn't do the same to ARM. Either that argument applies to both sides or neither. They need to be held to same standard.
The more troubling question is why an application should feel forced to do anything in the face of a platform upgrade in order to work at all. A modern Windows desktop can still run 10 year old software without a hiccup. Going back 20 years you start needing something like dosbox to use a lot of the applications, though still doable. I haven't tried firing it up in a while, but last time I tried the commercial package of quake 3 under linux, it still worked on a modern distribution. Same for linux neverwinter nights. As an application maintainer for some linux stuff, the only things that I can recall forcing my hand to change something for things to work were systemd and python changes.
Android (and to a significant, but somewhat lesser extent Apple) are not doing that good with respect to application and/or hardware compatibility into the past. It's a tiring situation for developers to have to follow an upgrade treadmill in order to cater to new system sales, just to keep the current applications workable as-is.
M.2 is the desktop interface for this, it supports 4 PCI 3.0 lanes at 985 MB/s per lane that is nearly 4GB/s. PCI 4.0 is not to far off and doubles that.
Still want a VoIP desk phone with a Qi charger, bluetooth cellphone and headset connectivity. Something where I could charge my phone, use the better handset/speakerphone of my VoIP phone and a bluetooth headset. A perfect world would also allow multiple phone ringing for inbound calls, some contact sync, and possibly calendar/task sync as well.
It is Qi so most will work it's pretty much the winner. It's only 1080P (ish since it uses AMD's sync protocol). It's a PLS panel so none of the IPS goodness.
Pretty much is a fairly meh monitor with a qi charging puck shoved into the base they are literally a few bucks added to the BOM.
Plenty of people have modded bases, keyboard, desks etc etc etc to add qi charging this is just a cheap gimmick to try and make a meh monitor look cool.
Because subsidies turn 10k of PV into 30k, much like when the 7k fed tax credit for hybrids went away the price went down 7k.
Because making PV is a rather nasty business, it pretty much just ships the pollution portion of power generation elsewhere.
The restriction was prior restraint of a particular speaker. Insuring you have adequate security, cleanup insurance etc is fine.
Oh I would say the event people intended to have the cops stop it for the PR value rather than going to the courts in the first place.
Why should the state be allowed to put such restrictions on permits??? If the fugitive showed up they should arrest him possibly some of the event team for aiding and abetting (though that is a broken law). This is the state restricting speech on public property.
Exploits that were watermarked to the client that your sold them to.
These are not tools that should ever be in police hands. Requiring that outside firms do this sort of thing and thus need to keep the paper trail of warrants that allowed each and every event. Require that they be audited and a special prosecutor look into any apparent/potential breaches of law and prosecute them to the full extent (no plea deals). Require that all security vulnerabilities be disclosed to the public in 30-90 days. Tighten up these warrants in the first place and full public disclosure of the same after a reasonable investigatory period say 90 days.
The NSA etc should have these tools and a very big firewall between them and law enforcement.
The Secret Service categorizes all threats, online and offline alike, into one of three categories. Class 3 threats are considered the most serious, and require agents to interview the individual who issued the threat and any acquaintances to determine whether that person really has the capability to carry out the threat. Class 2 threats are considered to be serious but issued by people incapable of actually follow up on their intentions, either because they are in jail or located at a great distance from the president. And Class 1 threats are those that may seem serious at first, but are determined not to be. The overall number of threats directed at the first family that require investigation has stayed relatively steady at about 10 per day — except for the period when Obama was first elected, when the Secret Service had to follow up on roughly 50 threats per day. "That includes threats on Twitter," says Ronald Kessler, author of In the President's Secret Service. "It makes no difference to [the Secret Service] how a threat is communicated. They can't take that chance of assuming that because it's on Twitter it's less serious."
Oh we know how, it requires time and thought.
Now the ECM should be able to send things to the BCM and Infotainment gear. The reverse should be very limited, pretty much remote start and that should be thoroughly checked for sanity. Old school would be serial in one direction yea there are some hardware hacks but not that problematic.