Amira  Ryan

Amira Ryan


How to build a Custom Google Chrome Extension

Writing and building a Chrome Extension is never easier!
Article on this video -
My Channel Link -
Code -
Chrome Extensions - chrome://extensions/
Publish Here -

GraphQL Tutorial Full Playlist -

Part 01 -
Part 02 -
Part 03 -
Part 04 -
Part 05 -

Other Interesting Videos and Video series application development :
------- Complete Guide on Flutter Development

------- Deep linking mobile applications

------- React Hooks Playlist

------- Fundamentals of GraphQL in Hindi

Please share your suggestions and feedback with me in the comments below or on Twitter.

Twitter -
Linkedin -
Facebook Group -
Facebook Page -
Telegram Group:

#chrome #extension #google #javascript #html #css #publish #tutorial

#chrome #extension #javascript #html #css

What is GEEK

Buddha Community

How to build a Custom Google Chrome Extension

Google's TPU's being primed for the Quantum Jump

The liquid-cooled Tensor Processing Units, built to slot into server racks, can deliver up to 100 petaflops of compute.

The liquid-cooled Tensor Processing Units, built to slot into server racks, can deliver up to 100 petaflops of compute.

As the world is gearing towards more automation and AI, the need for quantum computing has also grown exponentially. Quantum computing lies at the intersection of quantum physics and high-end computer technology, and in more than one way, hold the key to our AI-driven future.

Quantum computing requires state-of-the-art tools to perform high-end computing. This is where TPUs come in handy. TPUs or Tensor Processing Units are custom-built ASICs (Application Specific Integrated Circuits) to execute machine learning tasks efficiently. TPUs are specific hardware developed by Google for neural network machine learning, specially customised to Google’s Machine Learning software, Tensorflow.

The liquid-cooled Tensor Processing units, built to slot into server racks, can deliver up to 100 petaflops of compute. It powers Google products like Google Search, Gmail, Google Photos and Google Cloud AI APIs.

#opinions #alphabet #asics #floq #google #google alphabet #google quantum computing #google tensorflow #google tensorflow quantum #google tpu #google tpus #machine learning #quantum computer #quantum computing #quantum computing programming #quantum leap #sandbox #secret development #tensorflow #tpu #tpus

Kole  Haag

Kole Haag


Google Chrome Bugs Open Browsers to Attack

Google has stomped out several serious code-execution flaws in its Chrome browser. To exploit the flaw, an attacker would merely need to convince a target to visit a specially crafted webpage via phishing or other social-engineering lures.

Overall, Google’s release of Chrome 85.0.4183.121 for Windows, Mac and Linux – which will roll out over the coming days – fixed 10 vulnerabilities. The successful exploitation of the most severe of these could allow an attacker to execute arbitrary code in the context of the browser, according to Google. Google Chrome versions prior to 85.0.4183.121 are affected.

“Depending on the privileges associated with the application, an attacker could view, change or delete data,” according to Google’s Tuesday security advisory. “If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.”

#vulnerabilities #web security #chrome 85.0.4183.121 #chrome browser #chromium #cve-2020-15961 #cve-2020-15962 #cve-2020-15963 #cve-2020-15965 #fix #google #google chrome #google flaw #out of bounds read #security updates #stable channel release

Tyrique  Littel

Tyrique Littel


Chrome 86 Aims to Bar Abusive Notification Content

Google has added a new feature to Chrome 86 that aims to stomp out abusive notification content.

Web notifications are utilized for a variety of applications – such as prompting site visitors to sign up for newsletters. However, they can also be misused for phishing, malware or fake messages that imitate system notifications for the purpose of generating user interactions. Google has taken steps to battle this issue by automatically blocking the web notifications that display abusive or misleading content.

When visitors encounter a webpage with malicious notification content, the webpage will be blocked and a Chrome alert on the upper navigation bar will warn them that the website might be trying to trick them into displaying intrusive notifications. It will ask them to “Continue Blocking” or “Allow” – the latter option will let users continue on to the webpage.

