CAPTCHAs required to join CGs
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I've had a complaint from someone unable to joint the Social Incubator CG because they can't/won't run the code for the mandatory Google reCAPTCHA. I expect to see more such complaints from members of free software and decentralisation communities; in general many find it disheartening that the first hurdle to getting involved with projects that align with their values in W3C is to jump through hoops that don't. Ethically I agree with their concerns, but pragmatically I understand there are limited resources to deal with problems like this. I know we can't fix it overnight, and indeed that many people won't see an problem at all really.
I'm opening this issue though so we can track it in case there are resources to explore alternatives. Please let me know if this isn't the right place and there's somewhere more appropriate to take it to.
See also: CAPTCHAs are horrible TAG issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this issue and the linked TAG issue, “CAPTCHAs are horrible.” The payload identifies no source files, tests, or implementation entry point. Progress would require identifying feasible alternatives to mandatory Google reCAPTCHA for joining Community Groups and agreeing on a concrete scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100