Alexa put the life of a 10-year-old in danger, gave a deadly challenge to the girl, know what is the whole matter?

 
tech

Amazon Alexa: Virtual voice assistant Alexa is being used for some time now and there is a lot of craze among people. In Alexa, you get many small and big information from setting an alarm. (Voice Assistant Device) That's why this smart speaker is also called. But sometimes using technology can be overwhelming and in such a situation, Alexa can become an enemy instead of being your friend. Recently a similar case related to Alexa has come to the fore. In which Alexa gave such a dangerous challenge to a 10-year-old girl, due to which she could have lost her life. (Voice Command) Let us know what is this whole matter?

TECH

Dangerous challenge was given to the girl
Kristin Livdahl, a Twitter user from America, told about the challenge given by Alexa to the girl through a post. His 10-year-old daughter's school teacher had asked him to do some physical challenges at home. But due to rain outside, the girl's mother asked her to challenge her by staying at home. After which the girl took the help of Alexa and asked Alexa if she can take any challenge by staying inside the house?

In response, Alexa told the girl that it is very easy. Alexa asked the girl to plug the phone's charger about halfway into the power outlet. Then the two ends of it which are left out, have to be touched by putting a coin in the middle. Touching the plugin this way will not only incur current but can also kill someone. Let us tell you that this is a Penny Challenge challenge that became quite viral on social media last year.

Alexa

Girl's life saved
The girl's father told her that his daughter is very intelligent and that's why she did not put a coin in the current plug at the behest of Alexa. Otherwise, a big accident could have happened. The child's father says that if the parents are not with them, then technology can become a big threat to the children. However, when Amazon was asked about this, Amazon replied that it was due to a bug in Alexa and it was fixed as soon as possible.

From around the web