3 ms·
introduce a captcha for known porn-sites wont affect others
by theGeatZhopa 2y ago
introduce a captcha for known porn-sites wont affect others
- KouroshGhaffari 2y agoSorry could you elaborate on that please? Just a captcha before they can use the product?
- theGeatZhopa 2y agoits an extension as i see. You told, you can see which sites your extension is used on. If its a porn site, make it unattractive to use your extension on such sites or accept/use that knowledge. one way of making it unattractive is to put a captcha or some distracting something before the text is put into the input-field. Or you accept that a multipurpose tool is used multipurpose :)
- thrw42A8N 2y agoWhy would he drive away his users?
- theGeatZhopa 2y agoit may be needed for certain markets and advertisements - the question should be pointed toward the OP. Why is he even asking that?? - lean into it corresponds to accept that smthg built by you is used for porn. - not lean into it corresponds to drive away his users. so, why is OP considering not to lean into and by that risking to drive away the users - should be the question :)
- thrw42A8N 2y agoIt's one thing to not lean into the use case, a completely another thing to make this group of users suffer through captcha just because you don't like them.
- theGeatZhopa 2y agoso, whats your solution for OP if he doesn't want to lean into? 1. stop them from using it there (= drive away users) 2. make them suffer by captcha on such sites (= drive away users, as you implied in your first answer) 3. lean into it (= let them use it on porn sites) I really don't get your intention. Do you mean OP should let them use the built tool?
- thrw42A8N 2y ago3. Leaning into it isn't just letting them be, it's making more specifically for these users and their use cases. 4. Just let them be...? OP, lean into it. Money is green regardless of what sound your tool generated.
- theGeatZhopa 2y agonow i get your point. "not leaning into it" means exactly and exclusively to stop the usage on porn-sites. There's no misinterpretation possible. Sort of EULA, specifically defining use cases or some "i don't lean into so please do not do that" wouldn't stop anyone. If there are no sanctions, no nag-screens, Captchas and no other ways to make the use of that extension on porn sites cumbersome - then it will be used on such sites. I don't know the reasons of OP is even asking it. Thus, i told to put a captcha on such sites. Having distracting captchas is a mild solution. Blocking is the hardest. Other than that, there's no way of "not leaning into" that would work. I may've over-read your solution of the problem and how OP could make it more specifically for these users and their use cases, in case he/she/it doesn't want to lean into...
- thrw42A8N 2y agoWell yeah, this is the confusion. My understanding: - Lean into it - perform work to make it better for these users. - Not lean into it - let it be as it is. My opinion is - why are they a problem? I don't see a reason to block them. I'd lean into it fully, it's the product-market fit startup god screaming at you, but I guess people don't like working in this market - sure. Why block them though?