Add description page for Gitea API Protector
parent
0ee3420855
commit
d13e8891a4
@ -1 +1 @@
|
||||
3544450995 2099
|
||||
381269847 2090
|
||||
|
@ -1 +1 @@
|
||||
1653402568
|
||||
1653462513
|
||||
|
@ -1 +1 @@
|
||||
72850756 6424
|
||||
2000627787 6392
|
||||
|
@ -1 +1 @@
|
||||
1653457975
|
||||
1653462215
|
||||
|
@ -0,0 +1,26 @@
|
||||
<header>Gitea API Protector</header>
|
||||
<p>
|
||||
I built the Gitea API Protector in response to a request for help that
|
||||
maintainers of <a href="https://codeberg.org">codeberg.org</a> put out on the
|
||||
fediverse in january of 2020. Codeberg was (and probably still is) one of the
|
||||
largest public <a href="https://gitea.io">gitea</a> instances and as such was
|
||||
having trouble with spam bots that would create spam issues on repositories
|
||||
using the API. My solution was to lock new users out of API access and have
|
||||
them apply for it through a pull request they could create using the gitea web
|
||||
UI. The people from codeberg
|
||||
were <a href="https://github.com/go-gitea/gitea/issues/9847#issuecomment-575799090">interested</a>,
|
||||
but in the end they didn't end up going with my solution. Nevertheless the
|
||||
software is fully functional and the codebase is small enough for people to
|
||||
change it for their own use cases if they so desired.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
A more elaborate explanation of the technical details an setup instructions can
|
||||
be found in the README of the repository
|
||||
on <a href="https://github.com/hugot/gitea-api-protector">github</a> or
|
||||
on <a href="https://codeberg.org">codeberg.org</a>.
|
||||
</p>
|
||||
|
||||
<!-- Local Variables: -->
|
||||
<!-- sgml-basic-offset: 1 -->
|
||||
<!-- End: -->
|
@ -0,0 +1 @@
|
||||
452533407 1259
|
@ -0,0 +1 @@
|
||||
1653462474
|
@ -0,0 +1 @@
|
||||
1653462215
|
Loading…
Reference in New Issue