BEIRUT/JERUSALEM July 3 (Reuters) - An Israeli strike killed one of Hezbollah's top commanders in south Lebanon on Wednesday, prompting retaliatory rocket fire by the Iran-backed group into Israel as their dangerously poised conflict rumbled on. The Israeli military said it had struck and eliminated Hezbollah's Mohammed Nasser, calling him commander of a unit responsible for firing from southwestern Lebanon at Israel. Nasser, killed by an airstrike near the city of Tyre in southern Lebanon, was the one of the most senior Hezbollah commanders to die yet in the conflict, two security sources in Lebanon said. Sparked by the Gaza war, the hostilities have raised concerns about a wider and ruinous conflict between the heavily armed adversaries, prompting U.S. diplomatic efforts aimed at deescalation. Israeli Defence Minister Yoav Gallant said Israeli forces were hitting Hezbollah "very hard every day" and will be ready to take any action necessary against the group, though the preference is to reach a negotiated arrangement. Hezbollah began firing at Israeli targets at the border after its Palestinian ally Hamas launched the Oct. 7 attack on Israel, declaring support for the Palestinians and saying it would cease fire when Israel stops its Gaza offensive. Hezbollah announced at least two attacks in response to what it called "the assassination", saying it launched 100 Katyusha rockets at an Israeli military base and its Iranian-made Falaq missiles at another base in the town of Kiryat Shmona near the Israeli-Lebanese border. Israel's Channel 12 broadcaster reported that dozens of rockets were fired into northern Israel from Lebanon. There were no reports of casualties. The Israeli Defence Ministry said that air raid sirens sounded in several parts of northern Israel. Israel's military did not give a number of rockets launched but said most of them fell in open areas, some were intercepted, while a number of launches fell in the area of Kiryat Shmona.

Google Wallet can help you store your IDs, driving license, loyalty cards, concert tickets and more. You can also store your payment cards and use tap to pay to pay anywhere Google Pay is accepted. Google wallet is available in various countries but Google never launched it in India. Google let indian users stick with the Gpay which facilitates UPI payments. Tap to pay is not part of it. Also we can not store things such as IDs and Passes in indian version of Gpay. This might change and Google may launch Google Wallet in India. With the recent version of Google Wallet and Google Play Services, Google has added some flags and code which indicate that Google is working on something for Indian users regarding wallet. The first change I noticed recently when going through the Google Play Services apk was addition of two new flags Both flags are part of com.google.android.gms.pay package in the Google Play Services. This package contains all the flags for features of Gpay/Wallet. Google does server side flipping of flags to enable/disable features for users. So both these flags doesn't really provide any info about what features enabling these flags is going to bring. But the point here is that Google Wallet is not launched in India so why Google added these flags inside Play Services ? The answer could be that Google may be working on bringing Google Wallet to India. It can enable tap to pay, store payments and various other features for Indian users which we don't have in the current Gpay for India. I found similar flags in the analysis Google Wallet APK - These flags are also disabled by default. But this is again a clear indication of Google working towards something for Indian users. In both cases, enabling the flags doesn't bring anything noticeable UI or feature because there is nothing much added besides flags. Google has dogfood/testing versions internally, so the code will show up slowly in upcoming versions. The last piece of code I found is also from Google Play Services. In case you don't know, Google was working on Digilocker integration in the Google Files app which was supposed to bring your digital document inside the app such as driving license, COVID certificates, aadhar card. But Google has ditched the effort of bringing these features and they removed the "Important" tab (where digilocker was supposed to be integrated) from the Google Files app completely. So things are going to change and here is how. This is the code which I found in the Google Play Services - So the word "PASS" along with PAN, DRIVERS LICENCE, VACC CERTIFICATE & AADHAR CARD, is clear indication of the possibility of Google adding support for these directly through Google Wallet using Digilocker, just like Samsung Pass does it. This code is not old as I have checked older beta versions of Play Services where this code is not present. Here is a string which was added in a previous beta version a few weeks ago but I completely ignored it because it didn't make any sense without flags and the other code - This addition was surprising because there was nothing regarding digilocker before in the Play Services. In the words "pay_valuable", the "pay" to Wallet/Gpay and "valuable" refers to the things like Passes, loyalty cards and transit cards. Since we are talking about digilocker, these "valuable" are driving license, vaccination certificate, PAN card and Aadhar card which can be store in Google Wallet after digilocker integration. That's all about it. We will know more about it in upcoming app updates or maybe Google can itself annouce something about this.

