Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

nonsfw.com

Post reply on HN
Print view View original

21–30 of 35 posts

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#21

Post by Husafan »

ptm wrote: post #14
Husafan wrote: post #12

Earlier quoted context omitted.

Why do you need to rewrite links to your server? Can your extension not insert JavaScript to do most of this logic client-side?

Actually 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.

Gotcha. 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?

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#22

Post by marrone »

ptm wrote: post #14
Husafan wrote: post #12

Earlier quoted context omitted.

Why do you need to rewrite links to your server? Can your extension not insert JavaScript to do most of this logic client-side?

Actually 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.

Traversing 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

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#23

Post by kirubakaran »

ptm wrote: post #16

Did anyone actually install the plugin :) ? I would appreciate any bug reports / feedback.

Instead of rewriting the links, can you asynchronously (without holding up the browser) check all the external links after the page loads and mark all the nsfw links in red or something like that? This way, privacy concerns can be addressed to a certain extent (if you can also don't store the current url that I am on).

[edit:oops, just noticed that Husafan comment says pretty much the same thing.]

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#24

Post by ptm »

kirubakaran wrote: post #23
ptm wrote: post #16

Did anyone actually install the plugin :) ? I would appreciate any bug reports / feedback.

Instead of rewriting the links, can you asynchronously (without holding up the browser) check all the external links after the page loads and mark all the nsfw links in red or something like that? This way, privacy concerns can be addressed to a certain extent (if you can also don't store the current url that I am on). [edit:oops, just noticed that Husafan comment says pretty much the same thing.]

I could do that.

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#25

Post by ptm »

Husafan wrote: post #21
ptm wrote: post #14

Earlier quoted context omitted.

Actually 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.

Gotcha. 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?

I could do that.

I had decided against it earlier due to the potential lag.

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#26

Post by kirubakaran »

ptm wrote: post #24
kirubakaran wrote: post #23

Earlier quoted context omitted.

Instead of rewriting the links, can you asynchronously (without holding up the browser) check all the external links after the page loads and mark all the nsfw links in red or something like that? This way, privacy concerns can be addressed to a certain extent (if you can also don't store the current url that I am on). [edit:oops, just noticed that Husafan comment says pretty much the same thing.]

I could do that.

or may be offer both? People who want speed but aren't concerned about privacy can use the current set up. May be this can be a monetization idea too... the more private path = $5 per month "a small insurance against getting fired"

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#27

Post by kirubakaran »

ptm wrote: post #18
rksprst wrote: post #17

Just tried whitehouse.com and it said it's safe for work. i couldn't figure out how to vote on the site (without using the plugin).

For now you can only vote via the extension. And the site is pretty much empty, so all sites default to safe.

You can screen scrape nsfw.reddit

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#28

Post by ptm »

kirubakaran wrote: post #26
ptm wrote: post #24

Earlier quoted context omitted.

I could do that.

or may be offer both? People who want speed but aren't concerned about privacy can use the current set up. May be this can be a monetization idea too... the more private path = $5 per month "a small insurance against getting fired"

Won't that choice become too technical ? And is it acceptable to charge for privacy ?

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#29

Post by kirubakaran »

ptm wrote: post #28
kirubakaran wrote: post #26

Earlier quoted context omitted.

or may be offer both? People who want speed but aren't concerned about privacy can use the current set up. May be this can be a monetization idea too... the more private path = $5 per month "a small insurance against getting fired"

Won't that choice become too technical ? And is it acceptable to charge for privacy ?

Well, you have to put it in a different way :-)

IMHO you have to offer the more private option (regardless of your monetization plan) just to get the early adopters who usually are geekier than the masses and hence care about privacy.

Re: Ask YC: Feedback on my site No-NSFW, The Not-Safe-For-Work Warning System.

#30

Post by ptm »

kirubakaran wrote: post #29
ptm wrote: post #28

Earlier quoted context omitted.

Won't that choice become too technical ? And is it acceptable to charge for privacy ?

Well, you have to put it in a different way :-) IMHO you have to offer the more private option (regardless of your monetization plan) just to get the early adopters who usually are geekier than the masses and hence care about privacy.

Thanks for the inputs.

I had anticipated privacy concerns, but in all fairness, this is an early prototype.

Post reply on HN