Censored for betas

If you're a current Beta Safety user, your first thought on seeing this was probably "Isn't this what Beta Safety already does?

Beta Censoring is a simple ish app for on-demand detection and censoring of NSFW images, designed especially for betas. Beta Censoring itself is something of a middleman. Under all the covers, Beta Censoring uses the NudeNet AI model to classify images on demand then returns censored versions of the same images. Essentially, something requests an image to be censored more on the something below , Beta Censoring will load the image, run some prep work then run it through the open-source NudeNet model to detect specific body parts or features. Then, it will censor the image according to the results from the AI and the supplied preferences and return a censored version of the original image.

Censored for betas

.

Hypothetically, a high-framerate p video just 15 seconds long would take almost an hour. As for completion, censored for betas, not even close. That being said, the most common use case is in conjunction with the Beta Protection Chrome extension.

.

If you are currently using the Beta Safety Chrome extension, disable it first. Do not attempt to run both Beta Safety and Beta Protection extensions at once. Bad things will happen. Beta Protection currently supports Chrome and Edge and should work on any other Chrome derivatives like Vivaldi. The extension actually would support Firefox but Mozilla still open in new window don't support the latest version of the browser API that this extension relies on. First off, make sure you have a censoring backend running somewhere. Beta Censoring is a new highly flexible open source censoring server.

Censored for betas

In it's current form, you don't really use Beta Censoring in the traditional sense. You leave it running and other apps we call them 'clients' can interact with it, requesting images to be censored. That does mean that you need to leave it running though, as clients will need to contact the running server to request censoring.

Nhentai alternative

The points discussed below except where it says otherwise are generally referring to the "backend" part of Beta Safety, not specifically the Chrome extension. You can find a ton more information on Beta Censoring's performance, including how to monitor and tweak it, in the performance docs. Beta Protection is designed from the ground up to be a flexible bells-and-whistles-included solution for classifying and censoring images from anywhere. Then, it will censor the image according to the results from the AI and the supplied preferences and return a censored version of the original image. Beta Censoring includes its own built-in web interface for checking on the status of the server, providing limited information on requests, checking on loaded assets or monitoring the performance of the server and all of its components. For most users, this one is probably not hugely important, but it is to me, so here we are. If you request a GIF to be censored, the server will censor the first frame and return it as a static image. How is this different from Beta Safety? Beta Censoring itself is something of a middleman. Performance Due to completely different stacks and some pretty significant changes in how they work, Beta Safety and Beta Censoring have extremely different performance impacts. Hypothetically, a high-framerate p video just 15 seconds long would take almost an hour. As it stands, the NudeNet model is just nowhere near fast enough to support animations or videos with a vaguely acceptable user experience. As of v0. The runtime we use ONNX has support for multiple forms of acceleration, but I simply don't have the right combination of OS and hardware to test it. Incompatibilities There are some features from Beta Safety that Beta Censoring doesn't include, either a case of "not yet" or deliberate choice.

Beta Censoring is a simple ish app for on-demand detection and censoring of NSFW images, designed especially for betas.

Under all the covers, Beta Censoring uses the NudeNet AI model to classify images on demand then returns censored versions of the same images. If you request a GIF to be censored, the server will censor the first frame and return it as a static image. Essentially, something requests an image to be censored more on the something below , Beta Censoring will load the image, run some prep work then run it through the open-source NudeNet model to detect specific body parts or features. Due to completely different stacks and some pretty significant changes in how they work, Beta Safety and Beta Censoring have extremely different performance impacts. Performance Due to completely different stacks and some pretty significant changes in how they work, Beta Safety and Beta Censoring have extremely different performance impacts. Beta Censoring includes its own built-in web interface for checking on the status of the server, providing limited information on requests, checking on loaded assets or monitoring the performance of the server and all of its components. If you're interested in a comparison of the extension, see this page open in new window from the Beta Protection docs. Incompatibilities There are some features from Beta Safety that Beta Censoring doesn't include, either a case of "not yet" or deliberate choice. Clients Beta Censoring offers very fine-grained control of censoring so that clients can offer the most options. As such, Beta Censoring chooses to only support static images. The runtime we use ONNX has support for multiple forms of acceleration, but I simply don't have the right combination of OS and hardware to test it. Additionally, since Beta Censoring is configurable, you can customise your own performance.