WhatsApp beta version 2.24.14.20 has a new feature that allows users to share photos with Meta AI. The AI chatbot will analyze uploaded images and provide information or context about the content. Users may be able to request specific edits to their photos directly through Meta AI, though the extent of this feature is still unknown. As the battle for AI dominance heats up, Meta is adding a new trick to its AI chatbot, Meta AI, which is already part of Facebook, Instagram, and WhatsApp. While Meta AI already has impressive text capabilities, such as replying to questions, suggesting captions, and holding conversations, users cannot currently share or upload photos to the Meta AI chat. WaBetaInfo has uncovered the exciting new feature in the WhatsApp beta for Android version 2.24.14.20. This feature will allow Meta AI to interact with photos shared by users, reply to photos, and even edit them. As shown in the attached screenshot, WhatsApp is testing a new camera button in the Meta AI chat, designed to function similarly to the camera button in regular chats. This addition will allow users to manually share photos with Meta AI, a capability that is currently unavailable. With this new functionality, users will be able to ask questions about their photos, presumably allowing users to ask the AI to identify objects or locations or provide context about the photo’s content. Moreover, the screenshot suggests that Meta AI will also offer the option to edit photos, enabling users to make changes to their images directly within the chat by sharing a prompt. The exact scope of this image editing feature remains unclear, leaving us to wonder if it will be limited to simple tweaks or if it will unleash a powerful AI-driven photo editing suite. The possibilities are both exciting and intriguing, and this feature could definitely be a big hit, especially if it performs as promised. While this new image-sharing feature would mean Meta will analyze and face-scan the photos you upload, the screenshot includes a disclaimer indicating that users will have the option to delete their photos whenever they want. As of now, it seems that the feature is still in development, so it might be some time before we finally get to see it roll out publicly. Recently, we also reported about WhatsApp working on an “Imagine Me” feature that would allow Meta AI to generate AI avatars of you based on a set of your photos. WhatsApp in our newsletters WhatsApp is a leading messaging app, keep up to date on the latest, and learn about more Android apps today!

