AndrewCopeland

I am glad you find it useful. Please let me know if you have any questions.

If you like it, I would greatly appreciate an upvote, it really helps with visibility.

Its a simple cli in go It uses docker There is no k8s Handles certs Zero down time

I would love for it to support docker-compose as some of my side projects needs a library in python but I like having my service be in go, so I will wrap the python library in a super simple service.

Overall this is awesome and I love the simplicity, with the world just full of serverless, AI and a bunch of other "stuff". Paralysis through analysis is really an issue and when you are just trying to create a service for yourself or an MVP, it can be a real hinderance.

I have been gravitating towards Taskfile to perform similar tasks to this. God speed to you and keep up the great work.

I like the website. Did you start with a specific template?

Website looks nice! Looks like we are competitors, I run https://ipdetective.io.

It would love to connect, I will send an email to your support so we can exchange numbers.

I've seen AI generated content about dog breeds, the content was absolutely horrible to watch and listen too.

In the near future we will have YouTube videos that pride themselves on being organically made, no GMOs and built by humans.

That's what I do, I think I provide a great product/service but also still want to get the word out.

A marketing agency who will sell a bag of shit as long as they get paid is definitely a net negative.

Overall reddit has been going down hill for a decade at this point and it only makes sense that it will/has been captured by companies trying to profit off it.

Nice, I like how simple it is!

I provide a similar service but with more focus on bot/data center/VPN ip addresses.

https://ipdetective.io

Shameless plug, if you do not want to spend the time aggregating all datacenter IP addresses you can use the IPDetective.io API to easily detect of an IP address comes from a datacenter, VPN, proxy or botnet.

I wrote a bash script to collect demographic information for everyone in the country using the us census. I also created a simple bash script to take notes following the zettelkasten method, you can check it out here: https://github.com/AndrewCopeland/zettelkasten

Love the story! Breath of fresh air and a similar trajectory I would like to take for my own startup.

The slow burn is real and making meaningful connections to customers is important for consistent revenue in the long term.

I have added the feature for a user to add known addresses so they do not get flagged as bots. Take a look at the API docs here: https://ipdetective.io/api

Currently the known address is scoped to the user/client who is using the service.

I ended up allowing a mechanism to exclude ip addresses for a specific user. The step after this is too have certain IPs excluded from the entire IPDetective list and not just for a specific user.

All of the IP are stored in memory. This takes up about 3.5 GB. I have a text file that is 445K lines that contains all of the specific IP addresses and the IP prefixes (CIDR) that make up that 250 million ips.

Uncompressed I do not know. Are you interested in the ranges and ip addresses or a list of all the ip addresses that make up all the ranges as well?

Let me know what you need and I could definitely try and accommodate for you.

Is you VPN installed in some type of datacenter or hosting service? If so thats how I am detecting it. Yes I am blocking all IPs from specific ASNs.

Is it your home dedicated ip?

It seems more affordable, I do not know if its more accurate.

I would like to expand. See what users need and pivot as needed. A cheap version of CF's proxy seems like an interesting start. I do not know if I have the expertise though.

I feel you. Maybe we could work something out.

Ahhh makes sense. I could definitely offer that it's pretty large being 250 million IP addresses. I wonder what the best format would be? Csv? SQLite?

Sounds good, this has been a common request and is definitely on the road map. I am trying to create a very fast service and data querying slows it down. With that being said I am thinking about adding a query parameter like `?info=true` that would end up providing more information. Like the examples you gave above.

I get the idea, seems like a hot topic in the comments and a solution is definitely possible. The "placing protocols to avoid abuse" seems like the most difficult part :).

Sounds like a great idea and an even better feature. Would that exception only work for you? Or would it also work for other users of IPDetective?

I would agree with everything you are saying. I did not start this service for the sake of stopping actual people from using certain websites. I started this service to mitigate/detect bot abuse of consumer applications.

I think it really is dependent on the consumer application. But mentioned by some other folks is to add the ability to have IP exceptions, essentially an allow list, which I am in favor of. This brings up an entirely different issue, which is identifying the user as legitimate.

IPDetective collects data data from bot nets, datacenters, tor nodes, proxies and vpns. Is that what you are looking for?

Also IPDetective can be used just as a detection solution rather than a prevention solution.

Sometimes I use it against my nginx access logs and see how much of my traffic could be from bots.

Thank you very much for your input. I will look into having the privacy be more verbose around the system logs and for how long I store them.

> I keep look for something I can just add lists to my server and check against that, but not going to spend thousands on it.

What do you mean by this? Like having the ability to create your own deny/black list of ip addresses and then you can validate against it?

How would you plan on storing the feed of IP addresses? I currently reach out to 3rd party and then aggregate all of the IP addresses once a day.

That is a real good idea, I really like it.

I do not, but it seems like a great feature request. I will look into adding something like this.