Jonathan Kingston
Jonathan Kingston
https://github.com/mozilla/lightbeam/blob/master/data/graph.js
If a first party loads lots of domains that are not recognised as content providers, it would create a very messy graph if it had: a.cdn.com b.cdn.com etc If subdomains...
The risk of tracking pixels checking what the user types isn't an issue however scripts and iframes open up different vulnerabilities.
Follow up from https://github.com/electrolyfish/lightbeam-we/pull/39 > I agree with @princiya here in that origin isn't specific of which origin. If we wanted to be more specific we might change this to...
When loading a first party we don't get update events through with the icons in.
At high/low zoom the favicon is always the same size, when zooming out this makes the favicon bigger than the circles etc.
Try pulling around a node on the graph at different zoom levels. At a high zoom level the node will move faster than the cursor is at a low zoom...
So going to wearejh.com in both new and old Lightbeam produce a very different graph. Old:  New:  The third parties in the new Lightbeam are present, I'm just...
We should consider how much storage we have available. How much do we want to store etc? I think we need limit to a week perhaps like the current one...
@princiya asked how we should be testing the extension so lets discuss that here. This example has both functional and unit tests: https://github.com/Standard8/example-webextension Unit tests likely make the most sense...