rakjosh

"Created 34 minutes ago Waiting in a queue… You will get an email upon portrait generation."

Not sure if this is legit or just a way to collect data. I find it odd that it has been 34 minutes and my image is still in queue.

I was working on a similar website :) https://ppp-loan.info/

https://ppp-loan.info/ Shows all the businesses that were approved for more than $150K Loan (SBA PPP Loan). Filter by company name, city, state, loan amount

Created a small website to find businesses in my city that received SBA PPP (Payment Protection Program) Loan. For now the you can find businesses that received loan above $150K filtered by Name, city, state, amount.

I'll be adding some more visualizations and statistical summery. Any suggestions on what kind of summery would be helpful?

I don't think I'll be able to do dictionary checks because people from different country use this, in their own languages. I get around 5-6K people every day from all around the globe.

It would be ideal, but very hard to implement for all different languages I think, unless I'm missing something.

IP is not something I can rely on, because looks like they have enough unique IP addresses to use. And like you said, motivated and a lot of time on their hand. I feel like adding that 60 seconds delay only make the UX bad for genuine users.

This is my website if anyone was wondering: https://freephonenum.com/

My competitor was scrapping all my phone numbers and SMS received from my site and displaying it on their site. It took me several months to figure that out. I was seeing abnormal bandwidth usage for JSON (my API endpoint) but never realized that someone was constantly pinging my APIs.

[edit] Now, I've removed the API and everything is served as HTML (not easier for someone to scrap my API)

The content is served using API that is open for everyone to use. And that is making it difficult for me to protect it. I've tried changing the structure of API response several times, but they counter it within few hours. Tried adding unique headers to requests etc (That worked for quite some time) but they figured it out ultimately. I come up with some solution, they figure it out in a day or two. And that went on for few weeks

That is what I did initially. My API was sending garbage data Saying this website is shutting down, please visit [mysite] for more info :D. But later on, they figured, I was sending garbage data and people were visiting my site because of that. I even put in a tracked link to see how many visitors I'd get from there site and I was getting around 500 people every day.

It was like a cat and mice game for a few weeks.

That was definitely a very good resource. I've gone through that and tried to implement as many things as I could.