San Francisco Allows The Use Of Lethal Robots By Police
On Tuesday, November 29, the Board of Supervisors in San Francisco voted to allow the use of lethal robots by police. The vote was 8-3 in favor of granting police the use of military equipment and lethal robots in an emergency situation. SFPD spokesperson Allison Maxie said robots will be used:
to contact, incapacitate, or disorient violent, armed, or dangerous suspect. Robots equipped in this manner would only be used in extreme circumstances to save or prevent further loss of innocent lives.
**** ****** ** *********** ***** ********* the *** ** *********** ***** ** *** **** ****** shooting.
**** ********** ************ **** **** ****,*** ***** ********** ******, *** ****** ***** ******* ******* "***** ******* cheap *****". ** ******** ** ***** ********** robots, ** *** **** ****** ********, a ******-********** ***** *** ****** **** C4 *** *** ******** ********* **** the *******.
** *** ******* ****** *********** ***** weaponized ******?
Login to read this IPVM discussion.
| 12/01/22 02:02pm
***** *** **** "******" **** **** "remote ******* ****", **'* *** ***** in *******.
***** *** **** "******" **** **** "remote ******* ****"
**** ** ** ********* ********* **** sometimes **** **** ** *** ************ slant:
***** *** *** ********** ****** ******...
*******, **** *** ******* ********** **** isused ** * ***** ********** to deliver the shot that they can't deliver safely with traditional LE weapons.
** ** ****, ***** ** ** clarifying ******** ****-******* ****** “*****-**********”. *** **** ** “military *********” **:
********, ******** *******, ******* ****** ** ground ********.
******** ******* *** **** ***** ********** but **** *** **** ***** **********, where *** “*****” ********* ***** ** perform * ****, *** ***** ************ identifies *** **** *** ******* *** target. *** ****** ******** ** *** much **** *** ******, ** ***** are ****** ********* **** *** ** automatically ******** ** ***** *********.
* ***** *** **** ****** ***** support * ***** **** ** ** be *** *****, ****, *** *** executioner. **** ****** ******* * ********** language ** ******* “***** ********.”
******** ******* *** **** ***** ********** but **** *** **** ***** **********, where *** “*****” ********* ***** ** perform * ****, *** ***** ************ identifies *** **** *** ******* *** target.
'*** *** **** ****' *** ** true - *** ******** ** ** select *** ****** **** ****** ********* never ** ******* ** ** ******** into *** - ******* ** *** sane ****** *** *******.
** ***** * ******* **** *** linked ** **-*** ** ************* *** the *** ** '******** *********' ** local/state ** - *** ****'* *** the ****. *** ******* ** **-*** are ** **** ** *****/***** *********** using ******** ******* **********.
*** ******* ** *.
**-*** ***** ** ****** ********* ******** on *** *** ** ******** ******* by *****/***** ** - *** * am * *** ** **** * thing.
** ******** ** ******** ***** ** the ******* ** ***** ************.
** *** ***** **, ***** *** outfit ******** **** * *******, *** are ******** ** ******* **** * soldier - ******* ** * *****/***** police ******* ********** *** ******* **** community ************.
*** *** ******** * **** ****** would ** ** ******. ** ***** is ** **** **** **** ** act *** ** ** ***** *** a ***** ***** ** ***** *********** explaining *** **** ******* *** * glitch *** *** ********** ** *****. Followed ** * **** ** ********.
| 12/02/22 02:26pm
******** ******* *** **** ***** ********** but **** *** **** ***** **********, where *** “*****” ********* ***** ** perform * ****, *** ***** ************ identifies *** **** *** ******* *** target.
***, ** *****, *** ***** *** no ********** **** ****** ** ***** applications, ** ** ****** **. **** the ******** ****** ******* *** ************* a ***** ******-*********** *** *****, **** might *** **** ** *** ******** for ******* ********** ** ****** *********, but **'* *** **** ****'** ******* a ***** *** **** ** *** Guy *** ****** ** ************ "** kill, *******".
**** ******, *** ********* ****** ** 'killer ****** ******'
*** ********* *********** ***** ******* ** put *** ****** ** * ************* policy **** ***** **** *** ****** use ****** *** ****** *****, ********* course **** **** ***** ***** ******** of *** **** ********* ****** ******** and ******** ***** *** ************** *** automation ** ********.
*** ***** ** *********** ***** *********** to ********** *** *** *** ** robots ** **** * ******* *** now. *** **** **** *** ***** back ** * ********* *** ******* discussion *** ***** **** ** *** future ** *** ****** *** ****** in * ****** ****** ** ******* cases.
Newest Discussions
| Discussion | Posts | Latest |
|---|---|---|
|
Started by
John Honovich
|
9
|
less than a minute by John Honovich |
|
Started by
John Honovich
|
14
|
3 minutes by Corey Keast |
|
Started by
Sean Patton
|
13
|
less than a minute by Michael Silva |
|
Started by
Donald Maye
|
5
|
less than a minute by John Honovich |
|
Started by
Ethan Ace
|
6
|
less than a minute by Undisclosed Manufacturer #1 |
* ***** ******* ** *** **** if * ***** *** ** *******. The ******** ** *** ****** ***** should *** ** **** ** **.