https://codeberg.org/user/sing_up
it should be sign_up instead of sing_up.
https://codeberg.org/user/sing_up
it should be sign_up instead of sing_up.
No, this is intentional 🙃
Quoting hw:
This intended to make it a tiny bit harder for bots that flooded us in the past with automatically submitted abusive registration+login requests. It is simplicistic but worked nicely so far. If bots catch up in the cat'n'mouse game and start their requests on this endpoint, we will have to fully randomize it to make it fully unpredictible.
Please don't abuse login or we need to add further restrictions.
Also see #439, #427, #383, #181, #127. Thank you for reporting your findings anyway. Welcome to Codeberg.
Wouldn't it be better to use a turing test instead?
What do you mean? We already have a captcha in place, but there are also captcha-solving services (where humans in certain countries are paid via BTC to do the work). The point is that this doesn't really prevent targetted attacks on Codeberg, but automated bots that search Gitea instances and spam them (as they'd need to change the URL just for Codeberg).
Of course, better spam protection is still a topic we are working on.
I wonder if it would be possible to call sign up page sigո_up instead to avoid questions (using Armenian "ո" character here). Unicode tricks like this have an additional advantage in that they use Unicode, so they could confuse bots that poorly implement Unicode (an actual web browser will URL-encode "ո" as %D5%B8, but a bot may not be able to).
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?