A Portadown man has avoided jail after sexually assaulting a 16-year-old shop worker under his employment. -ADVERTISEMENT- Brian Thomas Chapman (58), of Moyallan Road, appeared before Newry Magistrates’ Court on Monday for sentencing on two counts of sexual assault. The prosecution outlined that on September 23, 2020, a 16-year-old student in the employment of Brian Chapman, disclosed to her mother about incidents that had occurred in her workplace. She said Chapman had put his hand on her thigh and the back of her leg. She also disclosed that she had been getting extra money from him and he had been sending her text messages. The allegations were reported to police the next day, September 24. The victim then took part in an interview on October 9, in which she said, when she was alone in Chapman’s office, he placed his hand on her upper thigh and his other hand on her lower back, underneath her trousers. The defendant was arrested and interviewed at Lurgan police station, where he denied the allegations. His phone was seized and an examination was carried out. The first interview of the defendant took place on October 9, during which he admitted to sending a message about wanting the victim to work 24/7, but stated this was a joke. The second interview took place on January 28, 2021, where he admitted to sending the 24/7 message, but denied sending other messages, such as “hope you’re spending the pounds on something special”. Throughout this process, Chapman denied sending the messages and denied any of the sexual assaults alleged by the victim. On the Chapman’s criminal record, the prosecution added that he was convicted of three common assaults on appeal. In terms of commission, these matters pre-dated this case but the conviction occurred during the running of this case and also involved a female working for the defendant. Prosecution continued that the age of the victim was an aggravating feature, arguing there was a “vulnerability” due to the “power-imbalance” between Chapman and the young student working for him. An additional aggravating feature, they said, was that during the course of the defence, part of the defence was that the victim had “manipulated or manufactured” some of the text messages that were sent. A defence lawyer, speaking on the pre-sentence report, noted the author deemed Chapman to be of low risk. He also noted that similar offences were contested in the County Court in respect of another complaint, with the judge substituting indecent assault charges for common assault. He also argued a Sexual Offences Prevention Order (SOPO) was not necessary as the offending was four years ago, there has been no repetition and risk had been addressed. District Judge Eamonn King noted the defendant was convicted on two of four original charges following a contest, which ran over a number of days, with the case adjourned for a pre-sentence report and victim impact statement to be produced. He added the defendant “continues to deny” the charges and seeks to appeal the outcome. District Judge King, on reading the pre-sentence report, noted the defendant “denies ever hugging or touching the individual and he denies any sexual attraction to the victim”, but pointed to a paragraph in the report which stated, “From the available evidence, it’s possible to surmise that he demonstrated risk taking and impulsive behaviour. It appears that he took advantage of his position and power in a bid to meet his sexual needs, given the victim’s young age and the fact that he was her employer”. The report added that this demonstrated “limited victim empathy and responsibility due to his denial of the offences”. On the victim impact statement, District Judge King described her as a young girl getting her first job, with the “world as her oyster”. He continued: “As a result of what she says occurred, that turned on its head. It left her feeling inwardly uncomfortable, anxious and lonely. She cut herself off from her friends. She stopped going out. She didn’t want to go to school.” He also described a “degree of manipulation” in the case, as this was the victim’s first job and there was a power imbalance between her as an employee, and Chapman as the employer. In his sentencing remarks, District Judge King, said: “I’ve taken time to emphasise to the victim in this case that the victim did nothing wrong. The victim did everything right and the victim shouldn’t feel lonely, anxious or isolated. “The victim should feel confident, strong and outgoing.” Owing to the defendant’s ongoing denial of the charges, he added: “My sentencing exercise isn’t the conclusion of the case today, but I will sentence, so that we can move towards the conclusion going forward. “I am satisfied, irrespective of what the pre-sentence report says, that the defendant took advantage of someone, attempted to groom someone and was guilty of the two offences.” On the two counts, Chapman was sentenced to three months in prison, suspended for two years. He was also made subject to a Sexual Offences Prevention Order (SOPO) for five years and placed on the sex offenders’ register for seven years. Following sentencing, District Judge King fixed bail for appeal at £1,000.

Use of AI is certainly the hottest topic in the tech industry and every major and minor player in this industry is using AI in some way. Tools like ChatGPT can help you do a wide range of task and even help you generate images. The other thing is - Voice Cloning. OpenAI recently introduced a voice engine that can generate clone of your voice with just 15 seconds of your audio. There is no shortage of voice cloning tools on the web which can help you do the same. The newest tech giant which is going to use AI to clone your voice is - TikTok. We all know TikTok, posting short videos with filters, effects and all other kind of things. So TikTok found a way to use the voice cloning AI in its app. TikTok is working on this feature, which does not seem to really have a proper name, it just references it as "Create your voice with AI" and "TikTok Voice Library". In the latest version of TikTok I came across some strings which indicates that TikTok is working on it. I was also able to access the initial UI which introduces the feature and was able to see the terms and condition of "TikTok Voice Library" which user have to accept in order to use the feature. Here are the screenshots from the app- As you can in the screenshot above, this is the initial screen which a user will see for the first time they access this feature. Tiktok claims that it can create an AI verison of your voice in just 10 seconds. The generated AI voice clone can be used with text-to-speech in TikTok videos. It also outline the process of how it will work. You have to record yourself speaking and TikTok will process the voice and use information about your voice to generate your AI voice. When it comes to privacy, your AI voice will stay private and you can delete it anytime. Tapping the "Continue" button brings "TikTok Voice Library Terms" screen which a user should definitely read, you can see here and read as well - How it will work After agreeing to terms and conditions I was introduced with a screen where TikTok will show some text and user have to press the record button while reading the text. Now unfortunately I did not see any text. This is probably because the feature is not fully ready or the backend from which it fetches the text is not live yet. Manually pressing the record button and saying random things also shows an error. So, it's also not possible to provide any sample voice generated with it and see how it compares to other voice cloning competitors. If it starts working someday, it will process your recorded voice and generate AI version of your voice. Here is a screenshot of that screen - My guess is that whenever the feature starts working, users have to clone voice only one time and the saved AI voice can be used through the text-to-speech method to add voice in your videos. You just have to type the words, choice is yours :p