With the recent changes, as of Issue #41, it is now possible to force user Name Sync data by mass inserting for every future post number, where the user's new request will not "overwrite" their name.
It has been, and also is currently, possible to insert very large numbers of requests, making the API output larger, which could be used as a malicious attack against the server.
Either implementing a temporary ban of some sort, or validating against whether or not a post exists on 4chan may be a possible solution to both of these.
With the recent changes, as of Issue #41, it is now possible to force user Name Sync data by mass inserting for every future post number, where the user's new request will not "overwrite" their name.
It has been, and also is currently, possible to insert very large numbers of requests, making the API output larger, which could be used as a malicious attack against the server.
Either implementing a temporary ban of some sort, or validating against whether or not a post exists on 4chan may be a possible solution to both of these.