miamiww / big-tech-detective Goto Github PK

Strange behavior happens when the extension page is refreshed. The background page stops recognizing that there is an extension page open and stops sending packet data to the charts on the extension page. Additionally a second page can be opened and the previous page does not close.

Currently BTD will rarely associate requests with a web site when the requests were originated by the previous site visited in the tab. For example, when clicking a link in google.com, the browser navigates away from Google and onto the search result's page. But google.com makes a variety of requests whenever a link is clicked and it is navigated away from. Because those requests happen at the same time as the url of the tab changes to the new link, BTD associates those requests with the new url even though they came from google.com. The fix for this is easy, and is implemented in the WIP-initiatior-fix branch in the blockTime function within content.js. BTD just needs to check the url of the initiator of the request agains the url of the current page and this issue no longer occurs. However, requests made by iframes have the initiator as the url of the iframe, and not of the website that the iframe is embedded within, so with this fix BTD will no longer trigger a lock from an iframe-requested resource or show requests made by iframes in the lock page. Currently working on a way to avoid associating requests with a new URL when navigating away from an old one.

Does this work in Brave? (Ubuntu 20.04)

It fails to load with error "Manifest file is missing or unreadable"

That's a great project. Continue with your idea ! ❤❤

Stop requests from loading until their origin can be ascertained and blocked/allowed as is fit.

Possible methods:
https://stackoverflow.com/questions/41281291/chrome-extension-block-page-items-before-access

Similar behavior to:
https://github.com/gorhill/uMatrix/tree/master/platform/chromium

the error :
Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.
{
"manifest_version": 2,
"name": "Big Tech Detective",
"version": "1.0.0",
"background": {
"scripts": [
"background.js",
"reload.js"
]
},
"content_scripts":[
{
"matches": ["<all_urls>"],
"js": ["lib/d3.min.js", "content.js"],
"css": ["pagecss.css"]
}],
"browser_action": {
"default_icon": "btd_icon_logo_128x128.png"

},
"permissions": [
	"<all_urls>",
	"tabs",
	"webRequest",
	"storage"
],
"web_accessible_resources":["assets/icons/unlock_icon.png","assets/icons/lock_icon.png", "assets/icons/copy_clipboard.png","assets/fonts/basis-grotesque-mono.otf","assets/fonts/GT-Walsheim-Regular.otf","assets/fonts/GT-Walsheim-Bold.otf","assets/fonts/GT-Walsheim-Black.otf"]

}