After a few messages on my main thread for this program, someone mentioned that the e621 blacklist system may now be working with the API as well. But, instead of removing the post like one would assume, it instead just nullifies the post. This means when I grab a collection of posts through a bulk search, a few of those posts will now be null. Any links to the file, preview, or sample, are all null now. So what I have to do, is I'm going to disable the blacklist system and see and then verify if this is actually the case. I'm also going to have to re-enable cookies and check if my user account will alter what post become null. Doing this will let me know if the blacklist on their site is actually working with the API now, or if there is a bug on the server side that I need to figure out or know about.
This isn't the case. e621 is actually using a filtering system when users are logged out, the only form of a blacklist it uses is young -rating:s, this is because of legality issues.
After a few messages on my main thread for this program, someone mentioned that the e621 blacklist system may now be working with the API as well. But, instead of removing the post like one would assume, it instead just nullifies the post. This means when I grab a collection of posts through a bulk search, a few of those posts will now be null. Any links to the file, preview, or sample, are all null now. So what I have to do, is I'm going to disable the blacklist system and see and then verify if this is actually the case. I'm also going to have to re-enable cookies and check if my user account will alter what post become null. Doing this will let me know if the blacklist on their site is actually working with the API now, or if there is a bug on the server side that I need to figure out or know about.