Aadhaar-Based eKYC Re-Verification for All Mobile Subscribers Should Be Completed Within a Year: DoT

Facebook will introduce a new notification screen on its platform that will warn users if the article they are about to share is over 90 days old, the company announced on Thursday.

“We’re starting to globally roll out a notification screen that will let people know when news articles they are about to share are more than 90 days old,” Facebook wrote in a blog post.

The social media platform had previously introduced a context button in 2018 that provides information about the sources of articles in the News Feed. Building upon that, the new feature will inform users about the timeliness of the article.

“To ensure people have the context they need to make informed decisions about what to share on Facebook, the notification screen will appear when people click the share button on articles older than 90 days, but will allow people to continue sharing if they decide an article is still relevant,” Facebook said.

The social media giant stated that timeliness is important in understanding the context of an article and curbing the spread of misinformation on the platform.

“News publishers, in particular, have expressed concerns about older stories being shared on social media as current news, which can misconstrue the state of current events. Some news publishers have already taken steps to address this on their own websites by prominently labelling older articles to prevent outdated news from being used in misleading ways,” Facebook added.

Apart from this, the platform will also be testing a similar notification screen for information related to the global Covid-19 pandemic. The notification screen will provide information about the source of the link shared in a post if the link is related to information on Covid-19. It will also direct people to its previously introduced Covid-19 information centre for “authoritative” health information, it said.

The GST Council is unlikely to make major changes in the indirect tax structure at its next meeting slated mid June.

A top government source said that the Centre is not in favour of increasing tax rates on any goods or service as it could further impact consumption and demand that is already suppressed due the COVID-19 pandemic and lockdown.

It was widely expected that the GST Council could consider raising tax rates and cess on certain non-essential items to boost revenue for states and the Centre. Several states have reportedly taken an over 80-90 per cent hit in GST collections in April, the official data for which has not yet been released by the Centre.

"The need of the hour is to boost consumption and improve demand. By categorising items into essential and non-essential and then raising taxes on non-essential is not what Centre favours. But, the issue on rates and relief will be decided by the GST Council that is meeting next month," the finance ministry official source quoted above said.

The GST Council is chaired by the Union finance minister and thus the views of the Centre play out strongly in the council meetings.

However, the Council will also have to balance the expectations of the states whose revenues have nosedived after the coronavirus outbreak and wide scale disruption to businesses while they have still not been paid GST compensation since the December-January period.

To the question of wider scale job losses in the period of lockdown as businesses get widely impacted, the official said that the Finance Ministry has asked the labour ministry to collect data on job losses during Covid-19 and is constantly engaging with the ministry to oversee job losses and salary cuts.

On restrictions put on Chinese investment in India, the official clarified that no decision had yet been taken to restrict China through the Foreign Portfolio Investment (FPI) route.

Asked about monetising government debt, the official said that the issue would be looked at when we reach a stage. It has not come to that stage yet.

In the government's over Rs 20 lakh crore economic package, the official defended its structure while suggesting that comparisons with the economic packages of other countries should not be drawn as India's needs were different from others.

"We have gone in more reforms that is needed to give strength to the economy. This is required more in our country," the official source said.

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.