Auto-creqing: Difference between revisions

Auto-creqing (view source)

3 bytes added , 22 April 2009

m

no edit summary

1,633

edits

@@ Line 5: / Line 5: @@
 ===Old system===
-The "old" autocreq system is part of the TCP API and is still in use. The API basically allows editing/creqing of many AniDB data types but has a special option for files and file tracks; autocreq (which means ''this creq was automatically generated by the client''). An autocreq does not necessary have to be handled by a moderator; it will be granted automatically if it was submitted by a trusted client '''and''' passes some basic sanity tests. (Automatic granting is however delayed 24h to be able to stop/revert creqs from "bad" clients.)
+The "old" auto-creq system is part of the TCP API and is still in use. The API basically allows editing/creqing of many AniDB data types but has a special option for files and file tracks; auto-creq (which means ''this creq was automatically generated by the client''). An auto-creq does not necessary have to be handled by a moderator; it will be granted automatically if it was submitted by a trusted client '''and''' passes some basic sanity tests. (Automatic granting is however delayed 24h to be able to stop/revert creqs from "bad" clients.)
 This means that all TCP API clients can automatically creq files as they see fit and there is no way to control this from the sever side except banning clients completely. This has never been a big issue, though, since it is only one TCP API client (AOM).