> maybe you could change it to opt-in per domain? Or opt-out for domains accessed via http and opt-in for ones accessed via https. I'd say I visit a couple hun

> maybe you could change it to opt-in per domain? Or opt-out for domains accessed via http and opt-in for ones accessed via https. I'd say I visit a couple hundred pages a day. On many different domains. The point of the extension is to index what I visit to make it easy to search - it's only useful if it indexes the majority of the content I visit. Having to opt-in per domain could quickly become tiring. Opt-out for domains accessed via HTTP and opt-in for ones accessed via HTTPS sounds fine in principle but I'd imagine it could quickly become confusing, especially for users who aren't really family with HTTP(S). And as more and more websites switch to HTTPS, you would find yourself having to manually opt-in more and more, and you'd have the same problem as opt-in per domain. I'm not normally a big fan of opt-out, but I think that if the point of the extension is to index pages you visit, and to be useful it has to index the majority of the content, it might make sense to make it opt-out. You could include a list of default domains that are opted-out when the extension is installed, like bank websites and stuff. If it's open source you could invite users to submit pull requests with more domains that should be opted-out of by default.