[jasonlotito]

> Why would the extension need all that above data if it's just bookmarking the page into Kippt?

It doesn't just bookmark the page. C'mon, spend a minute and actually look at what features it provides. It's on the actual Chrome plugin page.

It's obvious what it needs access to the page's content and the tabs that contain that data.

Next time, please do a little bit of reading, a tad bit of research. Don't just click next next next.

[kaizenfury7]

Uhmm...I'm going to ignore your snarkiness and condescension and just present the below data from Google's Support page for Chrome plugins:

" Your data on all websites

This item can read every page that you visit -- your bank, your web email, your Facebook page, and so on. Often, this kind of item needs to see all pages so that it can perform a limited task such as looking for RSS feeds that you might want to subscribe to.

Caution: Besides seeing all your pages, this item could use your credentials (cookies) to request or modify your data from websites."

I think it is not unreasonable to take pause when an extension asks for such permissions.

[jasonlotito]

> Often, this kind of item needs to see all pages so that it can perform a limited task such as looking for RSS feeds that you might want to subscribe to.

This is Google's issue. They provide a limited set of permissions (you want access to data about the site, you need to give permissions to read the site).

Maybe you could answer this: how else is the plug supposed to get the title of the page you are looking at without having access to the contents of the page? The title, after all, is part of that content.

> I think it is not unreasonable to take pause when an extension asks for such permissions.

It's not. It is, however, unreasonable to unfairly and dishonestly characterize a plugin without doing any research yourself.