“Abusive notification prompts are one of the top user complaints we receive about Chrome,” according to PJ McLachlan, product manager with Google, on Wednesday. “Our goal with these changes is to improve the experience for Chrome users and to reduce the incentive for abusive sites to misuse the web-notifications feature.”

In order to detect sites that send abusive notification content, Google will first subscribe occasionally to website push notifications (if the push permission is requested) via its automated web crawling service.

Notifications that are sent to the automated Chrome instances will be evaluated for abusive content, and sites sending abusive notifications will be flagged for enforcement if the issue is unresolved, said Google.

When a site is found to be in “failing” status for any type of notification abuse, Google will send a warning email to the registered owners of the site 30 days before cracking down. During this time, websites can address the issue and request another review.

Google first implemented controls that went against abusive notifications with Chrome 80, when it introduced a “quiet notification permission UI [user interface]” feature. Then, in Chrome 84, it announced auto-enrollment in quiet notification UI for websites with abusive-notification permission requests, such as sites that use deceptive patterns to request notification permissions.

However, the new enforcement in Chrome 86 takes it a step further by focusing “on notification content and is triggered by sites that have a history of sending messages containing abusive content,” said Google. “This treatment applies to sites that try to trick users into accepting the notification permission for malicious purposes, for example sites that use web notifications to send malware or to mimic system messages to obtain user login credentials.”

In an upcoming release, Chrome will revert the notification permission status from “granted” to “default” for abusive origins, preventing further notifications unless the user returns to the abusive origin and re-enables them. That’s because “prior to the release of Chrome’s abusive notifications protections, many users have already unintentionally allowed notifications from websites engaging in abusive activity,” it said.

Google this week also warned of an update to its Chrome browser that patches a zero-day vulnerability in the software’s FreeType font rendering library that was actively being exploited in the wild.

#web security #abusive content #abusive notifications #blocking #browser #browser notifications #chrome 80 #chrome 84 #chrome 86 #google #google chrome #malicious notification #safe browsing #web security

Arvel  Miller

Arvel Miller


9 Chrome Extensions To Make Your Life Easier

It’s 2021 and I am brought here some fresh new chrome extensions. And no, I will not be covering popular ones like Grammarly, uBlock Origin, Dark Reader, etc.

#chrome-extension #google-chrome #chrome #web-development #developer

Google OAuth2/OpenID Chrome Extension Login System

Don’t build your own authentication system; leverage Google OAuth2 for your Google Chrome Extension

This tutorial uses a boiler-plate Google Chrome Extension setup.

If you want to know how to get that setup,

Check out my write-up here:

Or the video tutorial here:

Before we even touch a line of code, we need to setup our development workspace so that we have the ability to do two major things:

  1. Giving our specific Chrome Extension the ability to use Google’s APIs and Services.
  2. Gain the ability to interact with Google’s OAuth2 Endpoint.

Let’s Begin.

First, we’ll need to “register” our Chrome Extension with the Google store. There are two ways to do this, we either officially upload our Chrome Extension to the Google Chrome Store and receive a unique key value for our extension or we “faux register” our extension with the Google Chrome Browser and receive a unique key that way. Since we don’t want to upload a development extension to the public store, we’ll opt for the latter method.

Navigate to the address “chrome://extensions” in your Chrome Browser.

Click on “Pack Extension” and choose the location of your Chrome Extension.

This will generate two files in the directory above your Chrome Extension location, a ‘crx’ and ‘pem’; we’re concerned with the ‘crx’ file.

Drag-and-drop the ‘crx’ file into the “chrome://extensions” page. You should get a prompt asking you to add the extension, click ‘Yes’.

Image for post

Now, navigate to where your Chrome Extensions are located.

For MacOS and Linux users, this will be different, but for Windows users you’re looking for something along the lines of,

C:\Users<Your UserName>\AppData\Local\Google\Chrome\User Data\Default\Extensions

We’re looking for the folder with same name as your Chrome Extension ID. This id can be found back at your “chrome://extensions” page. Look for the “ID” attribute.

Enter into the folder with the same name as your Chrome Extension, enter into the version number folder and open the “manifest.json” file. Copy the “key” attribute.

#programming #web-development #google-chrome-extensions #learn-to-code #chrome-extension