Python3 Support about open_nsfw HOT 8 OPEN

@rahiel, We don't have anyone to maintain this repo anymore, but we're more than happy to hand it off to community members to take on maintainership. Is this something you'd be interested in? Or would you simply be interested in upstreaming python 3 support? I can grant you write access either way.

from open_nsfw.

Hey @BenLloydPearson, I am interested in maintaining this.

Do you think the HTTP REST interface I made at open_nsfw-- would be a fit for the main open_nsfw project? The benefit of a HTTP interface is that people can use it with any programming language they like.

from open_nsfw.

I have a fork of open_nsfw with Python3 support here: https://github.com/rahiel/open_nsfw--

from open_nsfw.

Awesome I will check it out, but is there any chance to port this back into the upstream repo?

from open_nsfw.

As far as I can see, this repo is not maintained anymore. There are many pull requests left open. That's why I decided to fork it. This fork also has an additional goal of making it very easy to deploy the model in production.

I can upstream Python3 support if this repo becomes active again.

from open_nsfw.

I think the REST interface is interesting but I'd much prefer it if we could pass a multipart encoded file object, or a URL, something we can easily expand on. I agree we need a new maintainer for this, my main interest in OpenNSFW is for inclusion as a plugin in OpenStack Nemesis, it aims to make a file scanning API which provides intelligence about files. - https://github.com/openstack/nemesis

from open_nsfw.

I think the REST interface is interesting but I'd much prefer it if we could pass a multipart encoded file object, or a URL, something we can easily expand on. I agree we need a new maintainer for this, my main interest in OpenNSFW is for inclusion as a plugin in OpenStack Nemesis, it aims to make a file scanning API which provides intelligence about files. - https://github.com/openstack/nemesis

Currently you can already pass URLs to the API , I've made an issue for multipart encoded files (1#).

from open_nsfw.

@rahiel I invited you to have write access to this repo so you can work on merging improvements. There is currently branch protection on master to require one review before merging PR's. This will allow you to merge other's improvements, and feel free to ping me directly if you need help with reviews for your PR's. If anyone else in this thread is interested in helping with this, please reach out to me.

from open_nsfw.