EasyList Forum

Hello,

Recently the following line was added to the EasyPrivacy list: Crowdskout allows our clients to create forms that they can embed on their website, similar to Survey Monkey or other form builder services. With the addition of this line however, this removes all of these forms from all of our client's web sites. I don't think the intention of EasyPrivacy is to prevent users from willfully providing information.

You can see an example of a site with a blocked form here:
http://businessroundtable.org/test-your-tax-knowledge

FWIW, this is the changeset where it was added: https://hg.adblockplus.org/easylist/rev/608ad892c6ed

It seems very much a tracker to me. all 3 scripts. I'm not keen at removing this filter.

https://hg.adblockplus.org/easylist/rev/110f91d03376

Might be a better compromise to fix the non-tracker stuff.

fanboy wrote:https://hg.adblockplus.org/easylist/rev/110f91d03376

Check the TLD of the second filter https://hg.adblockplus.org/easylist/rev ... 3376#l1.30

Thanks

https://hg.adblockplus.org/easylist/rev/3b4e175476a4

Hey All -

This amended is still going to cause issues with submissions. Currently it will show the form, but will not successfully send data to our server without
s.crowdskout.com/analytics.js

You're correct that there is a tracking component to our software, and I don't want to try and circumvent people who opt out of that. If you were to block everything at a.crowdskout.com and s.crowdskout.com except for the following routes:
The * is indicating a single level of directory that is a version indicator (it looks like a.crowdskout.com/v1-1/form).

This would prevent almost any kind of tracking except for the form submission. Skout.js does set a third party cookie on the user's browser with a unique identifier. I can imagine that that would be an issue with EasyPrivacy, however all requests outside of the form submission that use that unique identifier would be blocked with the proposed rules above. Our forms as they're currently written cannot function without that cookie.

If this is a deal-breaker on your end, we can spend time to rewrite the code to work without skout.js, but that would leave our forms down for a bit, so I wanted to see if we could work it out.

Example site would be helpful so I can test.

Is the example provided in the initial post not what you're looking for? (http://businessroundtable.org/test-your-tax-knowledge) Or would you like a completely example form where submission will be meaningless?

The rules as defined right now block both our tracker and our embedded forms. Previously our forms required the tracker to correctly associate data inside our system. We have since done the development work required to decouple the two to allow privacy groups to block the tracker while still allowing their users to fill out the forms and intentionally provide information.

The final step here is to request you to change the ruleset currently blocking crowdskout.com requests, there are two options. The first is to block only the following: The second option is to only unblock these: The first option is a blacklist and provides us a little more flexibility and reduces the chance that we'll need to ask you to amend the ruleset again in the future. The second is a whitelist and provides you with more peace-of-mind. I definitely understand and respect the desire of some to protect privacy and would like to work together towards that end.

If you would like a site to test the ruleset on, you can find an embedded form here:

Okay, just made more specific, though if you add any more analytic scripts we'll re-add the filter.

https://github.com/easylist/easylist/co ... 07036c39f2