Your understanding of US v Causby is inverted. Public airspace does not begin until 500 above obstacles.
Case in point, airports must compensate land-owners for approaches below 500 feet since such traversal violates the land-owners airspace and "enjoyment of the land".
Facebook doesn't have a search engine nor the defacto video sharing platform. But yes, Facebook is after the same things; Google had them already and was arbitrarily mesh-mashing them together -- very unsettling to the user.
Facebook is still a slow cooker, so the frogs don't notice.
That last bit contradicts the first bits.
Clearly the last scenario was free market "work for hire", not all things in common. So which is it?
Biggest detraction was the unknown of how much of your browsing and searches and youtube video history would end up on your public profile.
I have a drone -- I don't know if his version works different, but the telemetry is relative to the drone's take-off. The drone does not have topographical data to determine actual altitude from ground obstacles!
Someone correct me if I'm wrong -- but all my tests with my drone flying over changes in terrain (say a hill a hundred feet high) changes the telemetry altitude by zero -- it's all relative to the home point.
Regardless the guy was a pretty good shot to take it down if they were just doing a fly-over, albeit since the drone was loitering first, he probably had a good slow start to work with.
IMO the land owner owns that airspace and the drone operator was flying over land he did not have permission to cross. If he was flying at 400 feet it would be debatable. Anything less, the drone-op is trespassing. Aside from the city ordinance against discharging firearms, the land owner should have every right to down the invasive craft.
This reversal of arrest here is just to set precedence so Amazon can trespass into everyone's property without paying for air right-of-way.
You must a lawyer or a legislator.
I imagine you could pass a law that says the State owns all the airspace from ankle height and give the police jurisdiction over drones, beach-balls, and soap bubbles. But then I don't need to imagine that since Oregon was trying to do just that. (Notice the use of a military drone in the article, when the legislation is actually trying to get the citizens to cede their rights to their own airspace.
So unless you have a political incentive to create and pass new legislation (to look busy), or you're feeling pressure from Amazon's lobby so they can fly shipping lanes into private citizens airspace without their permission, I'd say there's no reason for another law in this case.
Is it legal to climb your roof, and point a loaded handgun at your neighbour's head?
If you did this to a police officer he would probably shoot you. And I'm no legal expert but even your neighbor may be legally allowed to shoot you in this case.
You've described someone threatening assault with a deadly weapon. There are just a few laws dealing with that...
Unless Apple addresses this -- all Macs are wide open regardless.
But testing as "guest" or "nobody" would leave the system open without having to append the sudoers file first -- so agree: clean up after testing.
MacBook Pro -- integrated keyboard.
Happened twice: once after sitting idle for a few minutes with a web page open (did not enter sleep mode), the other on boot at the login screen.
The fact it happened on boot is what made me dismiss it as a possible update issue.
No ports being forwarded, but after seeing this anything that exposes a unix account and allows any environmental variable to be set (even one for the app's own private shell) would be able to core this apple. Redirecting a shell to a remote IP is trivial
Just don't know if that would take keyboard away from an active user...
Local application access!
You just have to be able to set an environment variable no matter who you are and you're root. It's just a question if FireFox has its own "environment" or relies on an under-privileged UNIX account.
From what I can tell, this is a wide-open window. Huge, huge, flaw.
Lost control of my keyboard twice this week.
Discovered the Mac's firewall was down. But couldn't find any history on the keyboard getting redirected to remote address.
I was ready to chalk it up to a bad driver update by Apple, but I should probably assume I've been rooted.
The opossum is a very sophisticated animal. It doesn't even get up until 5 or 6 PM.