It's theoretically possible for a falling drone to kill someone, but I would not classify it as easy.
Odds are probably higher for an accidentally shooting. Or for the drone pilot to chase his falling craft and get run over by not looking both ways before crossing the street.
Many of the ordinances that restrict drone(UAS) are to do with safety. It's not safe to fly them over highways for example. It's not safe to fly them over a redneck farmer's property. Lots of places you shouldn't be flying them.
The examples you are giving are people flying in public areas....ie, open to use BY the public.
technically it's not permissible to fly drones in a public space without permission from the entity that controls that space (city, county, or state)
That should cause you no harm since it isn't over your private land, but you seem to be arguing that it is...?
The other example is flying over private land, see the part where I talk about people flying 10+ miles out. That's all hills and meadows, some of it part of the county's Open Spaces preserve, some of it private land. Many of the open spaces are under fire advisory so drones are often prohibited at those times, even when they aren't it's not a smart thing to do. As your drone setting off a wildfire makes you liable for civil penalties, and the AMA isn't going to step in and save your butt.
What's wrong with flying at a public beach?
It's legal at some beaches and not others. You must check the beach posting to determine if drones are allowed and at what times. In my earlier example it is not permitted without special permission for public safety reasons at a very crowded beach. But if you really want more detail there is a nice summary from the California Department of Parks and Recreation
Happens a lot at the beach. But I'm not allowed to bring guns on the public beach. Also it might be upsetting if people were shooting in the air all the time, but it's Santa Cruz so a lot of weird shit goes down and nobody seems to care.
Where I live, people usually fly drones on their property, or with permission above others.
In urban areas people don't have acres of property. So they fly in parks and at beaches.
They normally don't want to pay hundreds-thousdands of dollars for a Drone, to have it just kinda fly all over the place just to create chaos.
We've reprimanded multiple members in our club for doing just this. They like to fly around illegally with FPV and make YouTube videos of their illegal flights. One guy had footage flying 10+ miles away while he sat in a lawn chair wearing his goggles. Made possible because he got some high powered VHF transmitter and a HAM license. He was legal for the FCC, but not following AMA guidelines or FAA regs.
I guess don't trespass on my property. You can use the airspace 80 ft above my property all you like, as long as you stay in accordance to FAA rules. And ideally you should have joined the AMA and paying your dues towards liability coverage.
A few years ago my RC club had a plane's battery catch fire in a dry field, and luckily we were nearby to extinguish it. But if you're outside of a reasonable range because you're flying FPV illegally, I'm going to take your toy out of commission. I'll politely return the pieces to you. You can try taking me to court for the damages, but I'm confident it won't go well for you.
I wonder if I could get the same ruling in California too, as long as I don't shoot some film studio's drone. The courts are overly protective of Hollywood.
PS - yes, you can own firearms in California. it's not a big deal if you're away from the big coastal cities. You used to be able to open carry here in unincorporated areas until recently
I really dislike Trump. And I am highly critical of his administration. But some people are really hung up on this emergency alert system like it's some kind of huge invasion. You put up with 80% of your mailbox being full of ads, but you get one unblockable test message for an emergency service and you lose your shit?
Maybe you should focus on the real wrongs Trump has done, and not the inane distractions he creates for you. I hope the liberals win back the government, but goddamn they can get stuck on stupid sometimes.
Luckily for Roman soldiers the whole paying in salt thing was very likely a back-formation invented by Pliny from assumptions on the meaning of the word salaries. And the section of his book where he mentioned this was more about facts relating to salt than about soldiers or economics. In Pliny's time soldiers were paid in coin, and have been since around 100-150 years before Pliny's time (Marian reforms).
Pluto is the ninth, and like everything else that revolves around thr sun, planet.
How about we say Pluto is the largest dwarf planet and fifth dwarf planet from the Sun ?
ordered by distance from Sun: 1. Ceres (945 km diameter, 2.9773 AU aphelion) 2. 120347 Salacia (approximately 850 km diameter, 46.548 AU aphelion) 3. 2002 MS4 (726 km diameter, 47.740 AU aphelion) 4. 90482 Orcus (920 km diameter, 48.069 AU aphelion) 5. Pluto (2380 km diameter, 49 AU aphelion) 6. Haumea (816 km diameter, 51.483 AU aphelion) 7. Makemake (715 km diameter, 52.840 AU aphelion) 8. Eris (1160 km diameter, 97.651 AU aphelion) 9. 2007 OR10 (1253 km diameter, 101.02 AU aphelion) 10. 90377 Sedna (approximately 1000 km diameter, 936 AU aphelion)
And I got promoted. And I got to automate more stuff. But being a project lead and pseudo-manager was boring so I quit. (pseudo-manager: I had 2 reports, but I split their review process with my boss)
If you RTFM for/. you can do all the fancy stuff: ‘ ' ’ “ " ”
I think Apple assumes a particular encoding for the HTML forms. Perhaps/. could hint better on the HTML side or perhaps during HTTP POST. But if the encoding isn't known it's not correct for the browser to assume UTF-8 encoding.
Ideally/. should just fix it, and report 8859-1 everywhere. I think that should convince the browsers to re-encode correctly without needing to change much on the server side.
You may wish to read the article more carefully, or go straight to the Sandvine blog. From a engineering perspective it's certainly interesting. But in terms of assigning blame as the tone of a Variety article it's a pretty useless factoid.
If any of you sat in a tech support call center for one day you'd realize that few end users are reading and understanding the manuals we've been providing.
The most effective method is to include a small bit of colorful card stock in the top of the stack of packaging with something like "Quick Start" in a big font. Some users will see this when first opening a product and if you're really lucky they will try to follow directions the pictures and very short sentences. If all else fails a phone number and website is on the back of the card for a proper hand-holding experience.
PDF downloads on the company website of a very comprehensive manual is especially nice. As I can search it, or access it from my phone instead of having to remember where I hid the physical copy.
lead-acid is good if you don't care about the weight of your batteries and may want them to perform well in cold conditions. It's storage I'm intending to use for my power system project for a small remote out building.
A lithium iron phosphate battery can handle around 2000 charge cycles, which is significantly more than a typical usage for a lead-acid. But the price of LiFePO is much higher than lead-acid per amp-hour. A lithium-ion polymer battery on the other hand doesn't have the same longevity of a LiFePO but it is significantly cheaper per amp-hour than a sealed lead-acid.
Right now lead-acid has a very good infrastructure for disposal and recycle. Theoretically we could get some of the lithium based technologies up to a similar level of environmental conformance and convenience, but it's currently not there yet.
You pay for additional registers with increased context switch latency. It's not really a slam dunk. Some architectures only make you pay on a context switch for registers you used, but if you're not using them then you probably didn't need them, so assumed an efficient program uses all the registers.
Having lots of registers and good swizzle operations can help SIMD (single instruction, multiple dispatch). But that doesn't come out of the general purpose register set on most architectures.
Your CPU architecture isn't the biggest factor when it comes to general purpose computing. A bad one will hinder you, but there are several good enough ones. Having fewer state changes can improve your thermodynamic efficiency (so less bits, less registers, narrower "way" cache), but other factors like manufacturing technology tend to matter more. Use case matters the most by far.
Apple's hardware team is able to leverage testing and validation for a single CPU architecture is a savings for them (I'm on a SW validation team for an SoC vendor, so I have some idea of the amount of work involved). Apple's volumes as a chip producer are perhaps low enough for this to matter significantly. I highly suspect this choice makes as much sense for bean counters than it does for technical reasons.
Yeah, having to use two CPU registers to hold my file offsets was a real chore. It was impossible for 20 year old Unix systems to add system calls to with names like lseek64(). We can only write software that is as simple as possible, and we would never include even slightly complicated interfaces to do something as basic as accessing large files.
Also 32-bit systems never offer 64-bit values for time stamps, so those will all explode in the year 2038. You don't want your obsolete 32-bit watch to EXPLODE do you?
(actual upsides are related to the industry providing security updates and enhancements to newer architectures)
Slashdot Mirror
It's theoretically possible for a falling drone to kill someone, but I would not classify it as easy.
Odds are probably higher for an accidentally shooting. Or for the drone pilot to chase his falling craft and get run over by not looking both ways before crossing the street.
Many of the ordinances that restrict drone(UAS) are to do with safety. It's not safe to fly them over highways for example. It's not safe to fly them over a redneck farmer's property. Lots of places you shouldn't be flying them.
Doesn't mean a broken clock isn't right twice a day.
The examples you are giving are people flying in public areas....ie, open to use BY the public.
technically it's not permissible to fly drones in a public space without permission from the entity that controls that space (city, county, or state)
That should cause you no harm since it isn't over your private land, but you seem to be arguing that it is...?
The other example is flying over private land, see the part where I talk about people flying 10+ miles out. That's all hills and meadows, some of it part of the county's Open Spaces preserve, some of it private land. Many of the open spaces are under fire advisory so drones are often prohibited at those times, even when they aren't it's not a smart thing to do. As your drone setting off a wildfire makes you liable for civil penalties, and the AMA isn't going to step in and save your butt.
What's wrong with flying at a public beach?
It's legal at some beaches and not others. You must check the beach posting to determine if drones are allowed and at what times. In my earlier example it is not permitted without special permission for public safety reasons at a very crowded beach. But if you really want more detail there is a nice summary from the California Department of Parks and Recreation
Double blind studies don't work like this.
Blindfold both grandparents.
Is this a common problem in your community?
Happens a lot at the beach. But I'm not allowed to bring guns on the public beach. Also it might be upsetting if people were shooting in the air all the time, but it's Santa Cruz so a lot of weird shit goes down and nobody seems to care.
Where I live, people usually fly drones on their property, or with permission above others.
In urban areas people don't have acres of property. So they fly in parks and at beaches.
They normally don't want to pay hundreds-thousdands of dollars for a Drone, to have it just kinda fly all over the place just to create chaos.
We've reprimanded multiple members in our club for doing just this. They like to fly around illegally with FPV and make YouTube videos of their illegal flights. One guy had footage flying 10+ miles away while he sat in a lawn chair wearing his goggles. Made possible because he got some high powered VHF transmitter and a HAM license. He was legal for the FCC, but not following AMA guidelines or FAA regs.
I guess don't trespass on my property. You can use the airspace 80 ft above my property all you like, as long as you stay in accordance to FAA rules. And ideally you should have joined the AMA and paying your dues towards liability coverage.
A few years ago my RC club had a plane's battery catch fire in a dry field, and luckily we were nearby to extinguish it. But if you're outside of a reasonable range because you're flying FPV illegally, I'm going to take your toy out of commission. I'll politely return the pieces to you. You can try taking me to court for the damages, but I'm confident it won't go well for you.
Yeeehawww!
I wonder if I could get the same ruling in California too, as long as I don't shoot some film studio's drone. The courts are overly protective of Hollywood.
PS - yes, you can own firearms in California. it's not a big deal if you're away from the big coastal cities. You used to be able to open carry here in unincorporated areas until recently
I'd like to see more drones taken down. I'd also like a new federal program for private citizens to apply for a drone hunting permit.
I really dislike Trump. And I am highly critical of his administration. But some people are really hung up on this emergency alert system like it's some kind of huge invasion. You put up with 80% of your mailbox being full of ads, but you get one unblockable test message for an emergency service and you lose your shit?
Maybe you should focus on the real wrongs Trump has done, and not the inane distractions he creates for you. I hope the liberals win back the government, but goddamn they can get stuck on stupid sometimes.
If any of my friends are reading this, if you're a murderer I'm not your friend either.
Luckily for Roman soldiers the whole paying in salt thing was very likely a back-formation invented by Pliny from assumptions on the meaning of the word salaries. And the section of his book where he mentioned this was more about facts relating to salt than about soldiers or economics. In Pliny's time soldiers were paid in coin, and have been since around 100-150 years before Pliny's time (Marian reforms).
Your employer is literally paying you peanuts.
May 2018 price for Groundnuts (peanuts) is $1,420/metric ton. 35 metric tons of nuts is fucking nuts.
How would an employer even ship and store that many nuts for their employees. It would be the literally worst business decision.
Pluto is the ninth, and like everything else that revolves around thr sun, planet.
How about we say Pluto is the largest dwarf planet and fifth dwarf planet from the Sun ?
ordered by distance from Sun:
1. Ceres (945 km diameter, 2.9773 AU aphelion)
2. 120347 Salacia (approximately 850 km diameter, 46.548 AU aphelion)
3. 2002 MS4 (726 km diameter, 47.740 AU aphelion)
4. 90482 Orcus (920 km diameter, 48.069 AU aphelion)
5. Pluto (2380 km diameter, 49 AU aphelion)
6. Haumea (816 km diameter, 51.483 AU aphelion)
7. Makemake (715 km diameter, 52.840 AU aphelion)
8. Eris (1160 km diameter, 97.651 AU aphelion)
9. 2007 OR10 (1253 km diameter, 101.02 AU aphelion)
10. 90377 Sedna (approximately 1000 km diameter, 936 AU aphelion)
And I got promoted. And I got to automate more stuff. But being a project lead and pseudo-manager was boring so I quit. (pseudo-manager: I had 2 reports, but I split their review process with my boss)
If you RTFM for /. you can do all the fancy stuff: ‘ ' ’ “ " ”
I think Apple assumes a particular encoding for the HTML forms. Perhaps /. could hint better on the HTML side or perhaps during HTTP POST. But if the encoding isn't known it's not correct for the browser to assume UTF-8 encoding.
Ideally /. should just fix it, and report 8859-1 everywhere. I think that should convince the browsers to re-encode correctly without needing to change much on the server side.
You may wish to read the article more carefully, or go straight to the Sandvine blog. From a engineering perspective it's certainly interesting. But in terms of assigning blame as the tone of a Variety article it's a pretty useless factoid.
Nope, I've run out of them.
If any of you sat in a tech support call center for one day you'd realize that few end users are reading and understanding the manuals we've been providing.
The most effective method is to include a small bit of colorful card stock in the top of the stack of packaging with something like "Quick Start" in a big font. Some users will see this when first opening a product and if you're really lucky they will try to follow directions the pictures and very short sentences. If all else fails a phone number and website is on the back of the card for a proper hand-holding experience.
PDF downloads on the company website of a very comprehensive manual is especially nice. As I can search it, or access it from my phone instead of having to remember where I hid the physical copy.
lead-acid is good if you don't care about the weight of your batteries and may want them to perform well in cold conditions. It's storage I'm intending to use for my power system project for a small remote out building.
A lithium iron phosphate battery can handle around 2000 charge cycles, which is significantly more than a typical usage for a lead-acid. But the price of LiFePO is much higher than lead-acid per amp-hour. A lithium-ion polymer battery on the other hand doesn't have the same longevity of a LiFePO but it is significantly cheaper per amp-hour than a sealed lead-acid.
Right now lead-acid has a very good infrastructure for disposal and recycle. Theoretically we could get some of the lithium based technologies up to a similar level of environmental conformance and convenience, but it's currently not there yet.
If more websites went offline once in a while.
In space no one can hear you say "pew! pew! pew!"
Self driving cars work today. But they aren't necessarily less likely to drive off a pier than your average senior driver.
Bandwidth is supposed to be used by people. That's the point of having it.
If one service takes a significant portion of the pie, then our infrastructure is at fault.
You pay for additional registers with increased context switch latency. It's not really a slam dunk. Some architectures only make you pay on a context switch for registers you used, but if you're not using them then you probably didn't need them, so assumed an efficient program uses all the registers.
Having lots of registers and good swizzle operations can help SIMD (single instruction, multiple dispatch). But that doesn't come out of the general purpose register set on most architectures.
Your CPU architecture isn't the biggest factor when it comes to general purpose computing. A bad one will hinder you, but there are several good enough ones. Having fewer state changes can improve your thermodynamic efficiency (so less bits, less registers, narrower "way" cache), but other factors like manufacturing technology tend to matter more. Use case matters the most by far.
Apple's hardware team is able to leverage testing and validation for a single CPU architecture is a savings for them (I'm on a SW validation team for an SoC vendor, so I have some idea of the amount of work involved). Apple's volumes as a chip producer are perhaps low enough for this to matter significantly. I highly suspect this choice makes as much sense for bean counters than it does for technical reasons.
Yeah, having to use two CPU registers to hold my file offsets was a real chore. It was impossible for 20 year old Unix systems to add system calls to with names like lseek64(). We can only write software that is as simple as possible, and we would never include even slightly complicated interfaces to do something as basic as accessing large files.
Also 32-bit systems never offer 64-bit values for time stamps, so those will all explode in the year 2038. You don't want your obsolete 32-bit watch to EXPLODE do you?
(actual upsides are related to the industry providing security updates and enhancements to newer architectures)