Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capture submissions to BBFC #215

Open
JimKillock opened this issue Mar 3, 2019 · 3 comments
Open

Capture submissions to BBFC #215

JimKillock opened this issue Mar 3, 2019 · 3 comments
Assignees

Comments

@JimKillock
Copy link
Member

Once we have #214 in place, we can try to captiure submissions and correspondence with BBFC.

The BBFC is a one step form, without any capture as such.

http://www.bbfc.co.uk/what-classification/mobile-content/appeals/mobile-complaint-form

We would only allow appeals to be submitted once correspondence was logged from at least one mobile provider, and once we had retested the blocks (after say 3 three days from the correspondence) to show that they are still in place.

We would need to construct a page explaining BBFC guidance, and other factors to consider.

We would want to email the original complainant to give them a chance to submit a review request.

@edjw
Copy link

edjw commented May 30, 2019

@JimKillock – I remember you saying you'd had some useful conversations about how we might set this up in a constructive way. Do you want to write that down here?

@JimKillock
Copy link
Member Author

I think we can start with this as is. The issues would start if we were 'bulk processing' complaints eg of wedding sites.

dantheta added a commit to dantheta/blocked-frontend-py that referenced this issue Aug 8, 2019
dantheta added a commit to openrightsgroup/Blocking-Middleware that referenced this issue Aug 24, 2019
dantheta added a commit to dantheta/blocked-frontend-py that referenced this issue Aug 24, 2019
dantheta added a commit to openrightsgroup/Blocking-Middleware that referenced this issue Aug 24, 2019
@dantheta
Copy link

Ready for release during the next week. I'll send one check (mentioning that it's us in the comment) to make sure the form submission works OK.

They aren't using a captcha on the form, but there is a CSRF token embedded in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants