Google Docs is having some serious issues with its new “inclusive language” warnings

Google is nothing if not helpful: the search giant has built its reputation on making the internet more accessible and easier to navigate. But not all of its innovations are either clever or welcome. 

Take the latest change to Google Docs, which aims to highlight examples of non-inclusive language through pop-up warnings. 

You might think this is a good idea, helping to avoid “chairman” or “fireman” and other gendered language – and you'd be right. But Google has taken things a step further than it really needed to, leading to some pretty hilarious results.

Inclusive?

A viral tweet was the first warning sign that perhaps, just perhaps, this feature was a little overeager to correct common word usages. After all, is “landlord” really an example of of “words that may not be inclusive to all readers”? 

As Vice has ably demonstrated, Google's latest update to Docs – while undoubtedly well-intentioned – is annoying and broken, jumping in to suggest corrections to some things while blatantly ignoring others. 

See more

A good idea, poorly executed 

The idea behind the feature is well-meaning and will likely help in certain cases. The execution, on the other hand, is poor. 

Vice found that Docs suggested more inclusive language in a range of scenarios, such as for “annoyed” or “Motherboard”, but failed to suggest anything when a speech from neo-Nazi Klan leader David Duke was pasted in, containing the N-word. 

In fact, Valerie Solanas’ SCUM Manifesto – a legendary piece of literature – got more edits than Duke's speech, including suggesting “police officers” instead of “policemen”. 

All in all, it's the latest example of an AI-powered feature that seems like a good idea but in practice has more holes than a Swiss cheese. 

Helping people write in a more inclusive way is a lofty goal, but the implementation leaves a lot to be desired and, ultimately, makes the process of writing harder. 

Via Vice

TechRadar – All the latest technology news

Read More

GitHub wants to help developers spot security issues before they get too serious

In an effort to further secure open source software, GitHub has announced that the GitHub Advisory Database is now open to community contributions.

While the company has its own teams of security researchers that carefully review all changes and help keep security advisories up to date, community members often have additional insights and intelligence on CVEs but lack a place to share this knowledge.

This is why GitHub is publishing the full contents of its Advisory Database to a new public repository to make it easier for the community to leverage this data. At the same time, the company has built a new user interface for security researchers, academics and enthusiasts to make contributions.

All of the data in the GitHub Advisory Database is licensed under a Creative Commons license and has been since the database was first created to ensure that it remains free and usable by the community.

Contributing to a security advisory

In order to provide a community contribution to a security advisory, GitHub users first need to navigate to the advisory they wish to contribute to and submit their research through the “suggest improvements for this vulnerability” workflow. Here they can suggest changes or provide more context on packages, affected versions, impacted ecosystems and more.

The form will then walk users through opening a pull request that details their suggested changes. Once this done, security researchers from the GitHub Security Lab as well as the maintainer of the project who filed the CVE  will be able to review the request. Contributors will also get public credit on their GitHub profile once their contribution has been merged.

In an attempt to further interoperability, advisories in the GitHub Advisory Database repository use the Open Source Vulnerabilities (OSV) format. Software engineer for Google's Open Source Security Team, Oliver Chang provided further details on the OSV format in a blog post, saying:

“In order for vulnerability management in open source to scale, security advisories need to be broadly accessible and easily contributed to by all. OSV provides that capability.”

We'll likely more on this change to the GitHub Advisory Database once security researchers, academics and enthusiasts begin making their own contributions to the company's database.

TechRadar – All the latest technology news

Read More