OOPSpam Anti-Spam API
The better, new standard to stop spam content
With this release:
✅ Spam Sensitivity level. Control how aggressive you want your anti-spam filter to be.
✅ Once detected move spam comments either to Trash or Spam
https://wordpress.org/plugins/oopspam-anti-spam/
Here are some changes I made to the API itself this week to increase better detection of spam while avoiding misdetection of legitimate contents:
✅ Both Adult Content Detection and Spam Content Detection models are improved
✅ Added spam words in Russian
✅ Increased accuracy, lower latency
Followed marketing examples article and made my first competitor comparison page.
Akismet (mostly) and a few other big companies dominate the market. I bring the same and accuracy without exploiting people's data. Hopefully, this market move will attract some traffic.
Check out: An Akismet alternative
The initial version of OOPSpam Anti-Spam API was a school project and I made it public to show my potential future employer. But people started to email me and show interest. So I improved it based on one customer who was willing to subscribe and he did.
.... but I was worrying that I won't able to go beyond my 1st customer. Even though I improve the product daily and redesigned the website, wrote blog posts.
So it was true that if you solve someone's problem, there are going to be someone else who also has the same problem.
Well, yesterday I got my 2nd customer who subscribed to ULTRA plan.
Hopefully, this trend will continue.
Finally, updated the website with more information and call to action.
Added:
- FAQ with 6 questions
- Clear Pricing and Docs link on the navigation bar.
- Link to OOPSpam WordPress plugin
Get a keyaction links on 3 different places- Update illustration
and other small changes.
I'm happy to announce that OOPSpam Anti-Spam WordPress Plugin is finally available for OOPSpam API users.
This is big for me. This new plugin allows current customers to use the same API key they were using on other platforms within the Wordpress environment.
I got my first customer. Yay! ✨
I talked with this customer before the launch. I'm super happy that I was able to solve someone's problem and eventually get a paying customer.
-
2
🙌Congratulations!
- This is a really good way to get your first paying customer! Do you feel like you had to offer a discounted conservative price to entice them to be your first?
-
1
thanks!
Not at all, I delivered and the first customer tested it a few times to see if the product does what it claims. Eventually, he purchased a plane without contacting me.
-
2
Congrats!
Looking forward to hearing of your next customer milestone....10 customers? :)
-
1
thanks :)
-
-
1
How did you get speaking to the customer in the first place?
-
1
This project was my college project. I made it online as a public API a year ago. He contacted me via email and was interested in the paid version with a low-latency and more features.
-
Hopefully, the product will get more traffic and potential users. Still waiting for the first paid subscriber.
Today I got a notification, apparently, I didn't update the request body on RapidAPI to reflect the latest change 😞. Good thing, an error tracking Sentry reported it so I fixed it before someone else affected.
Lost a potential customer.
Lesson learned!
-
2
You will always do mistakes. What's important is: how much time you need to recover from them and not impacting more people. It's called MTTR (Mean Time To Restore) and it's really important.
In order to reduce it, you need some automation: simple way to put a previous version of your website / database, simple way to manage crisis like sending an email prepared in advance if your server crash, and so on.
-
1
Thanks for the comment.
I added some automation during the development, such as error tracking which notified me right away. Fortunately, the RapidAPI provides a way emailing to a user. So, I fixed the issue and let the user know.I will try to see what else can be automated to reduce even further.
-
-
2
The first of many 😅. The mindset I've shifted towards is less "never make mistakes" (because then you inevitably will make mistakes, and then you beat yourself up for it) and more "how do I minimize the scope impact of mistakes?" (heavy regression testing, status pages, ability to handle rollbacks / replays, etc)
-
1
Thanks for the input
I am glad I implemented an error tracking during the development, it notified me and I fixed the issue, so luckily there wasn't a big impact.
It is amazing how a small overlook may cause a bigger issue.
-
What does it mean? 🤔
If you know that you may receive a legit content in a few languages, say English, Vietnamese, Turkish then your content_lang parameter should have JSON array with multi-languages ["en","vi", "tr"].
In case the content you pass to the API doesn't match one of the languages you passed in content_lang then most probably you got a spam (it will affect the general spam score).
In 2017, during my studies, I built OOPSpam API as a way to pass my exam (I ended up passing two). It was a backend and a silly android app. as a proof of concept. I made a landing page, deployed the API on Heroku, just to have it online.
After a while I got a bunch of emails asking more features. People started to subscribe to the email list and so on. I decided to work on a new more accurate, detailed version of it.
... finally, today it is online.
It supports the following features:
✅ Spam score
✅ Machine Learning algorithm
✅ Multiple blacklisted IPs list
✅ Language outlier detection algorithm
✅ Spam word detection
Comment