I am creating an app for both iOS and Android. The app allows users to create a profile and upload short videos.
My question is, besides the manual revision of videos, how can I prevent uploads that contain nudity or anything that would usually be considered inappropriate?
Thanks for your suggestions!
If you are talking about recognizing nude images, then I'm very certain that you're out of luck. I don't think that you'll find anyt....wait a minute. I can't actually believe it.
I just went and looked for one to make sure that I was correct in saying that there is no nudity detecting API and voila! I found this:
https://www.mashape.com/rohan/nudity-detection-service#!documentation
Looks like that may be what you need. But in general, nudity detection is...not very easy to say the least. I don't think there is a simple algorithm you could implement. Your best bet is either to use that link that I just gave you, or create a system like YouTube has where offenses are punished fairly severely - things like copyright infringement and nudity result in a ban after just 3 times no questions asked.
I hope that helped. good luck!
To add on to Alex K's answer, there are many nudity detection APIs available on Mashape:
https://www.mashape.com/explore?query=nudity
https://www.mashape.com/explore?query=porn
There are quite a few APIs now available on the Mashape API marketplace for the detection of nudity in images, some still relying on skin tone detection (which has a high % of false positives) as well as newer more complex methods that deliver significantly more accurate results without dependence on skin tone such as Nude Detect.
Related
I want to upload my application data to google drive.So I have to integrate Google Drive into my application, but I can't find any proper solution or source code for do that thing. So please if any one have full code of how to use Google Drive into android application than please help me.
First, a bit of critique. If you ask a question this way ('show me the magic trick'), it will get promptly down-voted, purged. It only shows you did not do your homework.
The other possibility is that you are starting and being totally lost (been there). If this is the case, let me give you a direction:
Study the 2 APIs available to Android, the REST Api and the GDAA. They do essentially the same thing, the selection very much depends on your app's needs.
Make decision which one to use. Pay special attention to the fact the GDAA supports only FILE scope, limiting the files/folder your app can see. Weight advantages/ disadvantages.
Study / play with the demo code for the API you selected. The links are in the docs you already studied (point 1 above). In case the official Google did not meet your needs, you may also look at the basic CRUD implementations of the 2 APIs here(REST) and here(GDAA)
As you'll see, you are weeks away from getting anywhere. And don't count on anybody here to do the work for you.
Good Luck
I have seen lot of questions with this topic and read alot of articles but still cant find the best sloution for what I am looking for.
I want to build an app (Android/IOS/...whatever) which has this feature:
when the user write down a text (using killboard), the app will can recognize speech to text on what he wrote with 99.9% performance, I dont mind if he would have to record his voise first to make performance better... I want it to be "live" like Google Servies unlike Seri that writes the texts only after you finish talking.
I have found this site:
http://cmusphinx.sourceforge.net
and I wish to start working with it but before start I wanted to make sure it is the best way.
can anyone give some advises?
thanks
*edit: I dont care to build a new field for a new launguage if needed (its not in english).
I mean like, if you do some research you'll see that 99% accuracy in speech-to-text is only a very recent thing, and an example is Nuance's Dragon.
High accuracy speech-to-text can cost around $600 for a license. It's not an easy thing to create. You have to pay for high accuracy TTS libraries.
For what you're doing though, a really good service I have used is Wit.ai. It's very accurate, and its getting faster every week.
Another possibility for you might be the AT&T speech engine (Watson) found here: http://developer.att.com/
They offer 1 million API calls per month for a fee(low) and allow you to customize the "library" you use to recognize speech. It might be what you are looking for given your latest statements. You can try it for free though it is throttled until you pay.
I want to do Face recoginition (Not Face Detection) in my Android and iOS app. I have studied a lot on Web and found following possible solutions:
1.) openCV: I don't want to go into writing my own API using this. Also, I don't have prior experience in JNI for Android.
2.) Betaface API So far this is good.
3.) Sky Biometrics is also Good.
Now, I am searching for the solution from 3-5 days and came to know that I can use above API (so far I have decided to purchase license for Sky Biometrics). And this API will provide me a list of Features for the faces it recognised.
But, Now I am confused That how to use these features and save in my local data base to recognise faces from the pictures.So My queries are following
1.) How to convert Face features to Actual working Face recognition API means What is the actual algo or solution I can use to merge diffrent face features of a same person to identify him correctly.
2.) Uploading images and then creating database for Face-features set is a very time taking process. Do any one knows any Android/iOS Face Recoginition SDK to do this so that I can do this accurately and timely with no or less time taking process.
3.) Both solution-2 and 3 can be used with Images. Is there any other solution is available which can do the same with less efforts but with more accuracy.
OpenBR may be also interesting for you: http://openbiometrics.org/
Finally I am using Rekognition API. And this is good enough to serve my purpose.
Google provides a variety of 'cards' for Google Now (http://www.google.com/landing/now/). Is it possible to create your own cards? The system looks pretty modular, but I haven't found any documentation or instructions to do so. (I believe you need to supply the content of the card, and some way of signaling when it is supposed to be shown. There is probably just some interface that you have to implement.)
If there is no documented solution, a hackish/undocumented way would be ok, too. I'm mostly curious how it works.
Edit: Specifically, does somebody have knowledge about the internals of Google Now, e.g. by decompiling the .apk? What I've seen suggests it is pretty modular, and it should be fairly easy to drop another class into the .apk, or to maybe inject code using Cydia Substrate. I know that there is (as of Nov. 2013) no official way to add new cards.
There is currently no way to do that. Google makes its own cards and custom application cannot register any cards. But I hope it will be possible in future.
Actually Google announced last week that developers can now develop custom Google Now cards:
http://www.google.com/landing/now/integrations.html
However, a developer guide seems not available yet.
Edit:
On the end of the page they point out that:
We'll let you know when we are able to onboard more partners
There is a work-around that will soon allow you to place cards in Google Now's stream at a particular time or a particular location: Use Google Keep (https://drive.google.com/keep/)
You can create a new card at Google Keep with a time based or location based reminder, depending on which the relevant card will show up in Google Now.
Since Google Keep is now in Drive, the API is expected to be available soon (keep a lookout for it at http://discovery-check.appspot.com/ )
There is not way to do this by your own at the moment. If you really want to do it you can fill in this form: https://services.google.com/fb/forms/nowintegrations/. You can ask Google if they want to cooperate to create a Google Now card.
Note quite an answer, as it is still not possible to create Google Now cards, but you can now hook into the Google Now search function (basically Android's Siri) and provide custom search results. For example you can say "show me the lyrics to..." and it opens a lyrics app.
Here is a link to the project which is based on the Xposed framework.
Just guessing from my impression of the Google Search apk (which includes all the Google Now functionality and even the home screen on KitKat), it should be possible to use a similar technique to inject cards into the app - however since the app is huge and very complicated, it will be a lot of work. I'd keep my eyes open on the xda-developers forums, wouldn't be surprized if someone there solves this in the future.
It appears that there is developer documentation on how to push google now info via email, eg. flight details, restaurant reservations etc.
https://developers.google.com/schemas/now/cards
I have yet to dig into this, but may update this answer if I discover anything significant.
I've read numerous discussions lately about different forms of security for mobile devices outside of the typical password/pin code setup.
The articles talk about recognizing the touchscreen as a human input device and that security measures in apps ought to evolve for that as well.
One such concept involved a graphical keylock like one you would see on a safe. The would have to use multiple fingers to twist it to the correct combination. I haven't done any OpenGL stuff so I wouldn't really know how to develop that, has it been done, is it open source?
I did read this: Security Beyond a Username/Password? , but I am looking for other opinions.
Thanks for any suggestions and resources. Also please post resources instead of voting to close if it comes down to that.
I cann't say for all mobile devices, but iOS SDK provides UIGestureRecognizer class, you may create a subclass that UIGestureRecognizer that recognizes a distinctive gesture, character or some kind of gesture combination (in your case). I assume another mobile technologies also have similar methods to recognize keylock characters.
Hope it help you.