4 ms·
Yes, but you could disable it when you don't mind seeing NSFW content.
by ptm 19y ago
Yes, but you could disable it when you don't mind seeing NSFW content.
- ten-seven 19y agoStill, this is a deal killer.
- ptm 19y agoI understand this would raise red flags for a yc type crowd. Would the average surfer feel as strongly ?
- wanorris 19y agoIf the site contained a strong privacy guarantee on the front page -- basically, no data about individuals' surfing habits will be stored, but aggregate data about overall traffic will be stored unless you opt out -- I would use it if I needed it.
- Husafan 19y agoWhy do you need to rewrite links to your server? Can your extension not insert JavaScript to do most of this logic client-side?
- ptm 19y agoActually it uses Javascript to rewrite links. But the info about links being safe of not are contained in the server links. I could pre-emptively get info about all links, but that would slow down Firefox.
- Husafan 19y agoGotcha. Well maybe you could do this asynchronously, after page load? Once the page is done loading, extension fires off for info about links on the page? Assuming this didn't take to long, it might be doable before they clicked a new link. Also, extensions have access to cookies per domain? Maybe the extension could use this to cache results for a given page client-side?
- ptm 19y agoI could do that. I had decided against it earlier due to the potential lag.
- marrone 19y agoTraversing the entire DOM on page load and rewriting all links for large pages would also slow down the page though. Also rewriting links seems too intrusive for my tastes and means I cant "Copy link location" which I frequently do. I like the idea, but I personally would have just used a single "click" event handler on the entire page using the capturing phase and hijack links to redirect through your site first, rather than doing a rewrite for every link in the dom