Nadella rakes in USD 35 million in share sale

Twitter has joined efforts to do away with racially loaded terms such as master, slave and blacklist from its coding language in the wake of the death of African-American George Floyd and ensuing Black Lives Matter protests.

The project started even before the current movement for racial justice escalated following the death of 46-year-old George Floyd in police custody in May.

The use of terms such as "master" and "slave" in programming language originated decades ago. While "master" is used to refer to the primary version of a code, "slave" refers to the replicas. Similarly, the term "Blacklist" is used to refer to items which are meant to be automatically denied.

The efforts to change these terms in favour of more inclusive language at Twitter were initiated by Regynald Augustin and Kevin Oliver and the microblogging platform is now backing their efforts.

"Inclusive language plays a critical role in fostering an environment where everyone belongs. At Twitter, the language we have been using in our code does not reflect our values as a company or represent the people we serve. We want to change that. #WordsMatter," Twitter's engineering team said in a post on Thursday.

As per the recommendations from the team, the term "whitelist" could be replaced by "allowlist" and "blacklist" by "denylist".

Similarly, "master/slave" could be replaced by "leader/follower", "primary/replica" or "primary/standby".

Twitter, however, is not the first to start a project to bring inclusivity in programming language.

According to a report in CNET, the team behind the Drupal online publishing software started using "primary/replica" in place of "master/slave" as early as in 2014.

The use of the terms "master/slave" was also dropped by developers of the Python programming language in 2018.

Now similar efforts are underway at Microsoft's Github and LinkedIn divisions as well, said the report.

New Delhi, Jul 18: India's national cybersecurity agency CERT-in, has warned people of credit card skimming spreading across the world through e-commerce platforms.

Attackers are typically targeting e-commerce sites because of their wide presence, popularity and the environment LAMP (Linux, Apache, MySQL, and PHP), the Computer Emergency Response Team (CERT-In) said in a notice on Thursday.

Recently, attackers targeted sites which were hosted on Microsoft's IIS server running with the ASP.NET web application framework, it said.

Some of the sites affected by the attack were found to be running ASP.NET version 4.0.30319, which is no longer officially supported by Microsoft and may contain multiple vulnerabilities, CERT-In said.

The notice also included a list of best practices for website developers including the use of the latest version of ASP.NET web framework, IIS web server and database server.

The advisory is based on research by Malwarebytes which found that this skimming campaign likely began sometime in April this year.

Credit card skimming has become a popular activity for cybercriminals over the past few years, and the increase in online shopping during the pandemic means additional business for them, too, Malwarebytes said in a blog post, adding that attackers do not need to limit themselves to the most popular e-commerce platforms.

Researchers from global cybersecurity and anti-virus brand Kaspersky had warned in December last year that more cybercriminal groups will target online payment processing systems in 2020. 

It said that over the past couple of years, so-called JS-skimming (the method of stealing of payment card data from online stores), has gained immense popularity among attackers. 

Kaspersky researchers in their report said they are currently aware of at least 10 different actors involved in these type of attacks.

Their number will continue to grow during the next year, the report said, adding that the most dangerous attacks will be on companies that provide services such as e-commerce as-a-service, which will lead to the compromise of thousands of companies.

In a first, the Supreme Court on Friday allowed the service of summons and notices, a necessity in almost all legal proceedings, through instant messenger like WhatsApp as well as by e-mail and fax.

A bench headed by Chief Justice SA Bobde observed that it has been brought to the notice of the court that it is not feasible to visit post offices for service of notices, summons, and pleadings. The bench also comprising Justices AS Bopanna and R Subhash Reddy observed that notice and summons should be sent through e-mail on the same day along with instant message through WhatsApp and other phone messenger services.

The bench clarified that all methods should be deployed for a valid service on the party. "Two blue ticks would convey that the receiver has seen the notice," noted the bench.

The bench declined the request of the Attorney General for specifically naming WhatsApp as a mode of effectuating service. The top court noted that it would not be practical to specify only WhatsApp. The apex court also permitted RBI to extend the validity of cheques in the backdrop of lockdown to contain the coronavirus outbreak.

Senior advocate V Giri representing RBI informed the bench that he had circulated the note regarding validity of a cheque as directions issued on the previous hearing.

The bench noted that it will be in discretion of the RBI to issue orders which are suitable to alter the validity of the period of a cheque.

During an earlier hearing on the matter on July 7, the Attorney General contended before the top court that the Centre had some reservations in connection with the utilization of mobile applications like WhatsApp and other apps for service of summons. The Centre's top law officer informed the apex court that these apps claimed to be encrypted, and they were not trustworthy.

The RBI counsel had contended before the top court that it was considering clarifying the validity of a cheque which has been reduced to 3 months from 6 months.